# Documentation for AI agents

> How to consume this documentation from an LLM, a coding agent, or any automated tool.

This documentation is built for both people and AI agents to read. All content is generated as static HTML and plain Markdown.

## Which format to use

| Format | Use it when… |
| --- | --- |
| **Per-page Markdown** — e.g. [`/en/guides/partner-api-guide.md`](/en/guides/partner-api-guide.md) | You want to feed a single page to an LLM, or paste it into a chat without HTML noise. |
| [**`/llms.txt`**](/llms.txt) | You want the agent to first discover what the site contains and then decide what to read. This is the index, following the [llmstxt.org](https://llmstxt.org/) standard. |
| [**`/llms-full.txt`**](/llms-full.txt) | You want to load every guide in full, in one shot. |
| [**`/llms-small.txt`**](/llms-small.txt) | Same, but a trimmed-down version for models with a small context window. |
| [**OpenAPI 3.0**](/openapi/partner-api-en.json) | Your tool understands OpenAPI: it's the source of truth for the API reference (endpoints, schemas, authentication). There are two specs — [Partner API](/openapi/partner-api-en.json) and [Purchase Code API](/openapi/pcode-worker-en.json) — also available [in Spanish](/openapi/partner-api-es.json). |

<Aside type="note" title="How content is split">
	`llms-full.txt` contains the **guides**. The **API reference** is not duplicated there: that's what the OpenAPI specs are for, already machine-readable and always in sync with the published documentation.
</Aside>

## Per-page Markdown

Every guide page is also published as plain Markdown: add `.md` to its path.

```
https://docs.firma.digital/en/guides/partner-api-guide.md
https://docs.firma.digital/guides/partner-api-guide.md
```

Every guide also has buttons at the top to **copy the Markdown** to your clipboard, **view it** raw, or open that page directly in **ChatGPT**, **Claude**, or **Gemini** with the context already loaded.

## Pointing an agent at this documentation

For an assistant with internet access, the recommended entry point is `llms.txt`:

```text
Read https://docs.firma.digital/llms.txt and then whatever documents you
need from there to help me integrate Firma Digital's partner API.
```

If it's going to generate code against the API, give it the OpenAPI spec directly:

```text
Use https://docs.firma.digital/openapi/partner-api-en.json as the reference
for Firma Digital's Partner API and help me implement the redeem flow.
```

## Authentication

Any code an agent generates needs to authenticate. Every request to both APIs carries the API Key in the `x-gw` header:

```http
x-gw: {YOUR_API_KEY}
Content-Type: application/json
```

The full flow is in the [Partner API Integration Guide](/en/guides/partner-api-guide/).