QU
API · x402

Settlement-verified demand for x402 endpoints: for each indexed seller we read USDC Tra…

Settlement-verified demand for x402 endpoints: for each indexed seller we read USDC Transfer logs on Base over 24h and count only transfers matching a price that address actually lists, giving real paid-call counts, DISTINCT PAYER counts and USD/day per selle…

by Quietforge Docs API · verified provider · updated 2026-10-14

30d calls—
30d payers—
MethodHTTP
Outputjson

What it does

Settlement-verified demand for x402 endpoints: for each indexed seller we read USDC Transfer logs on Base over 24h and count only transfers matching a price that address actually lists, giving real paid-call counts, DISTINCT PAYER counts and USD/day per seller. Payer counts include sampler wallets that pay many sellers once: read them as an upper bound on customers. Includes each seller's on-chain-payments to reported-calls ratio.

Tags: x402 · demand · onchain · due-diligence · agents

Call contract

Method
HTTP
Input
HTTP request
Output
json
No input exampleProvider did not publish one in Bazaar metadata.
No output exampleProvider did not publish one in Bazaar metadata.

Use with an agent

  1. Discover. Agents find this listing with GET https://bazaar.saylorinnovations.com/discovery/search?query=…, the MCP tool search_resources, or /discovery/resources.
  2. Inspect. Fetch /resources/59921.json for the price and payment options.
  3. Pay. Call GET https://qf-api.quietforge-studio.workers.dev/v1/x402/demand. The provider answers 402 with its payment requirements. An x402 client signs one of the options below and retries with PAYMENT-SIGNATURE.
  4. Execute. The provider returns 200 with the data. Agent Bazaar is not in the request path and never sees your payment.

For humans

You don't need an account or an API key; you need a wallet holding a small amount of USDC on Base, and an x402-capable client (see the examples below). Call the endpoint unpaid first to see exactly what it asks for.

Pricing & payment

Price
$0.02 / request
Protocol
x402 v2
Auth
No account or API key. Pay per request.
Networks
Base

x402 payment requirements

SchemeNetworkAssetAmountPay toTimeout
exactBase
eip155:8453
USDC$0.020x3F5115236f25618c16021E983acaAF2CAaa1A35e300s
accepts[] (raw JSON)
[
  {
    "scheme": "exact",
    "network": "eip155:8453",
    "payTo": "0x3F5115236f25618c16021E983acaAF2CAaa1A35e",
    "asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
    "amount": "20000",
    "amountUsd": 0.02,
    "maxTimeoutSeconds": 300
  }
]

Examples

curl
curl "https://qf-api.quietforge-studio.workers.dev/v1/x402/demand"
# -> 402 Payment Required, accepts[] lists how to pay
# retry with a PAYMENT-SIGNATURE (or PAYMENT header) once paid
JavaScript
const res = await fetch("https://qf-api.quietforge-studio.workers.dev/v1/x402/demand");
if (res.status === 402) {
  const { accepts } = await res.json();
  // pay one of accepts[] via an x402 client, then retry with the payment header
}
Python
import httpx
res = httpx.get("https://qf-api.quietforge-studio.workers.dev/v1/x402/demand")
if res.status_code == 402:
    accepts = res.json()["accepts"]
    # pay one of accepts[] via an x402 client, then retry with the payment header

Details

Provider
Quietforge Docs API
Endpoint
https://qf-api.quietforge-studio.workers.dev/v1/x402/demand
Machine-readable
/resources/59921.json