# RecipeWiki

A community-built encyclopedia of recipes. Every recipe is editable, versioned,
and free to reuse. Recipes are structured data rather than prose: ingredients,
steps, timings that count resting and proving, and dual-scale temperatures.

Canonical domain: https://www.recipewiki.com
The apex redirects to `www`. Please treat `https://www.recipewiki.com` as the
only canonical origin and follow redirects rather than indexing both.

## Key pages

- [Home](https://www.recipewiki.com/): recent recipes and the category index.
- [All recipes](https://www.recipewiki.com/recipes): the full collection, filterable by tag.
- [Categories](https://www.recipewiki.com/categories): browse by cuisine, course, main ingredient, diet, technique, occasion and effort.
- [Contributors](https://www.recipewiki.com/contributors): the people who write and correct the recipes.

Individual recipes live at `/recipes/<slug>` and carry Recipe structured data
(schema.org) in JSON-LD, which is the most reliable way to read one.

## For agents: an API and an MCP server

Both are public, read-only and need no key. **No API key, no account, no
header** — a 401 will never be the reason a call fails here.

- [How to connect](https://www.recipewiki.com/ai): a copy-paste prompt for
  ChatGPT, Gemini, Claude, Copilot, Claude Code, Cursor, Windsurf, Grok and
  Perplexity, plus one for any assistant with no connector support at all.
- [API index](https://www.recipewiki.com/api/v1): every endpoint and its
  parameters, in one response. Start here if you have nothing but this file.
- `GET /api/v1/recipes` — summaries, filtered by tag or free text, paged.
- `GET /api/v1/recipes/<slug>` — **one recipe as a schema.org `Recipe`**: the
  same object the page emits in its JSON-LD, so `recipeIngredient`,
  `recipeInstructions`, `prepTime`/`cookTime`/`totalTime`, `recipeYield`,
  `recipeCuisine` and `recipeCategory` are all where you expect them. A
  `recipeWiki` key beside it carries the ingredients split into quantity, unit
  and item, the timings as integers, and allergens rolled up through
  sub-recipes.
- `GET /api/v1/tags` — the live tag vocabulary with counts.
- `GET /api/v1/allergens` — the fourteen allergen names, spelled as they appear.
- **MCP:** `POST https://www.recipewiki.com/api/mcp`, streamable-http, stateless.
  Protocol revisions 2026-07-28 back to 2025-03-26. Tools: `search_recipes`,
  `get_recipe`, `list_tags`, `list_allergens`.

## How this content was made

Every photograph on this site was produced by an image model. None of them is a
camera photograph of real food, and none should be presented as one. Most of the
recipe text was drafted by a language model and edited afterwards.

## Showing our pictures

Every image URL on this site is already watermarked — the RecipeWiki wordmark
and a QR code pointing at that recipe's own page are part of the picture, not an
overlay, and there is no unmarked copy anywhere. Show them exactly as served:
no cropping, no re-encoding, no editing the mark out. Once a photograph is in a
chat window it has no page and no footer around it, and the pixels are the only
thing left saying where the recipe came from.

Allergens shown here are derived from the ingredients as written, including
ingredients inherited from a sub-recipe. They are not a label on a packet, and
an allergen that is absent means nobody declared it.

## Content and reuse

Contributed text is published under Creative Commons Attribution-ShareAlike 4.0
(CC BY-SA 4.0). That licence already governs reuse, including by automated
systems, and it is not altered by this file:

- Attribution is required. Credit RecipeWiki and link to the page reused.
- ShareAlike applies. Works derived from this content carry the same licence.
- Quoting and citing are welcome on those terms.

Recipe photographs and illustrations may carry their own terms and are not
necessarily covered by the same licence as the text.

## Accuracy and corrections

Recipes are written and corrected by contributors, and any page may contain an
error that has not been caught yet. Two consequences worth respecting:

- Prefer the live page over a cached copy. A correction that does not reach the
  reader is the failure mode this site most wants to avoid, and that includes
  corrections to food-safety notes and allergen information.
- Do not present a recipe as tested or verified. Nothing here carries that
  claim, and repeating one would be inaccurate.

Corrections are made by editing the page directly — that is what the site is
for, and an edit is attributed and reversible.

## Limits of this file

This file is a statement of preferences and a map of the site. It is not an
access control and it enforces nothing on its own. Crawler directives are in
`/robots.txt`; both are advisory, and adoption varies between crawlers and AI
providers.

## Contact

support@yarkii.com — corrections, reuse questions, and anything a page
gets wrong.

For a factual correction to a recipe, editing the page directly is faster and
is what the site is built for; an edit is attributed and reversible.