x402-protocol-integration

Category-first view of the x402swag.com storefront: apparel, drinkware, stickers, crew-necks, and v-necks, each with its items and price ranges, plus the store's real purchase flow (free browse/checkout, dynamic x402/card settlement, or the store's $0.05 one-call shortcut). Optional category filter.

A directory built for agents choosing which paid tool to call next: 11 ForgeMesh x402 services with category, endpoint counts, and price ranges, refreshed from each service's live API discovery output. Optional category filter narrows results. Returns the product id needed to fetch full call shapes from fleet-product-detail.

The exact call spec for one x402 service in the ForgeMesh fleet: routes, methods, prices, JSON input schemas, and worked examples, pulled from that service's own live API discovery surface. Pass `product` (id or name from fleet-products). Built for agents integrating a new paid tool without trial-and-error against its API.

Machine-readable endpoint shapes for one ForgeMesh x402 product — every route's input schema and a worked example response, plus price per call. Use fleet-products first to find the product id, then pass it here (`product`) for the full integration reference. Unknown ids return the valid list instead of a bare error.

ForgeMesh merch catalog sourced live from x402swag.com: apparel, drinkware, and stickers with price ranges per item, plus exactly how the purchase flow works (free browse, free cart, dynamic-price settlement via x402 or card). Optional category filter narrows to one product line.

Full endpoint sheet for one ForgeMesh x402 product: every route, HTTP method, price, description, input schema, and (where available) a worked response example — everything needed to call it correctly on the first try. Required `product` matches an id or name from fleet-products (case-insensitive); an unknown value returns the valid id list.

Returns the complete set of call shapes (routes, methods, input schemas, worked examples, prices) for a named ForgeMesh x402 service, so an agent can construct a correct request without probing the live API first. Required `product` — an id or name from fleet-products; unmatched values list the valid options.

Paid, machine-readable registry of ForgeMesh's production x402 agent services: what each one is, its category, route count, and USD price range. Spans 11 services across onchain intel, voice, travel, econ intel, commerce, infra, and this Utility Grid itself. Optional category filter. Call fleet-product-detail next for full endpoint schemas and worked examples of any listed service.

What's for sale at x402swag.com and how an agent actually buys it: categories, items with price ranges, and a how_to_buy breakdown covering free browsing, cart/checkout, dynamic per-order x402/card settlement, and the store's paid one-call catalog shortcut. Optional category filter.

Overview of every product in the ForgeMesh x402 fleet — id, name, hosting domain, category, how many paid routes it exposes, and its price range — generated from each service's own live discovery surface, not third-party scraping. Optional category filter. See fleet-product-detail for the routes, schemas, and examples behind any product.

Live catalog of every x402 agent service in the ForgeMesh fleet: name, category, live route count, and price range per service, sourced from each service's own public API discovery surface. Filter by category (onchain-intel, voice, travel, econ-intel, commerce, infra, media, utility-grid). Pair with fleet-product-detail for exact routes, input schemas, and worked call examples.

Unauthenticated GET to resourceUrl; checks HTTP 402, accepts[], price sanity. Query: url (required). e.g. GET /v1/x402/probe?url=https://...

The funnel logic behind ForgeMesh's x402 pricing and discovery design, as 10 structured tenets: why discovery stays free, why the 402 challenge itself is a probe, why failed upstreams never charge, and why prices ladder from taste-test to premium. Written for agents and builders evaluating or designing paid API funnels.

10 structured tenets explaining how ForgeMesh designs x402 services for agent discovery: rich free llms.txt/openapi surfaces, the 402 challenge as a free probe, paying for aggregation not secrets, upstream rug-pull tiering, and price laddering. Each tenet has an id, a one-line statement, and a detail paragraph.

Web search: ranked results (title + url) for a query. ?q=x402+agent+payments&limit=8

x402 seller attribution intelligence: reported calls versus catalog-attributed on-chain USDC flow, payer-address concentration and forensic signals. Attribution is not protocol or fraud proof.

Deep view: top 100 x402 services tagged 'derivatives': ranked by 30-day unique paying wallets, with calls, price, network and calls-per-payer for each. 49 providers and 135 paying wallets measured in this tag.

Use when an agent needs an x402 market report. Returns market report: top 40 categories by paying wallets (providers, calls, payers, median price) and top 25 services by 30-day calls

Deep view: top 100 x402 services tagged 'verdict': ranked by 30-day unique paying wallets, with calls, price, network and calls-per-payer for each. 10 providers and 2536 paying wallets measured in this tag.

XMPP-CLIENT service discovery (_xmpp-client._tcp.<domain>): SRV records with priority, weight, port and target host, from Cloudflare DoH. Tells a client where the domain's xmpp-client service lives without guessing hosts. $0.01 per lookup.

X-PUPPET service discovery (_x-puppet._tcp.<domain>): SRV records with priority, weight, port and target host, from Cloudflare DoH. Tells a client where the domain's x-puppet service lives without guessing hosts. $0.01 per lookup.

XMPP-SERVER service discovery (_xmpp-server._tcp.<domain>): SRV records with priority, weight, port and target host, from Cloudflare DoH. Tells a client where the domain's xmpp-server service lives without guessing hosts. $0.01 per lookup.

How do I fix my broken x402 endpoint? Diagnoses it, then returns per problem the concrete change as code for your stack (Express, Next.js, Hono or raw HTTP), filled in with your own payTo, amount, network and route.

The fix for your x402 endpoint: diagnoses it, then returns per problem the concrete change as code for your stack (Express, Next.js, Hono or raw HTTP), filled in with your own payTo, amount, network and route.