Appearance
Quick start
This takes about ten minutes. At the end, an agent will have prepared a document from your template and asked to send it, and you'll have approved it.
1. Choose a workspace
Agent keys work on every plan, Free included. Sign in and use your personal workspace, or switch to a team where you're an owner or admin. Keys and templates each belong to one workspace, and the app opens in your personal one, shown as Personal. Make the template and the key in the same workspace. Below Teams & Platform, a workspace can have 3 active agent keys. API keys for your own software, and webhooks, come with Teams & Platform, which a team chooses under Settings → Plan & usage.
Confirm your email address if you haven't. Keys send invitations in your name, so the app asks for this first.
2. Have a template
Agents start documents from the workspace's templates. Use one you have, or make one:
- From the library. Open Library, choose a document or form, then Save as template. Its fill-ins stay blank, for each document. (Create document, then Save as template on the document's page, works too, but leaves a draft document behind, which you can delete.)
- In the editor. Write it with fill-ins such as
client_name, and give each signature field a role, such asclient. Then save it as a template. - From a PDF. Upload it and place its fields.
- Through the API. The agent can make one itself with
create_template, from text or a library entry. See Create a template.
3. Make an agent key
- Open API & agents in the sidebar, then New key.
- Name it after the agent, such as Sales assistant.
- On Teams & Platform, choose An AI agent under For. On other plans, every new key is an agent key.
- Under It may, tick what it needs: reading, creating templates and starting documents, and sending.
- Optionally limit Recipient domains (for example
example.com) and Sends a day. - Choose Create key and copy the key. It starts with
jd_live_and isn't shown again.
The key works only in the workspace you made it in, which the page names. Its row shows Agent key and Sends wait for approval. An agent can check where it is with get_workspace.
Keep the key secret
Store it in your client's secret settings or an environment variable such as JUSTDOCS_AGENT_KEY. Never put it in a file you commit. If it leaks, revoke it on the same page.
4. Connect your client
bash
export JUSTDOCS_AGENT_KEY=jd_live_…
claude mcp add --transport http justdocs https://tryjustdocs.com/mcp \
--header "Authorization: Bearer $JUSTDOCS_AGENT_KEY"json
{
"mcpServers": {
"justdocs": {
"url": "https://tryjustdocs.com/mcp",
"headers": { "Authorization": "Bearer ${env:JUSTDOCS_AGENT_KEY}" }
}
}
}json
{
"inputs": [
{ "type": "promptString", "id": "justdocs-key", "description": "JustDocs agent key", "password": true }
],
"servers": {
"justdocs": {
"type": "http",
"url": "https://tryjustdocs.com/mcp",
"headers": { "Authorization": "Bearer ${input:justdocs-key}" }
}
}
}For Claude Desktop, claude.ai, connector platforms and other clients, see Connect a client.
5. Ask for something
Try:
List our templates. Start a Mutual NDA for Acme Inc., effective today, and send it to Ada Lovelace (ada@example.com) as the client.
The agent calls list_templates, get_template and start_document (and create_template first, if there's no suitable template), then create_signing_request with send: true. JustDocs creates the request and holds the send. The agent is told:
text
Waiting for an owner or admin of the workspace to approve this. Nothing has been sent yet; check get_approval.6. Approve it
Open Approvals in the sidebar. Pending approvals are also listed on Home, with a link there. Check the title and the addresses, then choose Approve. JustDocs sends the request in the key creator's name, after checking the key and its limits again. The agent can follow along with get_approval and get_signing_request.
Ada gets the email, opens her private link and signs. When everyone has signed, the request is completed.
Next
- Hear about each step as it happens, on Teams & Platform: Track completion with webhooks.
- Call the same commands from your own code: REST API.
- Before you give an agent a key in production: Agent security checklist.