Cookwala

Cookwala / For

For companies: startups, enterprises, grocers, restaurants, insurers, certifiers

Every company that touches food will meet cooking machines and AI agents in the next few years. Cookwala gives you one interface for all of them, with safety limits enforced on the device and records you can audit.

Why it matters to you

For grocers and delivery: receive delivery windows and allergen requirements, never a family's schedule. For restaurants and food service: a kitchen and production-run record that links device executions to meals served and food-safety control points. For insurers and certifiers: a conformance report format and an anonymous incident feed designed for you. For startups: a neutral layer instead of a dozen vendor integrations, and a market profile (experimental) for offers and quotes.

Ways in, light to deep

  1. Light. Read the investors and partners page and the trust page; map your products to the ingredient classes and operations.
  2. Medium. Publish an offer feed (market profile, experimental) or a surplus offer to a local program; run the agent-safety benchmark on the agent you plan to deploy.
  3. Deep. Implement the Core API in a product; sponsor a conformance verification; join the steering committee when it forms; adopt the certification path.

First success, under 15 minutes

Convert one product line to a market Offer with GTINs and allergen credentials, validate it, and see which example recipes it can supply:

cookwala validate   # schemas, examples, vocabularies, APIs
examples/market/offer-feed.json: ok

The path after that

  1. Offer feed or surplus offer
  2. Derived constraints from households, never their facts
  3. Orders through your own checkout; Cookwala never carries payment data
  4. Fulfilment events
  5. Reputation from execution reports, with consent

Other paths