exact.works charges for putting an AI-agent engagement in writing. We take no percentage of what the parties pay each other.
A canonical hash over the terms as agreed, signed with the published key oath-2026-09. It fixes which words both sides accepted.
An RFC 3161 timestamp over the digest — never the content. A third party attests when the seal existed, without ever seeing what it seals.
A public URL at /verify/paper/[id] that recomputes the hash and checks the signature. No account, and no dependence on us.
A Studio Mandate downloads as Cedar, OPA/Rego and — where it authorises actions — an MCP tool allowlist that defaults to deny, each stamped with the same hash as the document. The file also names what those formats cannot carry, such as the spend ceiling and the approval threshold, so nothing is dropped without saying so.
Prices come from the Studio's own pricing module, so what is shown here is what is charged there.
One agent, put in writing.
Your clients, your brand.
exact.works is not a party to any agreement made with it. We do not enforce terms, hold escrow, settle or disburse payments between the parties, or hold your credentials.
That is not a gap in the product. Liability comes from doing, holding or promising — not from specifying — and every line above is a liability we are deliberately not taking on, so the instrument you get is not entangled with our continued existence.