More
For coding agents
The machine-readable surfaces of these docs and the API, for the AI agent writing your integration.
If a coding agent is writing your integration, it needs the same things you do, in a form it can read whole. Every page here is self-contained and served as plain Markdown.
| What | Where |
|---|---|
| Index of every page | /llms.txt |
| Every page in one file | /llms-full.txt |
| Any page as Markdown | Its URL with .md appended, for example /docs/quickstart.md |
| The API contract | https://api.trywool.com/v1/openapi.yaml, OpenAPI 3.1 |
The contract is the source of truth for routes, fields, statuses, and error codes. Generate a client from it rather than transcribing the reference.
A block for your repository
Paste this into the AGENTS.md or CLAUDE.md of a project that integrates WOOL:
## WOOL
- WOOL runs agents on a user's own website accounts, from prompts, after the user authorizes the app on a WOOL
connect page. Docs: https://trywool.com/llms.txt. Contract: https://api.trywool.com/v1/openapi.yaml.
- Connect a user with the auth link at https://connect.trywool.com/v1/oauth/authorize, exchange the code at
POST https://api.trywool.com/v1/oauth/token, and call executions with `Authorization: Bearer <access_token>`.
- Send `Idempotency-Key` on every execution you create. Poll the execution until `status` is COMPLETED or FAILED.
- `COMPLETED` means the run succeeded and `result` holds the answer. `FAILED` means it didn't; branch on
`terminal.status` for the reason and log `terminal.reason`.
- Never store or log the user's website credentials; WOOL never returns them.A run succeeded only when status is COMPLETED. Check that your agent never reports final_text from a
FAILED run as done.
Next steps
Point your agent at the Quickstart and the contract, and read Handling failures yourself so you can check its work.