GateCheck
Validate the paid route, unpaid 402 behavior, OpenAPI, MCP card, pricing, discovery files, and claim boundaries before buyers or agents hit the endpoint.
Open GateCheckLarryBuildsAI · MCP/x402 public-readiness evidence · packaged for marketplace review · Agent Verification & Security
Know if a paid agent API is safe to test before anyone spends.
GateCheck checks the public route, price clues, unpaid 402 response, OpenAPI/MCP metadata, and launch claims, then returns a plain-English report: proceed, fix first, ask for proof, or do not route.
Use it before a marketplace review, xpay wrapping, MCP directory submission, X launch, or paid-agent traffic so buyers see the route, proof, stop condition, and expected receipt before money moves.
No live web form yet: use the API or inspect samples. No keys, cookies, wallets, or customer data needed for public-metadata checks.
RouteabilityBuyer-readable proof for whether a paid x402 route should be tested, skipped, or stopped.
$9–$49Launch packs with listing copy, FAQ, checklist, and approval notes.
402Probe 402 payment metadata without signing or spending.
0 secretsPublic metadata only by default; no keys, cookies, wallets, or customer data required.
What you get in the readiness report.
A normal buyer or agent should not need protocol archaeology. GateCheck turns scattered launch evidence into a decision artifact they can inspect before spend.
Live surfacesEndpoint, OpenAPI, MCP metadata, x402 manifest, llms.txt, agents.txt, and product-card links found.
Price cluesVisible price/payment hints before payment, with missing or conflicting payment metadata called out.
Missing proofUnsupported claims, stale metadata, broken discovery files, or unclear result expectations.
Route decisionProceed, fix first, ask for proof, or do not route, with a reason an agent can follow.
Receipt expectationSource URLs, timestamps, hashes, fields, or claim boundaries expected after payment.
How GateCheck works.
GateCheck should feel like a concrete next step, not a brochure. The public samples show the output today; the API is the runnable path.
1Paste a paid routeUse an x402 endpoint, MCP server, OpenAPI URL, marketplace page, or seller homepage as the target.
2Check public evidenceGateCheck inspects discovery files, OpenAPI/MCP metadata, visible pricing, launch copy, and unpaid 402 challenge behavior.
3Get a routeability decisionReturn
route_with_limits, ask_for_proof, fix_first, or do_not_route with the buyer-safe evidence behind it.Turn "can this charge me?" into a one-screen answer.
GateCheck makes the trust moment visible: the route, price clue, public 402 response, discovery files, missing proof, and recommended next action are packaged so a buyer can evaluate the paid path without reading protocol docs.
ROUTEWhat endpoint is live?Target URL, OpenAPI path, MCP endpoint, x402 manifest, and product card stay linked from the same report.
PRICEWhat could it cost?Quoted price fields, unpaid challenge metadata, launch copy, and visible pricing are checked for consistency.
DECISIONShould an agent proceed?Return
route_with_limits, ask_for_proof, or do_not_route with named blockers.RECEIPTWhat proof should come back?Expected source URLs, timestamps, hashes, receipt fields, or claim boundaries are listed before spend.
One pricing map, five buyer moments.
Use the smallest check that matches the decision in front of the buyer. Quick scans find obvious gaps, routeability reports make the paid path explainable, launch packs package the evidence, and receipts preserve what was observed.
Metadata scan$0.25Quick public manifest, OpenAPI, MCP, price, and discovery-file check.
Paid-path probe$0.50Unpaid 402 challenge and payment-metadata shape without signing or spending.
Routeability$1 / $5 / $10Quick, deep, and report-tier readiness decisions with buyer-safe claim boundaries.
Launch pack$9 / $29 / $49Listing copy, FAQ, checklist, approval packet, and distribution drafts.
Receipt$0.05Deterministic workflow receipt for observed evidence and returned artifacts.
Built for the places paid agents will look first.
GateCheck is not a marketplace, facilitator, wallet, or directory. It prepares the evidence those surfaces need: Bazaar and Agentic.Market metadata, xpay discovery files, MCP registry cards, OpenAPI schemas, visible price boundaries, unpaid 402 behavior, and buyer-safe non-claims.
DISCOVERYCan agents find it?Check
llms.txt, agents.txt, MCP metadata, OpenAPI, product cards, sitemaps, and answer-engine discovery JSON.PAYMENTCan the route prove what it charges?Inspect unpaid 402 challenge shape, price hints, resource names, payment headers, and claim boundaries without signing or spending.
TRUSTCan a buyer understand it?Return a readable routeability report with pass/fail evidence, what not to claim, and the next fix before launch.
Would this be catalog-ready?
GateCheck turns each distribution surface into an evidence checklist so sellers can fix the route before asking for marketplace, directory, or answer-engine attention.
CDP BazaarMetadata qualityDescription, input/output schema, resource URL, price clarity, and settled-route readiness without claiming Bazaar indexing.
Agentic.MarketBuyer previewHuman-readable listing copy, routeability card, examples, and claim boundaries before seller promotion.
xpayAgent files
llms.txt, agents.txt, product-card markdown, skill docs, and clean per-call pricing language.MCP directoriesServer cardMCP endpoint, tool list, auth/payment boundary, OpenAPI links, and namespace-safe metadata for crawlers.
Answer enginesCitable factsCanonical pages, JSON-LD, sitemap entries,
ai-discovery.json, and proof samples for ChatGPT, Grok, Gemini, Google, and Bing.Buyer agentSpend decisionPlain labels:
route_with_limits, ask_for_proof, fix_first, or do_not_route.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.
no keysno wallet accessno signingno spendpublic evidence
The wow: your agent does not have to guess.
Before a paid tool call, GateCheck shows what is live, what it may cost, what proof exists, when to stop, and what receipt should come back.
SEEWhat is actually liveExpose the manifest, OpenAPI, MCP card, public samples, and routeability card before asking for trust.
DECIDEWhether to buy, pause, or fixTurn scattered launch clues into a plain-language spend decision with named blockers.
PROVEWhat came backKeep every output tied to observed evidence, source links, timestamps, receipt fields, or claim boundaries.
routepriceevidencedecisionreceipt
Consumer-grade clarity for agent payments.
The buyer should not need to understand every protocol detail to feel in control. GateCheck turns the paid-agent moment into three plain questions with visible artifacts: can this route charge me, what evidence supports the purchase, and what receipt proves the result was delivered.
BeforeWill this charge me?Show the x402 route, quoted price, unpaid 402 challenge, and public product card before any buyer trusts the paid path.
DuringShould my agent continue?Return a plain-language decision: proceed, fix first, ask for proof, or stop when the evidence is not strong enough.
AfterWhat did I get?Point every completed action at a sample report, receipt field, source URL, timestamp, hash, or claim boundary that a person can inspect.
Live status, without fake traction claims.
These are operational crawlability signals only. They do not claim customer adoption, marketplace approval, ranking, revenue, or endorsement.
ROUTESProduction pages are liveGateCheck, Signal Desk, ResultRail, proof-stack, comparison, OpenAPI, and sitemap routes return public pages or machine-readable files.
CRAWLERSSearch and AI bots are allowedrobots.txt advertises sitemaps and allows OpenAI, Google/Gemini, Bing, Perplexity, Claude, and general crawlers.
AGENTSMachine cards are publishedOpenAPI, MCP directory metadata, agent cards, llms files, product cards, x402 manifests, and sample proof artifacts are linked.
Three proof products for the first paid-agent wave.
Agent commerce will not be won by raw payment buttons alone. Buyers need public evidence before spend, decision receipts before multi-tool chains, and source-attributed result packs after payment. LarryBuildsAI keeps each product scoped so agents, crawlers, and buyers can understand exactly what problem each one solves.
Signal Desk
Ask whether an agent should buy, skip, stop, or require proof before it chains search, enrichment, model, market, or onchain-data calls. Advisory only until a real policy gateway exists.
Open Signal DeskResultRail
Quote first, then buy one source-attributed public domain or URL result with timestamps, confidence, stop conditions, and receipt hashes.
Open ResultRailGateCheck gives buyers and sellers the evidence layer before spend.
GateCheck by LarryBuildsAI gives x402 and MCP sellers a clean pre-listing evidence packet and gives buyers a routeability card: what is live, what is missing, what the unpaid 402 proves, what buyers will see, and which claims are safe to make.
PRIMARY
GateCheck Routeability
Score an x402/API/MCP service, identify launch blockers, validate discovery surfaces, and produce a claim-bounded routeability handoff for review.
UPSELL
x402 Launch Pack Generator
Turn readiness evidence into marketplace-safe listing copy, buyer FAQ, checklist, distribution draft, and approval packet.
Pick the smallest proof step that matches the spend decision.
Start with a $1 quick readiness check when you need a fast public-surface pass. Use the $10 report when you need a routeability handoff artifact. Package the launch only after the evidence is clean enough to sell from.
1$1 quick readiness checkScan x402 manifest, OpenAPI, pricing metadata, llms.txt, agents.txt, MCP discovery, and optional marketplace URL for obvious launch blockers.
2$10 buyer-safe reportAdd a claim-bounded Markdown handoff with score breakdown, findings, fixes, and re-test guidance a seller can share before marketplace review.
3$49 premium launch packGenerate buyer-safe listing copy, FAQ, checklist, distribution draft, pricing guidance, approval notes, and claim boundaries without posting or spending.
What GateCheck is — and is not.
GateCheck is a buyer-readable routeability layer for paid x402 and MCP routes before a seller submits, promotes, or routes agents into a paid 402 flow. It is not a payment processor, wallet, security audit, or marketplace approval guarantee; it checks public launch evidence and produces a buyer-safe routeability report.
IT IS
Preflight evidence before spend
A quick way to find launch blockers and package bounded proof before a marketplace review, X launch, MCP directory submission, or paid agent routing.
IT IS NOT
No false trust claims
Not a marketplace endorsement, wallet or payment automation layer, security audit, escrow, guaranteed ranking signal, or deep benchmark lab.
1Not a marketplaceComplements Bazaar, Agentic.Market, x402scan, xpay, and MCP directories by checking seller evidence before distribution.
2Not a wallet or payment automation layerInspects unpaid challenge metadata and public docs without signing, spending, holding funds, or executing buyer purchases.
3Not a security auditKeeps claims bounded: observed public metadata and readiness evidence, not vulnerability certification or agent-spend safety guarantees. Not a deep benchmark lab for multi-turn task completion.
MCP and REST tools packaged for marketplace review.
Direct REST endpoints are x402-gated. The MCP endpoint exposes read-only and receipt tools prepared for xpay wrapping and agent-directory crawlers. Legacy names remain in machine-readable files only where existing receipts or marketplace slugs still need them.
Boundary Guard Check
$0.03
Create a deterministic, read-only pre-action receipt from request, policy, and optional result evidence. Use before an agent posts, spends, lists, or writes so the decision can be audited; no external action is executed.
x402 Resource Scan
$0.10
Read-only scan of a public API/provider URL for x402, OpenAPI, pricing, and agent-discovery metadata. Pass url, and optionally marketplace_url plus expected_resources, to get a readiness score, issues, and fixes; no private endpoints are called.
x402 Paid-Path Health Probe
$0.50
Probe a public x402 paid endpoint without signing or paying, then parse the HTTP 402 challenge. Pass target plus optional expected network/asset/price to verify payment metadata and receive a deterministic health receipt.
GateCheck Readiness
$1.00
GateCheck readiness: check whether an x402/agent-facing tool is ready for agent routing, marketplace listing, and paid-path monitoring, including public agent discovery surfaces (/llms.txt, /agents.txt, /.well-known/mcp.json, /mcp). Pass target plus optional tier, marketplace_url, expected_resources, and paid_path; deep/report tiers add unpaid 402 probing when paid_path is supplied. Tiers: quick $1, deep $5, report $10.
x402 Launch Pack Generator
$9.00
Generate marketplace-safe launch assets for an x402/MCP seller: listing copy, buyer FAQ, checklist, approval packet, and claim boundaries. Pass target plus optional product_name, audience, primary_use_case, marketplace_url, and paid_path; service/premium tiers include readiness evidence. Tiers: single $9, service $29, premium $49.
Generate Trust Receipt
$0.05
Generate a deterministic trust receipt from sanitized request/policy/result/payment summaries. Do not submit raw auth headers, cookies, API keys, private keys, payment signatures, payment response headers, customer prompts, customer documents, or payer-identifying evidence.
MCP endpoint: https://x402ready.vercel.app/gatecheck/mcp. Public docs are served from this deployment. Claim boundary: readiness reports and receipts prove what this service observed, received, hashed, and returned — not marketplace endorsement, settlement proof, security certification, or downstream real-world execution. Legacy note: Agent Tool Readiness Checker, x402 Resource Scanner, and Boundary Guard x402 are retained only for migration and receipt continuity.