> ## 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.
> - On Listo's self-serve pricing the stores your account created itself carry no Plan Listo: `plan` is `null`, there is no Plan Listo per store, and the account pays for each trip and for the add-ons it switches on (monthly ones each month, per-use ones each time they are used). A restaurant that connects to a self-serve account keeps its own plan and pays it itself. On any other account every live store carries one Plan Listo, charged to the partner, unless the agreement has each restaurant pay its own. 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 (a store created by a self-serve account is never refused for lack of a plan, but it can still be refused with `402 plan_required` when Listo has switched its couriers off, and then the message says to contact Listo and nothing you pay changes it); 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, ChatGPT) can act on a developer account at `https://api.listo.delivery/mcp`, an MCP server over Streamable HTTP. A person connects by signing in (OAuth: the client opens a browser, the person signs in, chooses the account and allows it, optionally read-only); a script sends `Authorization: Bearer <API key>` instead. A sign-in access token works on `/mcp` only, never on `/v1/`. 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.

# Repartidores en una llamada API

> Cotiza, crea y rastrea envíos para tus tiendas, y administra el saldo con el que se pagan.

Listo despacha repartidores para tus tiendas. Registras un punto de recolección,
preguntas cuánto cuesta un envío y lo despachas; Listo consigue al repartidor, te
mantiene al tanto mientras avanza y se encarga del dinero, incluido el efectivo
que se cobra en la puerta del cliente.

Todo vive bajo `https://api.listo.delivery/v1/` y se autentica con una llave de
API tipo bearer. La llave que envías decide en qué mundo estás: una llave de
prueba despacha un repartidor simulado que recorre el ciclo real, y una llave de
producción despacha uno de verdad. Los montos siempre son pesos mexicanos en
centavos enteros, y las marcas de tiempo siempre son ISO-8601 en UTC.

> [card] [Inicio rápido](https://docs.listo.delivery/es/quickstart.md)
>
> Tu primer envío, de principio a fin, con una llave de prueba.

> [card] [Cotiza y crea un envío](https://docs.listo.delivery/es/guides/quote-and-create.md)
>
> Las dos llamadas con las que empieza toda integración.

> [card] [Recibe y verifica webhooks](https://docs.listo.delivery/es/guides/webhooks.md)
>
> Suscríbete a los eventos de un envío y valida su firma.

> [card] [Fondea tu saldo y retira](https://docs.listo.delivery/es/guides/balance-and-withdrawals.md)
>
> Con qué se pagan los envíos y cómo sale el dinero de ahí.

> [card] [Sal a producción](https://docs.listo.delivery/es/guides/go-live.md)
>
> Qué cambia cuando cambias la llave de prueba por una de producción.

> [card] [Conecta un restaurante que ya usa Listo](https://docs.listo.delivery/es/guides/connect-existing-account.md)
>
> Pídele a su dueño que conecte la cuenta que ya tiene, en lugar de crear una segunda.

> [card] [Plan y cobro](https://docs.listo.delivery/es/guides/plan-and-billing.md)
>
> El Plan Listo que lleva una tienda en modo real, y quién lo paga: cuánto te cuesta, cuándo se cobra, cómo terminarlo o reactivarlo, y por qué las tiendas que creas con el precio de autoservicio no llevan ninguno.

> [card] [Conecta Claude, Cursor, Codex o ChatGPT](https://docs.listo.delivery/es/guides/connect-ai-client.md)
>
> Inicia sesión desde tu asistente de IA y deja que cotice, reserve y siga envíos, con un paso de confirmación antes de mover dinero.

> [card] [Referencia de la API](https://docs.listo.delivery/es/api-reference/authentication/check-that-your-api-key-works.md)
>
> Todos los endpoints, generados desde las pruebas.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.