Every rail — x402, MPP, agentic acquiring — moves an agent's money. None of them answers the question that comes first: was this agent allowed to spend it? KYE Protocol™ answers it per call, before the charge, and seals the proof after it.
$ curl -X POST https://agentpayment.dev/v1/authority-check ← 402 Payment Required (offer minted — admissibility already ran) $ curl … -H "PAYMENT-SIGNATURE: …" ← 200 OK { "verdict": "allow", // or a refusal you can show an auditor "evidence": { "ref": "…", "verify_url": "…" } }
A wallet is capability, not authority. Money moving proves nothing about whether it should have moved. No authority, no finality — the doctrine of the Authority Finality™ category, applied to agent commerce: admissibility is decided before the payment exists, and the decision seals locally even when the network doesn't.
A payment credential never substitutes for admissibility. The offer itself carries the proof that the governed decision ran first.
One call: mandate + context in, ALLOW/DENY + sealed evidence reference out. Priced per call, paid over the same rails your agent already speaks.
Drop-in middleware for any endpoint charging agents: the admissibility question is asked — and answered — before your 402 flow ever runs.
Agnic, AP2, OAuth grants, DIDs — every mandate format resolved against the principal's real delegated authority, with a confidence-laddered verdict.
Per-transaction sealed proof of who authorised what, under which purpose, within what limits — the receipt that survives a chargeback and satisfies an auditor.
Budgets, top-ups, purpose-scoped spend, live accounting — the authority ledger is ours; custody stays with regulated partner instruments.
Agents selling to agents: governed offers, gated purchases, both sides sealed. Plus continuous reconciliation — declared authority to settled statement.
Your x402/MPP endpoint takes an agent's money today and finds out later whether it should have. The gate answers first.
Agnic mandates, AP2, OAuth grants, DIDs — one intake contract resolves them all against the principal's real delegated authority.
Budgets, purpose scopes, and approval thresholds enforced at the moment of spend — not reconstructed for the auditor afterwards.
A disputed agent purchase resolves with the sealed authority chain, not an email thread.
Evidence exists from the moment of the action — nothing is reconstructed after the fact.
x402 and MPP are consumed exactly as they are. Your settlement stack does not change.
A network failure degrades payment, never the decision — the verdict path has no remote dependency.
A sample flow — illustrative payloads, the real order of operations. Click each step.
Two things every governed payment leaves behind — the receipt your dispute team files, and the approval your principal actually taps.
No invented percentages — each line names the work the mechanism removes.
A chargeback response is assembled from the sealed chain — the authority, approval, and receipt were bound at the moment of sale, so the dispute answer already exists.
Mandate adjudication across Agnic, AP2, OAuth, and DID formats collapses into a single intake — the per-format integration matrix is work you never build.
x402/MPP settlement stays untouched. The adoption cost is the gate call, not a payments re-platform.
Every DENY before an offer exists is a refund, a support ticket, and a reconciliation break that never happens.
| Alternative | What it answers | What it structurally cannot |
|---|---|---|
| Payment rails (x402 · MPP) | How value moves between agents | Whether it should — a rail is neutral about admissibility. We consume them; they distribute us. |
| Wallets & mandate issuers | That an agent holds funds or a signed intent | Adjudication against the principal's real, current delegated authority — an issuer can't referee its own mandates. |
| Policy & spend dashboards | What happened, after it happened | Stopping the inadmissible spend before the charge exists, and proving the verdict offline afterwards. |
| AgentPayment.dev | The pre-payment verdict + the sealed, offline-verifiable evidence — from the neutral layer every rail, wallet, and dashboard needs and none can be. The moat compounds: every seller brings buyers, every transaction seals evidence only this layer can issue, and the verdict path's zero network dependency is a property a SaaS control plane cannot copy. | |
Early access is open for design partners — sellers gating agent purchases, platforms resolving mandates, and enterprises that need agent spending to survive an audit.