> ## Documentation Index > Fetch the complete documentation index at: https://docs.listo.delivery/llms.txt > Use this file to discover all available pages before exploring further. > ## Agent Instructions > Notes on the Listo Partner Delivery API: > - Every endpoint is under `https://api.listo.delivery/v1/` and authenticates with a bearer API key. > - This documentation site is at https://docs.listo.delivery. The full machine-readable reference is the OpenAPI document at https://api.listo.delivery/docs/openapi.yaml (served by the API host, not by this site). > - Any page of this site is also available as raw markdown by appending `.md` to its URL, for example https://docs.listo.delivery/en/guides/webhooks.md. The index of every page is https://docs.listo.delivery/llms.txt and all of them in one file is https://docs.listo.delivery/llms-full.txt. > - Every page is published in English under https://docs.listo.delivery/en/ and in Spanish under https://docs.listo.delivery/es/, with the same path after the language. The API reference is under https://docs.listo.delivery/api-reference/ in English and https://docs.listo.delivery/es/api-reference/ in Spanish. > - To debug an integration yourself: `GET /v1/request_logs` lists the calls your keys made with what you sent and what was answered, `GET /v1/events` lists the events Listo emitted, `GET /v1/webhook_deliveries` lists every attempt to deliver them, `POST /v1/events/{id}/resend` sends one event again and `POST /v1/test_webhooks` sends a sample event (`"test": true`). The page https://docs.listo.delivery/en/guides/debugging describes them. A resent event is a snapshot from when it happened; `GET /v1/deliveries` is still how you recover current state. > - Every error response has `error.doc_url`, a page that explains that error code and what to do, and `error.request_id`, the same value as the `X-Request-Id` response header. All the pages are listed at https://docs.listo.delivery/en/errors. Filter `GET /v1/request_logs` with `request_id` to read the logged call. > - A `409 account_exists` from `POST /v1/stores` means the restaurant already has its own Listo account: connect it instead of creating it, as the page https://docs.listo.delivery/en/guides/connect-existing-account describes. > - Every live store carries one Plan Listo, charged to the partner. The exception is a connected restaurant that had already paid its current month: it keeps paying its own plan until its next renewal, shown as `paid_by: "store"` with the handover date in `pending_paid_by_on`. A `402 plan_required` from a quote, a delivery create or a retry means the store's plan is not paid or has ended; the page https://docs.listo.delivery/en/guides/plan-and-billing describes the plan, the `plan` block on a store and how to end or restart it. > - An AI assistant (Claude Code, Cursor, Codex) can act through the same API key at `https://api.listo.delivery/mcp`, an MCP server over Streamable HTTP authenticated with `Authorization: Bearer `. Every tool runs the matching `/v1/` endpoint, and each one that moves money first previews and then needs a confirmation token; the page https://docs.listo.delivery/en/guides/connect-ai-client lists the tools and describes the two steps. # Couriers in one API call > Quote, create and track deliveries for your stores, and manage the balance they are paid from. Listo dispatches couriers for your stores. You register a pickup location, ask what a delivery costs, and dispatch it; Listo finds the courier, keeps you posted while it moves, and handles the money, including cash collected at the customer's door. Everything lives under `https://api.listo.delivery/v1/` and authenticates with a bearer API key. The key you send decides which world you are in: a test key dispatches a simulated courier that drives the real lifecycle, a live key dispatches a real one. Amounts are always Mexican pesos as integer cents, and timestamps are always ISO-8601 in UTC. > [card] [Quickstart](https://docs.listo.delivery/en/quickstart.md) > > Your first delivery, end to end, on a test key. > [card] [Quote and create a delivery](https://docs.listo.delivery/en/guides/quote-and-create.md) > > The two calls every integration starts with. > [card] [Receive and verify webhooks](https://docs.listo.delivery/en/guides/webhooks.md) > > Subscribe to delivery events and check their signature. > [card] [Fund your balance and withdraw](https://docs.listo.delivery/en/guides/balance-and-withdrawals.md) > > What deliveries are paid from, and how money leaves it. > [card] [Go live](https://docs.listo.delivery/en/guides/go-live.md) > > What changes when you swap the test key for a live one. > [card] [Connect a restaurant that already uses Listo](https://docs.listo.delivery/en/guides/connect-existing-account.md) > > Ask its owner to connect the account they already have, instead of creating a second one. > [card] [Plan and billing](https://docs.listo.delivery/en/guides/plan-and-billing.md) > > The Plan Listo every live store carries: what it costs you, when it is charged, and how to end or restart it. > [card] [Connect Claude, Cursor or Codex](https://docs.listo.delivery/en/guides/connect-ai-client.md) > > Let your AI assistant quote, book and track deliveries through your API key, with a confirmation step before any money moves. > [card] [API reference](https://docs.listo.delivery/api-reference/authentication/check-that-your-api-key-works.md) > > Every endpoint, generated from the test suite. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.