# developer.law for Agents

Give your coding agent a legal execution layer — so the contract stops being the slowest step between signing and getting paid.

Source: https://developer.law/knowledge/for-agents · Published 2026-08-13 · Story LLP

## The plain-English answer

You have automated almost everything between "we're doing this" and "the money landed." Tests run themselves. Deploys run themselves. Invoices go out on a schedule. Then there is one step in the middle that still involves you copying a Word document into an email at 11pm — the contract. It is the slowest thing in your pipeline and it is the thing standing directly between a signed engagement and a paid invoice.

The reason it never got automated is that it was never yours to automate. Legal work sits inside a law firm, behind a human, on a different clock.

Story is a law firm that exposes a Model Context Protocol (MCP) surface. Your agent — Claude Code, Cursor, an internal one you built — connects to it the way it connects to any other MCP server. Once connected, it can read your organization's legal state, draft from lawyer-approved templates, route documents to counterparties, and hand off to a Story attorney when something needs actual judgment.

This is not an agent that practices law, and it is not a document generator you could have written yourself. Your agent can already produce a contract-shaped file. What it cannot do alone is run a multi-party transaction — correct template for the deal, right counterparty on the right routing, privilege boundaries intact, audit trail that holds up, a licensed attorney on the other end of the escalation. That is the part Story does.

## The four things your agent can do

1. **Read your organization's state.** Company context, matter status, which agreements exist, what is outstanding.
2. **Draft from approved templates.** A draft built from the same lawyer-maintained process a Story attorney would run, populated with your actual deal terms.
3. **Route counterparties.** Send the right document to the right person with role-aware visibility controls.
4. **Escalate to a real attorney.** When a redline needs a judgment call, it hands off to Story counsel instead of guessing.

## The four things your agent cannot do

These are hard limits enforced at the platform, not guidelines an agent is asked to follow:

1. **Execute a signature.** E-signature requires human identity verification. Your agent can get a document all the way to signature-ready; a person signs it.
2. **Escalate a draft's visibility.** Moving a document from internal to client-visible is a human decision — it is often a privilege decision.
3. **Approve what a counterparty sees or discloses.** Counterparty comments and disclosures require human approval.
4. **Reach outside your organization.** Access is scoped to your org at the middleware layer. Bulk data room export is also off the table.

## How it connects

1. **Authenticate** — with a Story-issued API key, scoped to your organization.
2. **Connect** — point your agent at the Story MCP endpoint.
3. **Orchestrate** — run legal workflows with policy-aware routing.
4. **Escalate** — bring in Story counsel when a call needs human judgment.

```json
{
  "mcpServers": {
    "story": {
      "url": "https://backend.story.law/mcp/story-agent",
      "type": "http"
    }
  }
}
```

Every action an agent takes is logged in an audit trail that distinguishes programmatic actions from human decisions.

Story is a law firm, and attorney-client privilege is real here. But privilege depends on context and role, and it is not automatically conferred on everything an agent touches. Agent access does not by itself create an attorney-client relationship, and no part of this surface gives legal advice without attorney review. High-impact and privileged calls escalate to Story counsel. Availability and constraints also vary by jurisdiction.

## Pricing

Agent access is available to developer.law subscribers on the Consultant tier and above:

- **Solopreneur — $49/mo** — lawyer-built client agreements and e-signature, without agent access.
- **Consultant — $69/mo** — agent access included, plus client agreements and subcontractor paper.
- **SMB — $99/mo** — the same, across unlimited clients and subcontractors.

See https://developer.law/#packages for current plan details.

## FAQ

**Can an AI agent sign a contract for me on Story?**
No. Executing a signature requires human identity verification and cannot be performed by an agent. An agent can prepare a document, route it to the right counterparty, and tell you when it is ready — a human still signs it. The same limit applies to escalating a draft's visibility, approving what a counterparty sees, and bulk-exporting a data room.

**How does an agent connect to Story?**
Story exposes Model Context Protocol endpoints. Your agent authenticates with a Story-issued API key scoped to your organization, then connects to the Story MCP endpoint the same way it connects to any other MCP server.

**Which developer.law plans include agent access?**
Agent access is available on the Consultant tier and above. It is not included in the Solopreneur plan.

## Related

- https://developer.law/knowledge/what-is-background-technology — what your agent should be carving out of every client agreement it drafts
- https://developer.law/knowledge/what-is-acceptance — the clause your agent checks before it tells you to invoice
- https://developer.law/knowledge/what-is-an-msa — the master terms an agent drafts from
- https://developer.law/knowledge/what-is-an-sow — the per-project document an agent generates most often