Integrate vision, costing, and inventory into your stack.
JSON webhooks and REST endpoints for recipe extraction, invoice ingest, and variance exports — designed for POS vendors, inventory tools, and custom operator pipelines.

500K+
Plates costed
12K+
Independent operators
98.4%
AI extraction accuracy
Try GET /api/v1/recipes
Issue a key from Integrations in your workspace, then call the v1 API from this marketing page. Requests go to your tenant host with Authorization: Bearer — no session cookie required.
Keys are created under Integrations → API keys (workspace owner only). This playground never stores your key — it stays in the browser until you leave the page.
Best-in-class Developer APIs for independent operators
Interactive API playground
Try GET /api/v1/recipes from the marketing site with your workspace slug and API key — responses render as JSON with no SDK.
Recipe extraction API
Send an image URL or upload; receive ingredient lines, yield hints, confidence scores, and suggested plate cost.
Invoice extraction API
Push PDF bytes; get normalized line items with SKU, quantity, UOM, and extended price for catalog matching.
Cost snapshot export
Pull current plate cost and food cost % per recipe ID for POS or menu board integrations.
Webhook subscriptions
Subscribe to price_index.updated for every case-price change, plus price_change (tolerance alerts), variance_threshold, and invoice_applied events.
From raw inputs to actionable plate cost
Bearer API keys from Integrations (owner-only)
Authenticate per-tenant API keys from Integrations in your workspace.

Live playground: GET /api/v1/recipes
Use the interactive playground on this page to call GET /api/v1/recipes with your slug and Bearer key.

Vision extract: POST /api/v1/vision/recipes/extract
POST dish images or invoice PDFs to extraction endpoints.

Webhook events for price index updates
Subscribe to webhooks for price index updates, tolerance alerts, and variance events.

Operators already have POS, accounting, and inventory tools. CulinaryInventory meets them where data lives — not as another silo that requires double entry.
- ✓Bearer API keys from Integrations (owner-only)
- ✓Live playground: GET /api/v1/recipes
- ✓Vision extract: POST /api/v1/vision/recipes/extract
- ✓Webhook events for price index updates
- Embed AI costing in existing operator workflows
- Reduce double entry between POS and finance
- Extend CulinaryInventory without forking the data model
Start using Developer APIs today.
Try CulinaryInventory free — cost one dish and see if the numbers surprise you.