The agent asks for one thing.
Your product's agent proposes an action: a merchant, an amount, a reference. Nothing has been approved yet, so nothing about it can be trusted.

A person approves the limits once: what the agent may do, what it may spend, and where it has to stop. Every action after that is checked against those limits before it runs, and signed into one record, so authority becomes something the agent carries and anyone can check, instead of a promise a platform makes about it.
Spent
€412.00
Remaining
€88.00
Actions
8
Refused
3
Propose an action
From what the agent proposes to what anyone can check, without trusting the platform or us.
Your product's agent proposes an action: a merchant, an amount, a reference. Nothing has been approved yet, so nothing about it can be trusted.
The customer sees the exact bounds and signs them with a passkey. Not a blanket permission and not a checkbox: one signature over the limits that apply from here on.
Passkey approval happens on the approval surface, or inside your own app. The bounds are what get signed, not a policy label.
The agent acts. Attesso decides against the signed bounds, allows one execution, and records what was asked, what was allowed, and what happened.
No executor calls and no money movement. Your payment provider and your rail stay where they are.
The record carries its own signature and digest. A client, an auditor, an insurer or a regulator verifies it against published keys, offline, years later.
From the first approval to every action after it, one record. The same mandate, the same decision, the same evidence. Only the execution mode and the rail change.
The agent requests one specific purchase. Attesso allows or denies it against the approved bounds.
A recurring mandate carries a per-period budget and stays active until its term runs out.
Future-dated authority stays scheduled until its start time arrives, then becomes active.
The integrator moves the money on its own rail. Attesso reserves the amount against the mandate first.
Full and partial refunds are appended to the signed record as labelled external reports.
Every state change lands in one signed evidence bundle that anyone can verify.
Every layer of an agent's action already has an independent record. The itinerary lives with the airline, the payment with the network. Permission is the last layer still held by the platform's word. Attesso turns it into a record: who allowed what, which action was decided, and why, in a form a third party can verify without trusting the platform or us.
See how the protocols compareNo consumer app. No consumer account. One approval, then every action is checked and signed behind your flow.
See the embedded modelThe customer defines the permission. Attesso verifies the agent's request and produces signed evidence that proves it. The integration is plain HTTPS: create a mandate, submit the proposed action, commit the outcome.
See the implementation pathEvery figure below came from a run whose log we can show. Where a rule costs us tokens instead of saving them, that is in the table too.
6 of 6
worked actions blocked
With enforcement on, no run wrote the file; with it off, all six did. Same task, same model, six runs per arm.
+9.7%
median tokens to watch
Observe mode records every verdict without refusing, at identical call counts. The cost of looking is close to nothing.
193 of 2,070
tool calls were duplicates
In one long agent session. An inventory of repeats, an upper bound, not a saving until a measured run says so.
Refusing an action the agent needed costs tokens, not saves them: +66% median on a short task, because the model spends a turn handling the refusal. We quote no savings percentage we have not measured, which is why the audit report shows your counts and not ours.
How Bounds worksThe customer sets the limit. The agent stays inside it.
Signed evidence records what was approved and what the agent requested.
Add agent authorization without replacing your existing payment rail.
A traveler approves a bounded mandate before boarding: this route, this cabin, up to this price, until Friday. When the airline moves the flight, the booking agent rebooks inside exactly those limits, and every decision comes back as signed evidence.
Every step, from the customer's approval to that payment, comes back signed.