Agents send contracts. People sign.
Let agents send NDAs, contracts, and PDFs. Humans sign in their browser. You get the signed PDF and a webhook.
Set up AgentContract for this machine.
Run:
curl -fsSL https://agentcontract.to/cli/install.sh | bash
agentcontract login --email <my-email> --api-url https://agentcontract.to
agentcontract skill
If you do not know my email, ask first.
For any contract send:
- ask for recipient email, recipient name, and template
- run agentcontract templates --json
- read the chosen template before sending
- run the send with --dry-run --json
- show me the dry-run JSON and wait for approval
- only send after I approve
- return the agreement id, signing URL, and status
Never draft or edit legal terms.Send
Sign
Store
Built for the agent workflows where paperwork blocks the next step.
What AgentContract does.
Agents send templates or PDFs. People sign. Your app gets the result.
Reviewed documents in. Signed PDFs out.
Agents can fill template variables, submit custom Markdown, or send a PDF you give them. Your calling workflow is responsible for restricting and approving the terms; a human signs.
Acme Marketplace Privacy Acknowledgement
What you get back.
After someone signs, your app can fetch:
Give your agent a send command.
Humans use the dashboard. Agents use the CLI or API.
curl -fsSL https://agentcontract.to/cli/install.sh | bash
agentcontract login --email you@example.com --api-url https://agentcontract.to
agentcontract skill
agentcontract marketplace-onboard --to jane@example.com --name "Jane Contributor"FAQ.
AgentContract lets agents send contracts. It does not make agents legal signers.
Do agents sign contracts?
No. Agents send documents selected by your workflow. People review and sign them in the browser.
Can I use custom templates?
Yes. You can use templates, variables, required fields, metadata, and webhooks.
What gets stored?
Status, signer fields, events, signed PDFs, hashes, and completion time.
Is this only a dashboard?
No. Agents can use the CLI or API. Humans can inspect sends and manage keys.
Why not just use DocuSign or Dropbox Sign?
You probably can. AgentContract is shaped for agent workflows and includes a dry-run mode plus revocable API keys. Revoking a key blocks future authenticated requests; it does not cancel agreements already sent. If your sending is human-driven, DocuSign is fine.
What happens if my agent goes haywire and sends 500 NDAs?
AgentContract does not currently enforce per-key send caps. Put approval and budget limits around automated sends, monitor agreement creation, and revoke the key to stop future requests. Cancel any already-sent agreements separately.
Can the agent change the terms of the contract?
The API and CLI can send custom Markdown as well as approved templates, so your workflow must restrict agents to reviewed language when that is required. Use template-only policies and human dry-run approval in the calling system.
How does the recipient know this is real and not a phishing email?
They open a browser signing page on agentcontract.to. It shows the document, sender, and fields. It feels like any other e-signature flow.
Is this legally binding?
A signed PDF from AgentContract is like one from any e-signature tool. Enforcement depends on the contract and your jurisdiction.
What happens if the recipient never signs?
It stays in waiting status until you cancel it or send a reminder. You can do both from the CLI.
Do you train on documents sent through this?
No.
Is there a free tier?
Free during beta.
Can I self-host?
Not yet.
Let an agent send the next contract.
Install the CLI. Log in with an email code. Let your agent send the document.
curl -fsSL https://agentcontract.to/cli/install.sh | bash