AI agents
Every page on this site is available as plain markdown, plus a full-site export and the OpenAPI spec. Point your coding assistant at these instead of scraping HTML.
If you build with a coding assistant, give it the markdown sources rather than the rendered pages. Every documentation page serves clean markdown at a predictable URL, and the whole site is available as a single file. No HTML parsing, no scraping.
Get one page as markdown
Every page has a Copy Markdown button under its title. It copies the whole page as markdown, ready to paste into a chat with your assistant. The Open menu next to it links the raw markdown file, and can open the page as a prompt in ChatGPT or Claude.
Tools that fetch pages themselves can skip the buttons. Append .md or .mdx to any documentation URL:
curl https://docs.xpay.app/en/integrate/idempotency.mdThis works on every page in both languages. Swap the en prefix for ar to get the Arabic version. Sending Accept: text/markdown to the normal URL returns the same content, and each page carries a <link rel="alternate" type="text/markdown"> tag in its head, so an agent can discover the markdown URL on its own.
Get the whole site
Three files cover the full documentation surface.
| File | What it contains |
|---|---|
/llms.txt | An index of every page with its title, description, and URL. Start here. |
/llms-full.txt | The guides and SDK reference as one markdown file. The API Reference is not inlined: use /openapi.json or a single page's .md for that. |
/openapi.json | The machine-readable API specification: every endpoint, object, field, and enum. |
The API Reference pages are generated from the OpenAPI specification, and their markdown carries the same parameters, request bodies, and response fields the rendered pages show. A field typed as a top-level resource (Charge, Refund, Price) appears as a link to that object's page; every other nested shape is expanded inline.
Which source to use
Pick based on how much context your tool can hold.
- Building an integration: load
/llms-full.txtonce and let the assistant search it. - Answering one question: fetch the single page with
.md, using/llms.txtto find the right URL. - Generating a client or validating requests: use
/openapi.jsondirectly. It is the same specification the API Reference renders from, so it never drifts from these pages.
Where to next
Object model
How Checkout Sessions, Payment Intents, Charges, and Refunds relate.
API Reference
Every endpoint and object, generated from the OpenAPI specification.
Event reference
Every webhook event, when it fires, and the object it carries.
Idempotency
Retry write requests safely with an Idempotency-Key.