GateCheck Routeability Card
A compact buyer card for deciding whether a paid x402/MCP route is worth a bounded test before agent spend.
Buyer Decision
Public metadata is sufficient for a bounded paid test, but not for broad autonomous routing.
What the unpaid 402 proves
- the seller exposes an x402 payment challenge
- the buyer can inspect price, asset, and resource before payment
- the route can be rejected before spending if metadata is missing
What it does not prove
- successful settlement
- marketplace approval
- security certification
- downstream task completion
Remaining risk
- paid response may still fail after settlement
- seller output quality is not proven by payment metadata
- directory listings may lag the seller's current manifest
Stop conditions
- price, asset, or resource changes unexpectedly
- OpenAPI or MCP metadata conflicts with the x402 challenge
- seller claims approval, compliance, or security proof without source evidence
Expected after-payment proof
Required fields: resultStatus, sourceUrls, paidResource, receiptHash, claimBoundary
accept only if the paid result matches the resource, price, and task boundary inspected before payment
Claim boundary: GateCheck routeability cards use public metadata and unpaid 402 challenge evidence. They do not sign, spend, settle, contact sellers, certify security, or prove marketplace endorsement.
JSON | Markdown | Product card