PricePilot402 public market intelligence

PricePilot402 x402 Compatibility

Compatibility notes for calling PricePilot402 provisional x402 routes with Base mainnet USDC, x402 v2 exact payments, OpenAPI, and public metadata.

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

x402 API benchmark for pricing, buying, and listing decisions

Use this page when checking whether a buyer client or agent can request a PricePilot402 x402 challenge and retry with a compatible payment proof.

What this page shows

This public compatibility page shows the Base mainnet network, USDC asset, x402 v2 exact payment scheme, required headers, OpenAPI, x402 metadata, and the four live capped provisional routes.

What the paid API adds

The public page shows how to test compatibility without paying. The paid API returns structured benchmark JSON after a valid x402 payment proof is supplied.

Who should use it

Agents, developers, marketplace crawlers, x402 clients, and buyer-wallet integrations should use it before attempting a paid benchmark call.

Example use cases

Verify header handling, inspect PAYMENT-REQUIRED metadata, prepare a paid retry, and confirm which PricePilot402 routes are live under provisional caps.

Why the data is useful

The data is useful because it removes ambiguity about network, asset, scheme, headers, metadata URLs, and live route availability.

What the buyer gets after payment

After payment, the buyer gets route-specific JSON benchmark output. Compatibility testing only requests a 402 challenge and does not count as paid demand.

Clear next action

Start by requesting a 402 challenge without payment, then use an x402-compatible Base USDC client to retry the same route with a payment proof.

Network
Base mainnet

eip155:8453

Asset
USDC

0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913

x402 version
x402 v2

standards-compatible payment challenge

Scheme
exact payment scheme

fixed amount per route

Required x402 headers

Unpaid requests return PAYMENT-REQUIRED. Paid retries should send PAYMENT-SIGNATURE or X-PAYMENT. Successful paid responses return PAYMENT-RESPONSE.

Browser clients can read the x402 headers because responses expose PAYMENT-REQUIRED and PAYMENT-RESPONSE through CORS.

Test without paying

You can test client compatibility by requesting a 402 challenge without a payment header. That challenge is API intent telemetry, not paid demand, not revenue, and not M1A evidence.

For POST routes, send the example JSON body exactly. For GET routes, use the query parameters shown in the route-specific block.

Discovery resources

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.