# Documentation for AI agents

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

This documentation is built to be read by people and by AI agents alike. Every page is generated as static HTML and plain Markdown — no JavaScript required to read it — and the formats below are published automatically on every build.

## Which format to use

| Format  | Use it when…                                                                                                      |
| ------- | ----------------------------------------------------------------------------------------------------------------- |
| **Per-page Markdown** — e.g. [`/en/guides/integration-guide.md`](/en/guides/integration-guide.md) | You want to hand a single page to an LLM, or paste it into a chat without the HTML noise.                          |
| [**`/llms.txt`**](/llms.txt) | You want the agent to discover what the site contains first, then decide what to read. It is the index defined by the [llmstxt.org](https://llmstxt.org/) standard. |
| [**`/llms-full.txt`**](/llms-full.txt) | You want to load all of the guides into the context at once.                                                       |
| [**`/llms-small.txt`**](/llms-small.txt) | Same thing, trimmed down for models with a small context window.                                                   |
| [**OpenAPI 3.0**](/openapi/swagger-en.json) | Your tooling speaks OpenAPI: this is the source of truth for the API reference (endpoints, schemas and authentication). Also available [in Spanish](/openapi/swagger-es.json). |

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

## Markdown for every page

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

```
https://api-docs.legaldoc.io/en/guides/integration-guide.md
https://api-docs.legaldoc.io/guides/integration-guide.md
```

On top of that, each guide has buttons to **copy its Markdown** to the clipboard, **view** it raw, or open that page straight in **ChatGPT**, **Claude** or **Gemini** with the context already loaded.

## Pointing an agent at these docs

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

```text
Read https://api-docs.legaldoc.io/llms.txt and then whichever documents you need
from it to help me integrate the Legaldoc.io API.
```

If it is going to generate code against the API, give it the OpenAPI specification directly:

```text
Use https://api-docs.legaldoc.io/openapi/swagger-en.json as the reference for the
Legaldoc.io API and help me implement the signing flow.
```

## Authentication

Any code an agent generates needs to authenticate. Every API request carries the API Key in the `Authorization` header, with no `Bearer` prefix:

```http
Authorization: {API_KEY}
Content-Type: application/json
```

The complete flow is documented in the [Integration Guide](/en/guides/integration-guide/).