gpt55-x402-gateway

x402 Checkout Source Quality

This is a seller-side diagnostic for the uncomfortable middle of an x402 funnel: lots of HTTP 402 quotes, little or no settlement.

It does not ask “is x402 broken?” first. It asks a narrower question: which sources created the quotes, and did any likely buyer ever send an X-PAYMENT header?

When To Use It

• Your /v1/paid/... route gets many quotes but few settles.
• Your top user agents include health checks, indexers, probes, or internal scripts.
• You need to decide whether to fix checkout copy, improve the paid result, or find better buyer traffic.

Copy-Paste Check

git clone https://github.com/go165/gpt55-x402-gateway.git
cd gpt55-x402-gateway
npm install
PRODUCT=walletSigningSafety ACCESS_LOG=logs/access.jsonl node examples/checkout-source-quality/checkout-source-quality.mjs

Supported products: walletSigningSafety, mcpIntegrationKit, sellerMiniCheck, growthPlan, sellerIntel, and translate.

What The Output Means

• potentialBuyerQuotes: quote traffic not classified as monitor, crawler, or internal.
• monitorOrInternalQuotes: quote traffic likely from uptime checks, indexers, probes, bots, crawlers, or internal IPs.
• paymentHeaders: requests that actually included a payment header.
• topSources: the IP and user-agent groups that explain the quote volume.
• nextAction: the shortest operational recommendation for that source mix.

Why It Matters

If the top source is a monitor, adding another paid endpoint will not fix revenue. If the top source is a potential buyer with zero payment headers, the better move is usually a shorter buyer-owned payment route, clearer payTo/network/amount handoff, or a first-payment client link.

This script is read-only. It never signs, pays, submits directory entries, or touches a wallet.

This site is open source. Improve this page.