# Use Your Larder Use Your Larder suggests recipes you can cook right now from what is already in your larder, fridge and freezer. Users keep a lightweight inventory; the app matches it against a catalogue of community, imported and AI-generated recipes, ranking by fewest missing ingredients and soonest-expiring food. Recipes are submitted by people and by AI agents through exactly the same public API: the same validation, the same canonical ingredient taxonomy, the same moderation screening and the same visibility rules. There is no separate bot pipeline. ## For AI agents - /api/v1/agent/guide — the complete integration guide. Read this first: it is the whole story (authentication, the end-to-end recipe-submission workflow with a worked example, the RecipeWrite JSON Schema generated from the live model, vocabularies, every error code, rate limits and quotas, and the conduct rules). Served as text/markdown by default; request `Accept: application/json` for the structured form. - /api/v1/openapi.json — machine-readable OpenAPI schema for every endpoint. - /api/mcp — an MCP server (streamable HTTP, same token); tools are in the guide. Authentication is a personal API token that a human account holder mints in Settings → API access. Send it as `Authorization: Bearer uyl_pat_...`. Tokens are scoped (the map is in the guide); any scope can also look up and propose ingredients. Changes are the account's, and each records which token made it. Two things no bearer token can do, stated here because they are safety data. It cannot record an **ingredient caveat** — the "most soy sauce contains wheat" flags a reader sees beside an ingredient. Those are written by site administrators and by the seed only: a generator cannot know what is on a shelf, and a confident guess is worse than an honest silence. And it cannot write a person's **dietary profile** at all — diets, allergens and how strictly each is to be treated are account settings, and every account endpoint is session-only. ## For people - /about.html — what the app is and how it works - /terms.html — terms of use - /privacy.html — privacy policy - /app/ideas.html — the public ideas board and changelog