the machine commerce network — HTTP 402, put to work

Every 402 is a buyer you couldn't see.

Autonomous agents probe your x402 API, hit 402 Payment Required, and leave. Install one middleware. Monetize unused 402 responses with recommendations, discovery, and machine commerce analytics.

$npm install @forgemeshlabs/x402-ads 140 lines, zero dependencies, fail-open. Read exactly what it sends.
GET /api/forecast → your x402 server live from this network
HTTP/1.1 402 Payment Required { "error": "payment_required", "challenge": { "accepts": [ … ] }, // untouched "recommendations": { "items": [ ] } ↑ injected by @forgemeshlabs/x402-ads — these items are live network inventory }

live network

402 responses observed
agent-class requests
recommendations served
services reporting
x402 services indexed

how it works

Three protocol moments, one middleware.

402

An agent probes and bounces

A client hits your paid endpoint, gets 402, and walks. Alone, you can count these. You can't tell a buyer from an uptime monitor.

recommendations[]

The 402 body gets useful

The middleware injects typed recommendations — sponsored placements and similar services from an 800+ service registry. The payment challenge is never modified.

report

The pool interprets your traffic

Probe metadata joins the network, pre-classified — monitor, indexer, or agent. You get the funnel: who probed, what they wanted, why they didn't pay.

the boundary

We measure machine commerce, not API content.

We never see what your customers asked or what your API returned — only that a client hit an endpoint, got a 402, and whether it later paid. The complete list, same as in the terms:

sentnever sent
request path — /api/forecastrequest bodies
method + status coderesponse bodies — your API's actual data
user-agent stringpayment headers, signatures, wallets
client IP → salted one-way hashraw IP addresses
your serviceId + category labelsAPI keys, cookies, end-user data

The middleware is 140 lines with zero dependencies. Don't take our word for the table — read the source on npm; that's the point.

the co-op deal

Your traffic, your terms.

Joining is automatic: POST /v1/publishers/register costs one $0.10 x402 payment, the paying wallet becomes your identity, and your key is returned instantly. No emails. No forms. No manual handling.

Your own analytics are free

The full intent report for any service you contribute events to costs you nothing, ever. Your publisher key is the receipt.

Aggregates only

Network products are category-level aggregates. Your publisher-identifiable raw events are never sold or transferred to anyone.

Opt out any time

Run inject-only with reportEvents: false, report-only with injectRecommendations: false, or uninstall. Raw event deletion within 30 days on request.

for agents & builders

Buy the demand signal itself.

Aggregate intent analytics, paid per call in USDC on Base mainnet over the x402 protocol. No account, no API key — your wallet is the login.

GET /api/network/statsnetwork totals + traffic classification$0.005
GET /api/intent/trendstop endpoints & categories agents want$0.01
GET /api/intent/demanddemand depth for one category$0.02
GET /api/intent/reportwhy-agents-didn't-buy funnel for a service$0.05
GET /api/intent/report + x-publisher-keythe same report, on your own servicefree

Machine-readable docs at /llms.txt and /openapi.json.