# Docs for LLMs

> llms.txt, Markdown versions of every page, and one-click ways to hand these docs to Claude, ChatGPT or a coding agent.

These docs are written for people **and** for the agents they work with. Everything here is available as plain Markdown, so you can hand it to a model without scraping HTML.

## llms.txt

| File | What's in it |
|---|---|
| [`/llms.txt`](https://foodperfect.ai/llms.txt) | An index of every docs page with a one-line summary, following the [llms.txt](https://llmstxt.org) convention. |
| [`/llms-full.txt`](https://foodperfect.ai/llms-full.txt) | The full text of all pages in one file. Paste it into a chat or a Project for complete context. |

## Markdown for any page

Add `.md` to a page's path to get its Markdown: [`/docs/quickstart.md`](https://foodperfect.ai/docs/quickstart.md), [`/docs/tools.md`](https://foodperfect.ai/docs/tools.md) and so on. Every page also has a `<link rel="alternate" type="text/markdown">` in its head for crawlers.

At the top right of each page:

- **Copy page** copies the Markdown to your clipboard.
- The menu next to it opens the page in **Claude** or **ChatGPT** with a question ready, or opens the Markdown or `llms-full.txt`.

## Give an agent the docs

```text title="Prompt"
Read https://foodperfect.ai/llms.txt, then the pages you need, and set up the
FoodPerfect MCP server for me in this project.
```

For coding agents, add the [AGENTS.md snippet](/docs/agent-prompt/#agents-md-claude-md-snippet) to your repo so every session knows the endpoint, the retry rule and the approval flow.

## Machine-readable tool schemas

Your MCP client gets live schemas from `tools/list`. Without a client, `GET /openapi.json` on the MCP host returns a discovery document with every tool's input schema ([Raw HTTP](/docs/http/#other-endpoints)).