For developers & AI builders
Documents as infrastructure. Agents with boundaries.
A REST API, signed webhooks and an MCP server let your code and your agents prepare documents and send signing requests, with scoped, expiring keys and an owner's approval before an agent's request goes out. Agents never sign for a person.
Free plan, no card neededRecipients always sign for free
Agent request — held for approval
intake-agent (agent key)Avery Founder, admin
- Mutual NDAPrepared
- W-9 RequestPrepared
- Prepared
- Approved
- Sent
01 — Sound familiar
Where the paperwork gets stuck.
API, webhooks and an MCP server, with scopes and approvals. Here's what usually gets in the way, and what changes.
Signing is the step you can't automate
Your system drafts the document, then a person downloads it, uploads it somewhere else and sends it.
Agents need boundaries
Giving an agent an API key usually means giving it everything that key can do.
Status lives in someone's inbox
Your system learns a document was signed when somebody remembers to update it.
02 — How it works
How developers & AI builders use JustDocs.
Four steps, from the first draft to the signed copy on file.
- 01
Create a scoped key
In a team workspace, create an API or agent key with only the scopes it needs, an expiry, the recipient domains it may send to and a daily limit.
- 02
Call the API or connect over MCP
Your code uses the REST API; an AI agent connects to the MCP server with its key and uses the same commands.
- 03
Approve what agents send
An agent's signing request waits for an owner's or admin's approval before anyone is invited.
- 04
Listen for events
Signed webhooks report requests sent, opened, signed and completed, with retries and a delivery log.
03 — From the library
Documents ready to start from.
Keys work with the same documents and templates as the app, the library's included.
-
Written document Mutual NDA Two-way confidentiality for early conversations.
-
Official form W-9 Request The IRS Form W-9, ready for your payee to complete and sign.
-
Packet Contractor Onboarding Packet Consulting agreement, W-9 and a policy acknowledgment, sent together.
04 — Built in
Made for the way you work.
The same workspace for every document: write, upload, send, sign and keep.
- Scoped, expiring keys
Keys are stored hashed, scoped to what they may do, set to expire, and can be limited to recipient domains and a daily number of sends.
- Safe to retry
Calls with the same idempotency key don't send twice, so a retry after a timeout is harmless.
- Agents never sign
Agents can prepare and send within their scopes; a person's signature is only ever made by that person.
- Every action on the record
Each call records which key and which person acted, beside the request's own events.
05 — Questions
Developers & AI builders questions.
Which plan includes the API?
API keys, webhooks, agent keys and the MCP server come with the Teams & Platform plan, at $59 a month or $590 a year.
Can an AI agent sign a document?
No. Agents can draft, prepare and send within their scopes. Signatures are always made by people.
How are agent sends approved?
A signing request from an agent key is held until an owner or admin of the team approves it, and nobody is invited before then.
Is there an MCP server?
Yes. Agent keys connect to the MCP server at /mcp and use the same commands as the API, with the same scopes and limits.
Are webhooks signed?
Yes. Each delivery is signed so you can verify it came from JustDocs, retried when your endpoint fails, and kept in a delivery log.
For developers & AI builders
Your first document, sent in minutes.
Start free with 3 completed requests a month, no card needed. The people you send to always sign for free, on any device, without an account.