GateCheck ยท paid-agent routeability

Check your paid agent route before buyers hit it.

Before you send buyers, agents, marketplaces, or directories to a paid x402/MCP route, know whether it can be found, priced, understood, and safely tested.

Run via API See sample report See routeability card

How GateCheck works

1Paste a paid routeUse an x402 endpoint, MCP server, OpenAPI URL, marketplace page, or seller homepage.
2Check public evidenceInspect discovery files, OpenAPI/MCP metadata, pricing copy, launch claims, and unpaid 402 challenge behavior.
3Get a decisionReturn route_with_limits, ask_for_proof, fix_first, or do_not_route.

Built for the places paid agents look first

CDP BazaarMetadata readinessDescription, schema, resource URL, price clarity, and settlement-indexing prerequisites without claiming indexing.
xpayAgent filesllms.txt, agents.txt, product-card markdown, skill docs, and clean per-call pricing language.
MCP directoriesServer cardMCP endpoint, tools, auth/payment boundary, OpenAPI links, and namespace-safe metadata.
Answer enginesCitable factsCanonical HTML, JSON-LD, sitemap entries, OpenAPI, MCP cards, and proof samples for ChatGPT, Grok, Gemini, Google, and Bing.

Trust without overclaiming

GateCheck proves what was publicly observed: routes, schemas, metadata, price signals, unpaid 402 behavior, timestamps, and claim boundaries. It does not prove settlement, marketplace approval, security certification, buyer adoption, revenue, or downstream task quality.