Cookwala

Cookwala / For

For providers: grocers, farms, delivery, energy, AI vendors, recipe publishers

Providers plug into Cookwala as peers, not tenants. A grocer gets a constraint, never a household's facts. An AI vendor gets a benchmark and an MCP server. A recipe publisher keeps its name on every recipe and publishes a signed catalog from a static folder.

Why it matters to you

The standard defines a place for each of you and asks for nothing in return: a catalog is a folder with a discovery file; an offer feed maps products to ingredient classes; a signal (experimental) is aggregated and delayed so it is useful for planning and useless for pricing; an AI model is measured by a public benchmark before it is trusted in a kitchen. Reputation comes from outcomes with consent, not from fees.

Ways in, light to deep

  1. Publish a catalog of recipes. A static folder with /.well-known/cookwala.json and signed documents.
  2. Publish an offer feed. Market profile, experimental; your checkout stays yours.
  3. Run the agent-safety benchmark. Ten cases; publish results with the model id, date and config hash.
  4. Run a registry node. Anyone may; cookwala.ai is one of many.
  5. Offer surplus by SMS. FARM 120KG TOMATO A BB0411 to a program that runs the profile.

First success, under 15 minutes

Recipe publisher: scaffold, edit, validate, hash.

cookwala init my-dish && cookwala validate && cookwala hash my-dish.cookwala.json

AI vendor: add the MCP server to your client and run the ten agent-safety cases with promptfoo.

The path after that

  1. Catalog or feed under your proven namespace
  2. Registry entry with an exact version and a hash
  3. Recall feed if something goes wrong
  4. Reputation from outcomes

Other paths