Drafting to deployment

How exact.works Works

Present the standard form. Customise the terms. Seal what was agreed.

Start an agreement

The SAISA

The standard form service agreement for AI-agent work — two parties, and exact.works is not one of them

MCP

exact.works is reachable as an MCP server itself

The Complete Flow

Step 1Start Here

Present the SAISA

Start from the Standard AI Service Agreement — a two-party form written for AI-agent work, between the principal and the AI provider. No blank page, no bespoke contract for every engagement.

  • A standard form, read before either side commits
  • Two parties: principal and AI provider. exact.works is not one of them
  • Schedules for the parts that vary by engagement
Read the SAISA
Step 2

Customise the terms

Work through the terms that actually differ deal to deal — scope, completion criteria, which actions the agent may take, which need a human first, and what happens if something goes wrong.

  • Prohibited actions, and actions that require human confirmation
  • Liability allocation and IP terms agreed up front, not argued later
Open the Studio
Step 3

Seal what was agreed

A canonical hash is taken over the terms as agreed. The seal fixes exactly which words the parties accepted — nothing more, nothing less.

  • Canonical hash over the agreed terms
Step 4

Download the policy

A Mandate bought in the Studio compiles to policy files you can run: Cedar, OPA/Rego, and — where the Mandate authorises actions — an MCP tool allowlist that defaults to deny. Each carries the same hash as the document, so the policy and the agreement cannot disagree.

  • Downloaded at checkout, beside the PDF.
  • Prohibited actions become forbid/deny rules; the irreversibility ceiling becomes the gate
  • The file also lists what these formats cannot carry — the spend ceiling, the approval threshold, expiry — so nothing is silently dropped
Step 5

Refer out

The engagement needs providers and tools. We point at options sourced from the Agent Index — a pointer, never a recommendation. The parties elect what they use, and contract with them directly.

  • Provider options sourced from aidispatch
  • A pointer, never a recommendation, and never a covenant about what a provider will do
  • Their tenancy, their accounts, their credentials — we never hold them
The Agent Index

What we don't do

exact.works is not a party to any agreement made with it. We do not enforce terms, hold escrow, settle payments, or hold your credentials. We never operate the service.

Are you the AI provider?

The SAISA has two sides, and the same flow runs from yours. Here is what the form does for the party doing the work.

The provider's side

Ready to draft one?

Every AI agent doing real work needs a service agreement. Start from the standard form and change only what your engagement actually needs.

Start an agreementRead the SAISA