/llms.txt and
/llms-full.txt machine indexes.
What Atlas is
The e-signature platform where AI agents are first-class senders. One API/MCP call runs the full signing lifecycle: store a document, detect fields and parties, route for signature in order, return a signed PDF plus a verifiable audit trail. Review-first: agents prepare, humans approve.Surfaces
| Surface | Endpoint | Protocol | Auth |
|---|---|---|---|
| REST API | https://api-atlaswork.vercel.app/api/v1 | HTTP/JSON | API key (bearer) |
| MCP server | https://api-atlaswork.vercel.app/api/mcp | JSON-RPC 2.0 | API key (bearer) |
| OpenAPI spec | https://docs.atlaswork.ai/openapi.json | OpenAPI 3.0 | none |
Start here
- Quickstart — authenticate and make a first call.
- Core concepts — envelopes, participants, fields, templates.
- Envelope lifecycle — states and transitions.
REST
- Authentication — API keys; one auth method per prefix.
- Idempotency — safe retries on every write.
- Webhooks — signed, retried lifecycle events.
- Errors — the
{ code, message }envelope and codes. - API reference — generated from the live spec.
MCP (for agents)
- MCP overview — why MCP, endpoint, auth.
- MCP transport — JSON-RPC envelope and error codes.
- MCP tools — the signing tool set.
Hard rules for integrations
- Review-first. A send is not final until a human approves it. Don’t assume an agent can complete a send unattended (templates excepted).
- Idempotent writes. Reuse one idempotency key per logical operation; the SDK and MCP server supply keys automatically.
- Branch on
code, notmessage. Errorcodes are stable; messages are for humans. - Verify webhook signatures over the raw body before trusting a payload.
- The generated reference is canonical. When in doubt, read the spec at
https://docs.atlaswork.ai/openapi.json(also served by the API at/api/openapi.json).