# Load docs into a coding agent

The Paxa API publishes machine-readable docs for coding agents. They are two llms.txt indexes, a markdown twin of every docs page, and an installable skill, all generated from the modules that render these docs.

These surfaces teach a coding agent to write against the API. To give an agent the API as tools it calls itself, with playback through the speakers, see the [MCP server](https://paxalabs.com/docs/mcp).

The Paxa API publishes three machine-readable surfaces for coding agents. They are two llms.txt indexes, a markdown twin of every page of these docs, and an installable skill. Start with the llms.txt index. Fetch a page twin when the task is narrow. Install the skill when the agent has a skills directory. All three are generated from the same content modules and API contract that render these pages. All three cover every product: text to speech, OCR, and translation into Thai.

## llms.txt

[https://paxalabs.com/llms.txt](https://paxalabs.com/llms.txt) is a compact index in the llms.txt convention: one line per page with its markdown URL and a one-sentence description, small enough to sit in a system prompt. [https://paxalabs.com/llms-full.txt](https://paxalabs.com/llms-full.txt) is the entire documentation serialized into one markdown document, for retrieval pipelines and long-context models.

## Fetch a page as Markdown

Every docs page is also served as plain markdown at the same path with a `.md` suffix: `/docs/text-to-speech.md`, `/docs/api/translate.md`, and so on, with the overview at `/docs.md`. Fetch one page when the task is narrow; each twin carries the full reference tables and examples of its HTML counterpart.

## Install the skill

The skill is one `SKILL.md` carrying the whole integration contract: the speech, transcription, OCR, extraction, translation, and feedback endpoints, voices, pricing, retry semantics, and every error code, with runnable examples. The [skills CLI](https://github.com/vercel-labs/skills) discovers it from this domain and installs it for every agent it supports, Claude Code and Cursor among them:

Terminal:

```bash
npx skills add https://paxalabs.com
```

The CLI verifies the file against the published sha256 digest and installs it into the agent's skills directory (`.claude/skills/` for Claude Code). The file itself is served at [https://paxalabs.com/skills/paxa/SKILL.md](https://paxalabs.com/skills/paxa/SKILL.md), readable in a browser before any install.

> If you installed this skill as `paxa-tts`, run `npx skills add https://paxalabs.com` again. The install command itself is unchanged.

> Every one of these files is generated from the same content modules and API contract that render these pages. They cannot drift from what the API serves.

## Report feedback from an agent

An agent that gets a wrong output or an unexpected error can report it to [POST /v1/feedback](https://paxalabs.com/docs/api/feedback) with the key it already calls the API with. It names the request with its `x-request-id`, sets `kind` to `model` for an output or `api` for an API problem, and adds an example when an output was wrong. The skill carries the same instructions.

Reports take no Idempotency-Key. Before sending a report again, an agent checks [GET /v1/feedback](https://paxalabs.com/docs/api/feedback-list) with `request_id`. The same list returns each report's `status` and the team's `resolution` note.

## OpenAPI

The same contract is published as an OpenAPI 3.1 document at [https://paxalabs.com/openapi.json](https://paxalabs.com/openapi.json), for API clients, client generators, and API directories. The two WebSocket endpoints are described in these docs alone.