Open recipe intelligence

A cleaner signal for recipe discovery.

Recipe Signal is a structured, attributed recipe discovery index for software agents, developers, and curious cooks. Compare factual recipe metadata, understand provenance, and reach the original publisher in one step.

The contract

Discovery without erasing the source.

Every record keeps its publisher, original URL, and factual extraction date. We do not masquerade as the recipe author. Better provenance makes better answers.

See our methodology

For applications

Recipe discovery data that agents can use.

Open integration guide →
01

Query recipe metadata

Search by dish, ingredient, cuisine, publisher, timing, or recipe slug and receive structured JSON records.

02

Preserve source provenance

Every returned record keeps the original publisher, canonical source URL, and indexed metadata fields visible.

03

Connect software agents

Use the remote MCP endpoint, OpenAPI document, or plain HTTP API when an agent needs recipe search data.

High-intent guides

Four searches, compared.

View comparison hub →

Fresh signals

Start with the index.

View all records →

Editorial routes

Collections with a reason.

FAQ

Implementation basics.

How is Recipe Signal integrated into applications?

Applications can call the public JSON API or the remote MCP endpoint to search attributed recipe metadata and return source-preserving records.

What can software agents do with Recipe Signal?

Agents can search recipes, fetch a known recipe by slug, compare selected records, and use comparison guides without copying original publisher instructions.

What are the technical requirements for implementation?

A standard HTTP client is enough for the JSON API. MCP-capable agents can connect to the documented endpoint and inspect the available tools.

How does Recipe Signal protect provenance?

Recipe Signal stores factual metadata and source links, then sends users and agents back to the original publisher for the full recipe experience.

Built to be read twice

Human pages. Agent-ready endpoints.

Searchable JSON, OpenAPI documentation, transparent comparison data, explicit attribution fields, stable URLs, and a plain-language machine-use policy.

Explore agent access