AgentContract is for sending approved contracts from agent workflows. People still sign in the browser. Install the CLI
AgentContract
A For agent-run onboarding

Agents send contracts. People sign.

AgentContract lets an AI agent send an approved NDA, privacy acknowledgement, or contractor agreement. The recipient signs in the browser. Your app gets the signed PDF, hash, webhook, and audit trail.

Start with CLI View dashboard
Agents do not sign. Agents do not write legal terms. They only send approved packets.
CLI
cURL
TypeScript
Webhook
$ agentcontract marketplace-onboard \
  --to jane@example.com \
  --name "Jane Contributor" \
  --cc legal@example.com

sent agr_7ks9p2p8a4qv
signing_url https://agentcontract.to/sign/...
status waiting_on_recipient
Live Agreement
Specific Marketplace Privacy Acknowledgement Recipient: Jane Contributor Status: waiting on recipient signature
Send
Agent sent approved packetTemplate and required fields locked.
Sign
Recipient signs in browserESIGN consent and timestamp captured.
Store
Signed PDF archivedPDF bytes and SHA-256 hash saved.

Built for the agent workflows where paperwork blocks the next step.

What AgentContract does.

It gives agents a controlled way to send approved contracts. Humans stay responsible for signing, and your system keeps the record.

Approved template API
Recipient signing pages
Signed PDF storage
Webhooks and audit

Approved packets in. Signed records out.

Agents fill known variables, send signing links, track status, and report outcomes without drafting or changing legal language.

Specific Marketplace Privacy Acknowledgement

Built for repeatable contract sends.

Start with one agent sending one agreement. Use the same API and audit trail when the workflow repeats across contributors, contractors, and customers.

1 command to send a real contract from a local agent workflow.
SHA-256 hashes stored with signed PDFs for later verification.
API for creating agreements, checking status, fetching PDFs, and receiving webhooks.

Give your agent a send command.

The dashboard is for humans. The CLI and API are for agents, scripts, and backend workflows that need to send approved contracts.

quickstart 
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"
Read before sending Agents can inspect exact contract text and dry-run sends before an email goes out.
Track without the dashboard List agreements, read audit events, remind signers, cancel stale packets, and download PDFs.
Report failures immediately Feedback works before login, so install and auth issues still get captured.

Questions people ask first.

The most important distinction is simple: AgentContract lets agents send contracts. It does not make agents legal signers.

Do agents sign contracts?

No. Agents prepare approved packets and send signing links. Recipients and required human parties sign in the browser.

Can I use custom templates?

Yes. The API supports approved markdown templates, variables, required fields, metadata, and webhook URLs.

What gets stored?

Status, structured signer fields, audit events, signed PDF bytes, PDF hashes, and completion timestamps.

Is this only a dashboard?

No. AgentContract is CLI/API-first, with a dashboard for inspection, sender workflows, and API key management.

Let an agent send the next contract.

Install the CLI, log in with an email code, and give your local agent a simple contract-sending workflow.

curl -fsSL https://agentcontract.to/cli/install.sh | bash
Set up CLI Open templates