Skip to main content
Atlas runs the entire signing lifecycle — store a document, prepare it, route it to one or more parties in order, and return a signed PDF with a verifiable audit trail — behind one clean API and MCP surface. Agents prepare, humans approve. The developer surface is the product. Everything you can do in the dashboard you can do programmatically, with review-before-send, idempotent writes, and status built in.

Quickstart

Send your first envelope in a few minutes.

Core concepts

Envelopes, participants, fields, and the lifecycle.

API reference

Generated straight from the live OpenAPI spec — always current.

MCP server

The signing lifecycle as a tool set for AI agents.

​
How Atlas is documented

These docs are split by audience, mirroring the product’s surfaces:
  • Guides — task-oriented walkthroughs for building on the REST API.
  • MCP server — the JSON-RPC tool surface for AI agents. Hand-written, because MCP is not described by OpenAPI.
  • API reference — generated from the API’s OpenAPI document (download). The reference is never hand-maintained: adding a route to the API makes it appear here.
The API reference is rendered from the API’s generated spec. If an endpoint looks new or changed, that’s the source of truth catching up — not a docs edit.

​
The three surfaces

SurfaceAudienceAuth
REST API (/api/v1)DevelopersAPI key
MCP server (/api/mcp)AI agentsAPI key (JSON-RPC 2.0)
Signer links (/api/signer)Recipients (no account)HMAC envelope token
Each surface has exactly one authentication method. See Authentication for details.