PricePilot402 public market intelligence

Use x402 Category Benchmarks

Buyer example for category-level x402 benchmark calls across MCP tools, data APIs, and Base USDC paid API categories.

Latest generation timestamp: 2026-07-03T12:01:54.720Z

x402 API benchmark for pricing, buying, and listing decisions

The paid category benchmark compares all tracked endpoints in this category and returns price percentiles, payer density, GMV range, seller concentration, and decision notes.

What this page shows

This public buyer example shows the route, method, price, Base USDC network, example input, unpaid 402 probe, and placeholder paid retry.

What the paid API adds

The public page shows how to call the route. The paid API returns structured benchmark JSON after a valid x402 payment proof is supplied.

Who should use it

Agents, scripts, buyers, and builders should use this page when wiring a concrete x402 benchmark call.

Example use cases

Request a 402 challenge, test x402 client handling, prepare a paid retry, and connect the result to pricing or market-selection workflows.

Why the data is useful

The data is useful because it shows the exact route an agent can call and the market fields the paid response is designed to return.

What the buyer gets after payment

After payment, the buyer gets JSON benchmark output for the selected route, including comparable market context, confidence, and source trail where supported.

Clear next action

Agents can request the 402 challenge, pay with Base USDC, then retry the same route to receive JSON benchmark output.

Route
POST /v1/benchmark/category

route-specific buyer example

Price
$0.0200

fixed x402 payment

Network
eip155:8453

Base mainnet

Asset
0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913

Base USDC

Expected 402 challenge behavior

Payment is required for a 200 response. Without a valid x402 payment response, this route returns a 402 challenge with payment requirements.

The paid retry should target the same route and satisfy the challenge using an x402-compatible buyer wallet or client.

curl example

First request the challenge, then retry after your buyer client creates the x402 payment proof.

curl -i "https://pricepilot402.pricepilot402-arya.workers.dev/v1/benchmark/category?pp_ref=dist_view_67b78407-7b74-426f-a5fa-fab25f6a8577" \
  -H "content-type: application/json" \
  --data '{"category":"web-search","network":"eip155:8453"}'
curl -i "https://pricepilot402.pricepilot402-arya.workers.dev/v1/benchmark/category?pp_ref=dist_view_67b78407-7b74-426f-a5fa-fab25f6a8577" \
  -H "content-type: application/json" \
  -H "PAYMENT-SIGNATURE: <x402 payment proof>" \
  --data '{"category":"web-search","network":"eip155:8453"}'

JavaScript fetch example

const response = await fetch("https://pricepilot402.pricepilot402-arya.workers.dev/v1/benchmark/category?pp_ref=dist_view_67b78407-7b74-426f-a5fa-fab25f6a8577", {
  "method": "POST",
  "headers": {
    "content-type": "application/json"
  },
  "body": JSON.stringify({
  "category": "web-search",
  "network": "eip155:8453"
})
});
console.log(response.status);
if (response.status === 402) {
  console.log(response.headers.get("PAYMENT-REQUIRED"));
}

const response = await fetch("https://pricepilot402.pricepilot402-arya.workers.dev/v1/benchmark/category?pp_ref=dist_view_67b78407-7b74-426f-a5fa-fab25f6a8577", {
  "method": "POST",
  "headers": {
    "content-type": "application/json",
    "PAYMENT-SIGNATURE": "<x402 payment proof>"
  },
  "body": JSON.stringify({
  "category": "web-search",
  "network": "eip155:8453"
})
});
console.log(response.status);
if (response.status === 402) {
  console.log(response.headers.get("PAYMENT-REQUIRED"));
}

Discovery links

x402 API benchmark FAQ

What is an x402 API benchmark?

An x402 API benchmark compares paid API endpoints that use HTTP 402 payment flows, including observed price, activity, visible GMV, confidence, and comparable market context.

What does the paid API return?

The paid API returns structured JSON for agents and scripts, including comparable endpoint clusters, price dispersion, payer density, visible GMV estimates, opportunity flags, confidence, and source trail where supported.

How is this different from public marketplace listings?

Public marketplace listings usually show one seller or endpoint at a time. PricePilot402 connects listings into category, endpoint, and market benchmarks so buyers can compare price and activity across similar x402 APIs.

Can agents call this API?

Yes. Agents can read the public pages, inspect OpenAPI and x402 metadata, request a 402 challenge, pay with an x402-compatible Base USDC flow, and retry the same route for JSON benchmark output.

What payment network does it use?

The provisional live routes use Base mainnet USDC through x402 metadata. Full Phase 1 remains locked while capped provisional routes stay under the configured price and usage limits.