PricePilot402 public market intelligence

Check My x402 Endpoint Price

Paste your x402 endpoint and compare its price and visible activity against similar tracked x402 routes before listing, repricing, or buying.

Updated 2026-07-04T06:02:03.709Z Canonical /public/use/check-my-x402-endpoint-price Structured JSON-LD plus paid API metadata

x402 API benchmark for pricing, buying, and listing decisions

POST /v1/benchmark/endpoint?intent=seller&buyer_source=seller_operator is the primary M1A activation route for x402 sellers who need a pricing/activity benchmark for their own endpoint.

What this page shows

This page shows a local-only endpoint input, exact unpaid 402 probe, paid retry placeholder, payment-capable client prompts, OpenAPI link, x402 metadata link, and what does or does not count as M1A.

What the paid API adds

The paid endpoint benchmark compares one endpoint against similar active x402 routes and returns price position, payer density, visible GMV estimate, underpriced/overpriced score, suggested test price band, opportunity flags, confidence, and source trail.

Who should use it

x402 sellers, MCP tool owners, API builders, and pricing operators should use this when deciding whether to list, price, reprice, or benchmark an x402 endpoint.

Example use cases

Check if your endpoint is priced too low or too high, compare activity against similar routes, decide whether to adjust a listing, and test if a buyer client can complete the x402 payment retry.

Why the data is useful

Payment only happens when the buyer has an immediate job and a payment-capable client. A seller asking 'is my endpoint priced right?' has a clearer job than a generic market scan.

What the buyer gets after payment

After payment, the buyer gets structured JSON with comparable endpoint clusters, price percentile, payer/call density, visible GMV estimate, pricing score, suggested test price band, decision notes, and source trail where supported.

Clear next action

Paste an endpoint locally, dry-run the 402 challenge, then retry only from a real x402-capable buyer client with a deliberate Base USDC payment proof.

Endpoint price check

Paste your x402 endpoint and see whether the price/activity looks weak, fair, underpriced, or overpriced against similar routes.

I built a paid x402 benchmark API. If you run an x402 endpoint, this checks whether your price/activity looks right.

This input is local-only. Typing here does not submit or store the endpoint. PricePilot402 only receives the endpoint if you intentionally call the paid API route.

Hero route
POST /v1/benchmark/endpoint

intent=seller, buyer_source=seller_operator

Price
$0.0500

fixed Base USDC x402 payment

Max payment cap
$0.05

keep buyer approval tight

Primary buyer
x402 seller/operator

pricing problem first

Local-only example builder

Generated request body:

{
  "endpoint_url": "https://seller.example.com/x402-route",
  "category_hint": "data",
  "intent": "seller"
}

Generated unpaid 402 probe:

curl -i -X POST "https://pricepilot402.pricepilot402-arya.workers.dev/v1/benchmark/endpoint?intent=seller&buyer_source=seller_operator" \
  -H "content-type: application/json" \
  --data '{"endpoint_url":"https://seller.example.com/x402-route","category_hint":"data","intent":"seller"}'

Decision Preview

Decision Preview

Example only - not a live paid result. Paid responses start with a recommendation, not just metrics. If data is thin, the response says so; alternatives are only shown when a stronger comparable endpoint exists; historical/source freshness is included when enough observations exist.

POST /v1/benchmark/endpoint

Default intent
seller

What should I price or list my endpoint at?

{
  "sample_only": true,
  "not_live_paid_result": true,
  "route": "POST /v1/benchmark/endpoint",
  "intent": "seller",
  "decision": "list_near_category_median",
  "recommended_action": "test_p25_p50_p75_price_band",
  "plain_english": "Example only. The paid response makes a route-specific recommendation using comparable endpoints, price position, payer/call signal, visible GMV, source freshness, and history depth.",
  "confidence": "sample",
  "alternative_summary": "Example only: alternatives are only returned when a materially stronger same-category endpoint exists.",
  "supporting_evidence": {
    "price_position": "sample_only",
    "payer_signal": "sample_only",
    "call_signal": "sample_only",
    "gmv_signal": "sample_only",
    "source_freshness": "sample_only",
    "history_depth": "sample_only",
    "source_confidence": "sample_only",
    "observation_count": "sample_only",
    "observed_days": "sample_only",
    "endpoint_seen_in_latest_snapshot": "sample_only"
  }
}

Exact route to call

POST /v1/benchmark/endpoint?intent=seller&buyer_source=seller_operator

{
  "endpoint_url": "https://seller.example.com/x402-route",
  "category_hint": "data",
  "intent": "seller"
}

Unpaid 402 probe

Run this first. It should return HTTP 402, PAYMENT-REQUIRED, and a probe_id. This is API intent, not demand.

curl -i -X POST "https://pricepilot402.pricepilot402-arya.workers.dev/v1/benchmark/endpoint?intent=seller&buyer_source=seller_operator" \
  -H "content-type: application/json" \
  --data '{"endpoint_url":"https://seller.example.com/x402-route","category_hint":"data","intent":"seller"}'

Paid retry placeholder

Only run this after a real buyer client parses PAYMENT-REQUIRED, signs locally, and deliberately approves the payment. Do not paste private keys or raw proofs into chat.

curl -i -X POST "https://pricepilot402.pricepilot402-arya.workers.dev/v1/benchmark/endpoint?intent=seller&buyer_source=seller_operator&probe_id=<probe_id_from_402>" \
  -H "content-type: application/json" \
  -H "PAYMENT-SIGNATURE: <x402 payment proof>" \
  --data '{"endpoint_url":"https://seller.example.com/x402-route","category_hint":"data","intent":"seller"}'

Base MCP prompt

Call this x402 endpoint with maxPayment 0.05 USDC:
https://pricepilot402.pricepilot402-arya.workers.dev/v1/benchmark/endpoint?intent=seller&buyer_source=seller_operator

Use initiate_x402_request with method="POST" and this JSON body:
{
  "endpoint_url": "https://seller.example.com/x402-route",
  "category_hint": "data",
  "intent": "seller"
}

After I approve the Base Account payment link, use complete_x402_request with the returned requestId.

Coinbase Bazaar MCP prompt

Use Coinbase Bazaar MCP search_resources for "PricePilot402 endpoint price benchmark".
If the PricePilot402 endpoint benchmark tool is found, call proxy_tool_call for:
POST /v1/benchmark/endpoint?intent=seller&buyer_source=seller_operator

Use this body:
{
  "endpoint_url": "https://seller.example.com/x402-route",
  "category_hint": "data",
  "intent": "seller"
}

Set max payment to 0.05 USDC.

AgentCore Bazaar prompt

agentcore add gateway-target \
  --name CoinbaseBazaar \
  --type mcp-server \
  --endpoint https://api.cdp.coinbase.com/platform/v2/x402/discovery/mcp \
  --gateway MyGateway

Then ask the agent to search for PricePilot402 and call:
POST /v1/benchmark/endpoint?intent=seller&buyer_source=seller_operator

Use maxPayment 0.05 USDC and the endpoint JSON body from this page.

@x402/fetch path

Use @x402/fetch or examples/x402-buyer-cli with a funded Base USDC buyer wallet.
Dry-run the 402 challenge first.
Only pass --pay when the seller/operator deliberately approves the real payment.

What counts as M1A

Pivot if this still stays at zero

If 10 real x402-capable builder/seller attempts still produce zero paid retries, pivot to an x402 route readiness and pricing audit.

The pivot offer is: lint my x402 route, metadata, Bazaar readiness, payment headers, price, and discoverability.

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.