03 · Architecture
Six layers. One normalized instruction.
Adapters translate x402, MPP, and AP2 into a common settlement instruction. The engine never sees a privileged native format — only the normalized form.
- L1Client & Agent SDKThin construct-and-sign surface for agents and resource servers.
- L2Standard Adaptersx402 · MPP · AP2 → normalized settlement instruction.
- L3Policy EnginePermit, deny, or escalate against the grant chain.
- L4Identity RegistryCredentials, delegation, revocation, reputation tiers.
- L5Credit FacilityCapital-isolated envelopes and loss waterfall.
- L6Settlement & RailsVerification, routing, fee split, payout instructions.
04 · Settlement path
Delivery before finality. Exposure bonded to the node.
An agent cannot wait for block confirmation between tool calls. Nodes guarantee payment at verification and carry exposure until settlement confirms — which is why bonds scale with throughput.
Request
Resource server returns payment requirements: scheme, amount, rails, nonce, window.
Pre-flight
Policy engine walks the delegation chain and reserves budget before any payload is signed.
Verify
Node checks signature, credential status, nonce, grant, and funding adequacy.
Deliver
Service is served immediately. The node carries confirmation-window exposure.
Settle
Rail executes; base fee burns; priority accrues to the node; receipt lands on the audit bus.