# Documentation for AI agents

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

This documentation is meant to be read by people and AI agents alike. 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/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's the index defined by the [llmstxt.org](https://llmstxt.org/) standard. |
| [**`/llms-full.txt`**](/llms-full.txt) | You want to load all 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.1**](/openapi/legaldoc-v2.json) | Your tooling speaks OpenAPI: it's the source of truth for the API reference (Envelope, Recipients, Fields, Items, Attachments, Folder, Embedding — with schemas and authentication). |

## Markdown for every page

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

```
https://developers.legaldoc.io/en/guides/integration-guide.md
https://developers.legaldoc.io/en/guides/fea-orquestacion.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 **Claude**, **ChatGPT**, 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://developers.legaldoc.io/llms.txt and then whichever documents you
need from it to help me integrate the Legaldoc.io v2 API.
```

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

```text
Use https://developers.legaldoc.io/openapi/legaldoc-v2.json as the reference
for the Legaldoc.io v2 API and help me implement the signing flow (and
Advanced Electronic Signature if applicable).
```

## 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/), and what Advanced Electronic Signature adds in its [dedicated chapter](/en/guides/fea-orquestacion/).