PricePilot402 public market intelligence

Pay for PricePilot402 from AgentCore Bazaar

Configure AgentCore Gateway with Coinbase Bazaar MCP, then let an agent discover and call the PricePilot402 capped x402 benchmark route.

Updated 2026-07-04T06:02:03.709Z Canonical /public/use/pay-with-agentcore-bazaar Structured JSON-LD plus paid API metadata

x402 API benchmark for pricing, buying, and listing decisions

AgentCore Gateway + Bazaar is a payment-capable path for the recommended first PricePilot402 call: GET /v1/market/hot-categories?intent=market_research.

What this page shows

This page shows the exact route, max payment cap, unpaid 402 challenge request, paid retry placeholder, and what counts as real M1A demand.

What the paid API adds

The paid $0.02 response ranks active x402 categories by visible activity, density, confidence, and suggested follow-up benchmark inputs.

Who should use it

Use this when you already have an x402-capable agent, MCP gateway, SDK client, or x402 explorer wallet.

Example use cases

Move from seeing a 402 challenge to making a deliberate paid retry with a capped buyer wallet or agent payment client.

Why the data is useful

The route is useful because it gives a small first paid call before a buyer commits to deeper category or endpoint benchmarks.

What the buyer gets after payment

After payment, the buyer gets structured JSON with hot categories, confidence, decision notes, and recommended follow-up route inputs.

Clear next action

Use AgentCore Gateway + Bazaar to request the 402 challenge, approve at most 0.05 USDC, then retry the same route with the x402 payment proof.

Recommended first paid call

GET /v1/market/hot-categories?intent=market_research is the recommended first call because it costs $0.02 and answers which x402 categories are worth deeper benchmarking.

Client path
AgentCore Gateway + Bazaar

agentcore add gateway-target

Route
GET /v1/market/hot-categories

recommended first call

Price
$0.0200

fixed x402 payment

Max payment cap
$0.05

keep buyer approval tight

AgentCore Gateway + Bazaar setup

Add the Coinbase Bazaar MCP server as an AgentCore Gateway target, then ask the agent to search for PricePilot402 and cap the payment at 0.05 USDC.

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

agentcore deploy

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.

GET /v1/market/hot-categories

Default intent
market_research

Which x402 category or endpoint is worth watching?

{
  "sample_only": true,
  "not_live_paid_result": true,
  "route": "GET /v1/market/hot-categories",
  "intent": "market_research",
  "decision": "watch_category",
  "recommended_action": "watch_for_more_snapshots",
  "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 unpaid probe

Run this first to get HTTP 402 and the authoritative PAYMENT-REQUIRED header. This does not count as paid demand.

curl -i "https://pricepilot402.pricepilot402-arya.workers.dev/v1/market/hot-categories?intent=market_research&limit=10&buyer_source=agentcore_bazaar&pp_ref=dist_view_540b462a-3c4e-4e6b-8b0f-c373619c6801"

Exact paid retry placeholder

Only retry after your buyer client creates a valid x402 proof. Keep maxPayment at 0.05 or lower.

curl -i "https://pricepilot402.pricepilot402-arya.workers.dev/v1/market/hot-categories?intent=market_research&limit=10&buyer_source=agentcore_bazaar&pp_ref=dist_view_540b462a-3c4e-4e6b-8b0f-c373619c6801" \
  -H "PAYMENT-SIGNATURE: <x402 payment proof>"

Client request shape

{
  "url": "https://pricepilot402.pricepilot402-arya.workers.dev/v1/market/hot-categories?intent=market_research&buyer_source=agentcore_bazaar",
  "method": "GET",
  "maxPayment": "0.05",
  "expectedPriceUsd": "0.02",
  "network": "eip155:8453",
  "asset": "Base USDC",
  "buyer_source": "agentcore_bazaar"
}

Paid response preview

The public page does not expose paid-only values. After payment, the response unlocks fields an agent can use directly.

{
  "sample_only": true,
  "not_live_paid_result": true,
  "unlocked_fields": [
    "decision",
    "operational_decision",
    "supporting_evidence",
    "alternatives",
    "alternative_summary",
    "price_percentile",
    "payer_density",
    "call_density",
    "visible_gmv_estimate",
    "confidence_explanation",
    "opportunity_flags",
    "suggested_test_price_band",
    "source_trail",
    "decision_notes"
  ],
  "sample": {
    "route": "GET /v1/market/hot-categories",
    "decision": "sample: worth_testing / avoid_for_now / better_alternative_available / needs_more_history",
    "supporting_evidence": "sample: price_position, payer_signal, call_signal, gmv_signal, source_freshness, history_depth",
    "alternatives": "sample: only present when a same-category active endpoint has lower/equal price and stronger payer/call/GMV signal",
    "alternative_summary": "sample: No materially stronger active comparable endpoint was found in current public observations.",
    "price_percentile": "sample: p35 within comparable x402 data APIs",
    "payer_density": "sample: above category median visible payer density",
    "visible_gmv_estimate": "sample: low/mid/high range, not a live paid result",
    "confidence_explanation": "sample: derived from public observations and source trail confidence",
    "opportunity_flags": [
      "sample_underpriced_candidate",
      "sample_verify_activity_before_listing"
    ],
    "suggested_test_price_band": "sample: $0.015-$0.030 for a controlled test",
    "source_trail": [
      "sample: public marketplace/source URL and observation timestamp"
    ],
    "decision_notes": "sample: compare price against payer density and visible GMV before buying, listing, or repricing"
  }
}

What counts as M1A

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.