Case Studies

Where a reputation score could not help.

Three scenarios, traced step by step through the standards — each ending with what an authorization-based mandate provides that a trust score never could. Built from the protocol's own reference flows.

Interbank Settlement

A correspondent bank lets a counterparty's agent settle — without trusting its API

The situation

A regional bank receives payment intents from a correspondent's autonomous settlement agent. Compliance cannot approve software that acts on an unverifiable claim of authority — and cannot call the correspondent's own API to check, because that API is the very thing under question.

What PRAXIS changes

Registration and attestation become on-chain facts before a single intent is submitted. At settlement, the receiving system re-checks reliance itself — it never trusts a cached result. A payment outside scope, or under a revoked CPoA, structurally cannot settle.

The outcome

The compliance desk relies on a record it can re-derive independently — active, unrevoked, in-window, signature-verified at the instant of settlement — and a transparency-log receipt it can produce point-in-time, months later, for an examiner.

Illustrative scenario built from the protocol's interbank-settlement reference flow. Not a claim about a specific named institution.

The control flow

01Officer registers agent + issues CPoA (scope, ceiling, window)
02Agent submits payment intent referencing the CPoA
03Settlement re-runs the reliance check on-chain
04Verify scope, ceiling, cumulative limit, expiry — in order
05Settle + emit receipt to the transparency log

Every flow reaches settlement through an unbroken chain of checks — or terminates in a structured denial. Never a silent success.

Consumer Agent Commerce

A shopping agent transacts to a monthly ceiling — the merchant never sees a reputation score

The situation

A person authorizes an autonomous shopping agent with a monthly spending limit. The merchant's agent needs to accept the transaction — but should not have to evaluate the buyer-agent's reputation, and the buyer-agent should not get to decide for itself whether it is within its mandate.

What PRAXIS changes

Settlement decides — deterministically, from the CPoA and the intent alone. The scope grammar is default-deny: the monthly ceiling is enforced structurally, and an amount that would exceed the remaining limit is rejected, not flagged.

The outcome

The person keeps a receipt trail they can dispute against. The merchant relies on a cryptographic mandate rather than a trust score that could be farmed or purchased. Neither party depends on the other's goodwill.

Illustrative scenario built from the protocol's consumer-agent-commerce reference flow.

The control flow

01Person issues CPoA (scope = purchases, monthly ceiling)
02Agent negotiates purchase via the TAP-6 bridge
03Settlement runs the reliance check
04aWithin remaining limit + unrevoked → settle
04bExceeded or revoked → structured denial, no advisory mode

Every flow reaches settlement through an unbroken chain of checks — or terminates in a structured denial. Never a silent success.

Cross-Ecosystem Bridge

An external MCP agent is denied at the gate — and the denial is provable

The situation

An agent from another ecosystem initiates a Model Context Protocol handshake, requesting a task be relayed to a PRAXIS-registered agent. Its underlying mandate has expired — but the external ecosystem has no way to know that.

What PRAXIS changes

The bridge resolves the PRAXIS agent's metadata and runs a reliance check before any task relay happens. An expired or revoked CPoA produces a translated denial — in the external agent's own protocol format — with no settlement event emitted.

The outcome

Interoperability stops at exactly the same gate the payment flows stop at. The denial is fail-closed and legible on both sides; nothing silently succeeds because two ecosystems disagreed about state.

Illustrative scenario built from the protocol's cross-ecosystem bridge reference flow.

The control flow

01External agent sends MCP handshake
02Bridge resolves PRAXIS metadata (TAP-2)
03Bridge runs the reliance check
04CPoA expired → translated DENIAL (fail closed)
05No settlement event emitted

Every flow reaches settlement through an unbroken chain of checks — or terminates in a structured denial. Never a silent success.