Appearance
Docs for AI tools
These docs are published in formats that coding assistants and LLMs read well, following the llms.txt convention.
| File | What it is | Use it when |
|---|---|---|
/llms.txt | An index: one line per page with a short description and a link to its Markdown. | A tool should discover pages and fetch only what it needs. |
/llms-full.txt | Every page plus the full OpenAPI spec in one Markdown file. | You want to paste the whole of MarleyFetch into a chat or a context window. |
/<page>.md | Any page as raw Markdown, e.g. /guides/sending.md. | You want one topic. Every page also has Copy page as Markdown at the top. |
/openapi.yaml | The OpenAPI 3.1 spec for every public endpoint. | Generating a client, or giving a tool exact request and response schemas. |
Using them
In a chat — paste the URL or the contents:
text
Read https://docs.marleyfetch.com/llms-full.txt, then write a Cloudflare Worker that sends
a welcome email through MarleyFetch when it receives a POST to /signup.In Cursor — type @Docs, choose Add new doc and enter https://docs.marleyfetch.com/llms-full.txt.
In Claude Code, Copilot and other agents — point the agent at a page's Markdown, or put a line in your project's instructions file (CLAUDE.md, AGENTS.md, .github/copilot-instructions.md):
md
Email is sent with MarleyFetch. API docs: https://docs.marleyfetch.com/llms.txtFor code generation — feed /openapi.yaml to your OpenAPI generator of choice.
Keep keys out of prompts
Never paste an API key into a chat. Tell the assistant to read it from an environment variable such as MARLEYFETCH_API_KEY.