# Build with AI

Give your coding agent the contract and the docs, and it writes calls that match the API.

## Docs for machines

| Resource | Use it for |
| --- | --- |
| `https://docs.lelemon.cl/llms.txt` | Index of every page and every v2 route |
| `https://docs.lelemon.cl/llms-full.txt` | All the documentation in one file |
| `https://docs.lelemon.cl/openapi.json` | The v2 contract. No key needed |
| `https://api.lelemon.cl/v2/openapi.json` | The same contract, served by the API |
| Any page URL plus `.md` | That page as Markdown |

Every page has a "Copy page" action that copies it as Markdown for a prompt.

## A starting prompt

```text title="Header"
Help me integrate Lelemon.

1. Read https://docs.lelemon.cl/llms.txt before writing code.
2. Use the key (lel_live_...) from the LELEMON_API_KEY environment variable.
3. Send an Idempotency-Key on every POST.
4. Verify webhook signatures with the raw request body.
5. Branch on the error code, never on the detail text.
```


You can connect your own MCP servers to your agents with `POST /v2/mcp-servers`.

## MCP server for the API

A coding agent or a copilot can operate Lelemon through an MCP server generated from the contract. It does not offer approvals, API keys or erasure unless you turn them on. See [MCP server](/tools/mcp).

Every route declares what it does in `x-lelemon-effect` (`read`, `write`, `destructive` or `money`), so an agent can tell a safe call from one that reaches a person.