AI agent compliance for platforms
Make every agent ask first.
Cerata is legal compliance for AI agents. Today a company chooses to check its own agent. The services agents send through can require it: a dialer, SMS or email provider, job board or listing site can ask for a valid Cerata check before it delivers an agent's action, the way websites need HTTPS certificates and card networks run fraud checks.
The receiver protocol is documented and works over HTTPS today. The TypeScript receiver library is in private preview.
-
1 An agent plans an action A sales text to a lead in Tampa, Florida.
-
2 Cerata checks it Which laws apply, for who, where and what. ClearFlagHoldBlock
No token. The agent gets the reason and a fix before anything is sent.
-
3 Receipt and token A signed record, plus a token for this one action and this one service.
clearance-token eyJhbGciOiJFZERTQSIs… -
4 The receiver verifies
- Passed: Signed by Cerata
- Passed: Meant for this service
- Passed: The exact same action
- Passed: Not used before
No valid token, no delivery. If Cerata can't be reached, the receiver fails closed.
-
5 Delivered The text goes out. The token is spent.
One check, two sides of the network
Agents act through a small number of services. When one of those services requires a check, every agent that sends through it runs one. And the more agents that carry Cerata receipts, the easier it is for the next service to require them.
Services that deliver
Require a check before delivery
Dialers and voice platforms, SMS and email providers, job boards, listing sites and, later, payment processors.
Agents that send
Check first, carry the proof
Sales, marketing, recruiting and leasing agents, and the platforms thousands of businesses build them on.
Each service that requires receipts brings every agent that sends through it. More agents using Cerata make more services willing to require it.
For receivers: require a check before you deliver
You deliver the call, the text, the email or the listing. Require a compliance check for AI agents at your edge, and anything Cerata hasn't cleared for that exact action never leaves your network.
Less legal exposure and less abuse
Actions that break the rules Cerata covers are stopped before you deliver them, so fewer of them land on your network and in your inbox.
Your customers' agents get the fix first
A refusal isn't a dead end. The agent already has the reason and a safer version from its check, before it ever sends to you.
One shared, verifiable proof
Receipts and tokens follow receipt/v1, an open format published under CC0-1.0 and Apache-2.0. Verifying needs no API key.
No rules to build or maintain
You check one token, not a rulebook per state. We update rules as we learn of changes; each receipt records the rule version used. Rules cite their legal sources.
Services that can require a check, and what Cerata checks for them
- Phone dialers and voice platformsChecked todaySales calls: consent, calling hours, do-not-call
- SMS providersChecked todaySales texts under the TCPA and Florida rules
- Email providersChecked todayMarketing email under CAN-SPAM
- Listing sitesChecked todayRental listings under the Fair Housing Act
- Job boardsBeing verifiedPay ranges in New York City job posts
- Payment processorsComing soonPayments are on the roadmap, with no date yet
Status: the receiver protocol works over plain HTTPS from any language today. A TypeScript receiver library (Fetch API, Hono and Express middleware) that verifies tokens offline is in private preview. Only a clear check produces a token, and some actions, such as rental listings and job posts, don't answer clear yet. Require tokens first for the actions that can clear today.
For agent platforms: make every agent on your platform ask first
Thousands of businesses build agents on platforms like yours. Put the check in the agent's tool-calling loop once, and every agent built on it gets the reason and a fix before it acts, plus a receipt the services it sends through can accept.
Works today
- A hosted MCP server any agent can call, and the plain HTTP API from any language.
- A clearance token on every clear check, ready to pass to the receiving service.
- Private previewA Claude Agent SDK hook and an MCP gateway, on request.
Arranged with us
- Serving many client businesses from one platform: per-client keys, settings and billing.
- Volume pricing and platform terms.
- Help rolling the check out across your agent templates.
These aren't self-serve yet. We set them up with you through contact sales.
Talk to us about platform termsHow verification works
In plain words, from the agent's check to your delivery.
- The agent checks first. It sends the action to Cerata and names your service as the token's audience.
- Only a clear gets a token. It lives 15 minutes at most and is bound to that exact action and your service. Flag, hold and block get none.
- The agent sends to you with the same facts and the token in the
clearance-tokenheader. - You verify. Genuine, unexpired, meant for you, and the action hash matches what you're about to deliver. Signatures can be checked offline against Cerata's published keys.
- You redeem it once and deliver. A replay is refused. If Cerata can't be reached, refuse the action: fail closed.
// Refuse any call Cerata hasn't cleared for exactly these facts.
async function receiveCall(facts, token) {
if (!token) return [403, { error: { code: 'clearance_required' } }];
const action = { type: facts.action.type, ...facts }; // the action core
let res;
try {
res = await fetch('https://clearance-kohl.vercel.app/v1/verify?consume=true', {
method: 'POST',
headers: { 'Content-Type': 'application/json' },
body: JSON.stringify({ token, aud: 'dialer.example.com', action }),
signal: AbortSignal.timeout(5000),
});
} catch { res = null; }
if (!res || res.status >= 500)
return [503, { error: { code: 'issuer_unavailable' } }]; // fail closed
const out = await res.json();
if (!(out.valid && out.consumed)) {
const replay = out.reason === 'already_consumed';
const code = replay ? 'token_replayed' : 'token_invalid';
return [replay ? 409 : 403, { error: { code, reason: out.reason } }];
}
return [200, await dial(facts)];
}
The same receiver in Python, and every refusal code, are in the integration docs.
Questions
More in the receipts docs and the glossary.
Do we need a Cerata account to verify a token?
No. Verifying a receipt or token needs no API key, and the format is an open specification, so you can also check signatures yourself against Cerata's published keys. Talk to us about platform terms if you want to set up a relationship anyway.
Can an agent reuse a token, or use it for a different message?
No. A token is bound to one receiving service and a hash of the exact action that was checked. It lives 15 minutes at most and can be redeemed once. A changed message, another service or a second use is refused.
What happens if Cerata can't be reached?
The receiver fails closed: it refuses the action with issuer_unavailable rather than letting an unchecked action through. The agent can check again and retry.
Does a receipt contain our customers' data?
No. A receipt holds commitments (SHA-256 digests) of the action and facts, never the phone number, email, message or address. Anyone holding the facts can show they match.
Which actions can Cerata check today?
US rules for sales calls and texts, marketing email and rental listings are checked today. New York City pay ranges in job posts are being verified. Payments, public posts, reviews and other actions are coming soon. The coverage page in the docs has the detail.
We run an agent-building platform. Can every agent on it use Cerata?
Yes. Any agent can call Cerata over the hosted MCP server or plain HTTP today. Serving many client businesses, with per-client keys, settings and billing, and volume pricing are arranged with us through contact sales, not self-serve.
Is the receiver library available?
A TypeScript receiver library with Fetch API, Hono and Express middleware is in private preview. You don't need it: the receiver protocol is plain HTTPS and works from any language today.
Does a cleared check mean the action is lawful?
No. A check tells you what the rules Cerata covers say about one action. It is not a guarantee that the action is lawful, and Cerata is not a law firm.
General information, not legal advice. Cerata checks actions against the rules it covers and records the result. It is not a law firm, and a check is not a guarantee that an action is lawful. Requiring a check is each service's own choice.
Require the check. Every agent follows.
For the services agents send through and the platforms they're built on. Tell us what you deliver and how many actions a month.