MCP & Agentic Commerce · T630 · x402 spend evidence → VPSF claims

x402 Spend-Evidence VPSF Bridge

Takes the assembled x402_spend_evidence pack produced by the x402-spend-evidence chain (EIP-712 digest recompute → ECDSA signer recovery → domain/nonce/window check) and renders it as a VPSF SettlementReceipt + DelegationGrant Payment Claim pair, JCS-hashed (RFC 8785, SHA-256) per draft-vauban-x402-vpsf-algebra-01, joined by a Conjunction composite. The output is accepted by any VPSF-conformant verifier, including this suite's own VPSF Claim Algebra Verifier (T629), and this page runs that same round-trip check inline, offline.

⚠ This tool renders an evidence bundle, not a settlement proof. The x402-spend-evidence chain verifies an EIP-712/EIP-3009 authorization's signature and domain/window correctness; it never observes on-chain settlement. The claims below assert "this authorization was well-formed, correctly signed, and not self-reported as replayed," never "funds moved" or "this authorization reached finality." For a finality classification, use art-492 · Settlement Finality Classifier separately.
x402 VPSF RFC 8785 JCS Zero PII Client-Side
🔒 All inputs are processed locally in your browser. No data is transmitted. Do not enter real personal data — use synthetic or anonymised inputs only.

This claim pair asserts that the EIP-712 digest recomputed correctly, the ECDSA signature recovers to the address the payload claims signed it, the authorization's domain (chainId/verifyingContract) matched what the caller expected, the authorization sat inside its validAfter/validBefore window at check time, and the nonce was well-formed and not self-reported as already used; it carries no claim about on-chain settlement, on-chain nonce uniqueness (enforced only by the token contract), or STARK/SNIP-12 signature validity, since draft §6.2 places cryptographic-evidence verification out of scope for algebra conformance and this bridge carries none of the pinned schema's Starknet-specific primitives (see the Evidence Scheme note below).

1 · x402_spend_evidence pack (JSON) · §8 assembled shape, the chain's output
This is the object shape shown in the chain composer's "Assembled x402_spend_evidence" panel. A caller assembles it from the three chain steps' own responses (art-590 digest recompute, art-591 signer recovery, art-592 domain/nonce/window check); the chain execution model does not pipe one step's output into the next automatically.
2 · Origin execution_hash · from the terminal chain-step artifact (e.g. art-592's execution_hash)
Ties the emitted claims' evidence back to a specific, independently re-derivable AINumbers ChainGraph execution (executionHash(policy_parameters, output_payload) from _hash.mjs); never trusted, only carried through and displayed.
3 · Business context · AgentCore cookbook field names (ApprovalGrant / Receipt), verbatim
Field names borrowed verbatim from the OpenAI×AWS AgentCore Payments x402 cookbook's ApprovalGrant{approval_id,request_id,resource_url,purpose,maximum_amount,approved_by,approved_at,expires_at,currency} / Receipt{receipt_id,amount,currency,network,reused} shapes. None of these are present in the chain's crypto-only output, so they are supplied here as caller-declared context, carried through unverified into the claims' extension fields.