An open recipe JSON standard
Cookpit is a new recipe standard, freely available to app developers, vibe coders, cooks, chefs and culinary protagonists building real-time and innovative cooking and training applications for any platform — including those incorporating online grocery, cookware, kitchenware and appliance internet shopping. All in pursuit of improving personal meal options, home food choices, family nutrition and dinner-party meal outcomes.
Under the hood, Cookpit is an open cooking file format — recipe JSON (JSON-LD) with a published schema, lexicon and browser validator — that apps read in real time, turning any recipe into a live cooking plan.
Built for app developers, vibe coders, cooks, chefs and culinary teams.
The one sentence to send to your AI
Attach the recipe PDF to the chat, then send this. Use a chatbot that can fetch a URL and run code, with both enabled — minimum spec GPT-5, Claude Opus 4.7, or Gemini 3 Pro (or later). It fetches the mega-document, computes the deterministic ids and source fingerprint, and produces a v3.2 cooking file.
Follow the instructions at https://cookpit.org/v3.2/ai and produce a Cookpit v3.2 cooking file from the attached recipe PDF.The launcher pre-fills the prompt; you still attach the recipe file inside the chat before sending.
AI prompt (mega-doc)
Self-bootstrapping prompt + rules + lexicon + canonical profiles + JSON Schema. One URL, one fetch.
Validate (browser)
Drop a generated file in your browser. The canonical Python validator runs in-tab. Your recipe never uploads.
Authenticate (browser)
Stage-3 attestation. We validate, then sign with the cookpit-chefs-friend Ed25519 key and stream a downloadable .A.jsonld back.
Read the spec
Prompt, rules, lexicon, validation, glossary, canonical profiles. Versioned, immutable URLs.
How it works
Architectural overview of the v3.2 schema and the four-stage generation, validation, attestation and consumption lifecycle.
Versions
Every cookpit.org/vX.Y/ URL is immutable forever. /ai is the moving alias to the current version.
Security
A+ on the MDN HTTP Observatory. Hash-pinned CSP, HSTS preload, and a CI gate that blocks any inline-script regression before deploy.
Trusted (verify in your app)
The canonical reference for app developers: how to verify a file is genuinely cookpit-authenticated before you cook from it. The one rule, the pinned key, and a drop-in implementation.
License
The Cookpit v3.2 JSON-LD schema/format is dedicated to the public domain under CC0 1.0 Universal: copy, modify, and use it freely, no attribution required. CC0 covers the format only — recipe content within a cooking file is not covered.
This new standard was shaped in large part by AI, guided by us at broadbaseai.com. Use it well — donations welcome.