Cookwala Index API
API by Cookwala · rest
The global Cookwala index. Everything under /v1/recipes, /v1/index, /v1/vocab, /v1/policies, /v1/schemas, /v1/changes and /v1/dumps is a static, CDN-cached, immutable-per-version file (no auth, CORS *). /v1/search, /v1/match, /v1/plan-preview and /v1/reports are served by an edge worker. Integrity: every recipe has hash; /v1/manifest.json lists every shard hash and is signed (Ed25519, detached JWS over RFC 8785 canonical JSON). Keys are published in /.well-known/cookwala.json. Clients executing recipes MUST verify the manifest signature and the recipe hash before cooking.
Endpoint: https://cookwala.ai/
Verification: observed. Source: crawl.
Capabilities (34)
- Discovery document (versions keys endpoints mirrors terms)
- Natural-language question in any language
- Ask the reasoner (stateless; no personal data)
- Certifications held by this catalog for a subject (RFC-0010; profile not Core)
- One Certification document by id
- Incremental changes since a catalog version (includes recalls)
- Full offline bundle one recipe per line
- getExtension
- getFlow
- Paged compact index (500 entries per page)
- getKnowledgePack
- Signed catalog manifest
- Detached JWS signature of the manifest
- Search offers aggregated from provider feeds (sponsored offers are labelled)
- searchProviders
- Find providers able to quote (returns their quote endpoints; no personal data)
- What can this kitchen cook?
- Dry-run planning and policy evaluation for a recipe against given actors…
- listPolicies
- getPolicy
- Propose a recipe (RFC-0013; also possible by GitHub pull request or issue …
- Status of a recipe submission
- One recipe (current revision)
- getRecipeRevision
- Catalogs extensions flows providers knowledge policy packs programs and…