# GateCheck Routeability Card

Target: `https://seller.example/mcp`
Observed: `2026-05-24T13:46:00Z`
Decision: `route_with_limits`

## 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

- `resultStatus`
- `sourceUrls`
- `paidResource`
- `receiptHash`
- `claimBoundary`

Acceptance rule: 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.