Agentic CommerceThe question agentic commerce cannot answer is the question registers exist to answer. On the corridor, an AI agent never owns authority: it exercises a principal's recorded mandate — scoped, limited, expiring, revocable. Every event the agent triggers carries the mandate with it. Out-of-mandate actions are refused at the edge, not detected afterward. Responsibility, by construction.
Banks and platforms are convening panels on who is responsible when an agent transacts — because payment systems can only detect anomalies after the fact. Proof systems prevent them before.
Payment rails authenticate a user, then watch what happens. When an assistant initiates the transfer, the rail can say only that "the user authorized it" — it cannot show what the agent was authorized to do, up to how much, until when. Liability becomes a dispute between guesses.
A mandate is registered before any act: principal, agent key, scope, limits, expiry. Every event the agent triggers embeds the mandate reference and is signed. In-mandate, the principal is bound. Out-of-mandate, the register refuses. Dispute? One call returns the whole chain.
Registered by the principal before the agent acts — signed like every record, publicly checkable like every record, revoked like every record.
{
"mandate": "MDT-2026-0042",
"principal": "Manila Trade Inc",
"verified": true,
"agent_key": "ak_9f14…c2",
"scope": ["eCI issue", "ePN pledge"],
"limit": "PHP 250,000 / instrument",
"counterparties": ["3 verified buyers"],
"expires": "2026-12-31",
"status": "active"
}
Every lifecycle event written under this mandate carries mandate_ref: MDT-2026-0042 — the act and its authority are inseparable.
The same edge that refuses unlawful endorsements refuses out-of-mandate acts. The agent is not trusted and then monitored — it is structurally confined.
The act proceeds, signed, carrying mandate_ref. Like an officer's signature, the principal owns what their mandated agent did — and the record proves the mandate covered it.
An act beyond the value limit returns mandate_exceeded. The principal can raise the limit by registering a new mandate — the old one and its ceiling remain on the record forever.
Wrong class, wrong counterparty, expired, or revoked: the edge returns 403 mandate_revoked / mandate_expired / out_of_scope before the engine sees it. Detection is for systems without registers.
The registry is non-custodial — it never holds or moves funds, so it sits outside the payment-liability zone entirely. What it owns is the half nobody else can prove.
| Question | Where it is answered | Answer |
|---|---|---|
| Who bears the payment? | The bank rails | Unchanged — principal, bank, and platform, under their own terms. The registry holds no funds and takes no part in the money movement. |
| Was the agent authorized for this act? | The mandate record | Yes/no, to the second: scope, limits, expiry, status — public, signed, revocable. |
| Was this event within the mandate? | The event itself | Every act embeds its mandate reference and is signed. In-mandate → principal bound. Out-of-mandate → refused, never written. |
| Who acted after revocation? | The revocation timestamp | Anyone who tried is provably not the principal's agent anymore — attribution without ambiguity. |
| Is this agent trustworthy over time? | The rating layer | Agents build their own signed performance records — earned, bounded, recent — the same evidence discipline as counterparties. |
The trust layer agents need for reading the registry is in production today. The mandate layer for acting is published as Spec v0.9 — the enforcement machinery it builds on is already the registry's core.
The build order is small by design: officer authority, refusal at the edge, signing, and the rating layer already run. A mandate is officer authority, scoped and delegated.
Any agent, from any maker, can transact on the corridor — because trust is answered by the register, not by the agent's brand. Start reading today; the mandate spec is public and stable.
/llms.txt for orientation, the verify endpoint for checks, the capabilities manifest for discovery. No account, no key.
The MCP console and REST console expose the real enforcement surface read-only — including the refusal gallery. Your agent should learn what the register refuses.
Live on the commerce scope today: register a mandate, then place orders with your agent key — every order carries its mandate reference — the beginning of an attributable, provable trading history.