The cash register
for AI agents.
An autonomous agent asks for premium data, gets an HTTP 402 price quote, pays in USDC on Base over x402, and is served signed, provenance-stamped data, no signup, no human, no API key. Dynamic Feed is the merchant charging for its own service; the x402 facilitator verifies and settles on-chain. We never custody, hold, or route funds.
Three ways to pay-per-call.
Every endpoint returns the x402 bazaar discovery extension on its 402 response, so facilitators auto-catalog it and shopping agents find it with no registration. Prices below are read live from the running rail.
Bulk batch
Up to 100 signed tool calls in a single request. The high-throughput lane for an agent pulling many datapoints at once.
Any single tool
One signed call to any of the 90 live tools, weather, CVEs, sanctions, space, hazards, finance, shipping and more. Every datapoint carries its source, licence and timestamp.
Signed time-machine
Replay any tool's value at a past instant, verbatim and Ed25519-signed, for agent backtesting and "what did we know when we decided" audit trails. (Identity-bearing tools excluded, zero PII.)
See the cash register ring live.
Two live calls against the running production rail. Fetch the menu reads the machine-readable price list. Get a 402 quote sends a real request without payment and shows the exact HTTP 402 an agent receives, the price, the recipient wallet, and the bazaar discovery block. Nothing here moves money; the 402 is just the quote.
🛎️ Live from dynamicfeed.ai
Both buttons hit the real endpoints in your browser. The 402 response is the agent-facing price quote, read it, and you've seen exactly what a paying agent sees.
Machine-readable: /v1/pro/catalog · status /v1/pro/diag · the agent bootstrap /v1/onboard.
Four steps, zero humans.
- Discover. The agent finds the endpoint + price via the x402
bazaar, the/v1/pro/catalogmenu, the A2A AgentCard, or simply by calling and reading the 402. - Quote. It sends the real request with no payment. Dynamic Feed replies
402 Payment Requiredwith the amount, the asset (USDConbase), and the recipient address. - Pay. Its x402 client signs a payment and retries the same request with an
X-PAYMENTheader. A facilitator verifies and settles it on-chain, Dynamic Feed only reads the yes/no. - Get served. On success the data is returned, with the on-chain settlement proof in the
X-PAYMENT-RESPONSEheader. The whole loop runs machine-to-machine.
# any x402-aware HTTP client handles the 402 -> pay -> retry loop for you
pip install x402
from x402.clients import x402_requests # your wallet signs; the facilitator settles
http = x402_requests(account=my_base_wallet)
r = http.post("https://dynamicfeed.ai/v1/pro/asof",
json={"tool": "current_weather", "t": "2026-06-10T14:30:00Z"})
print(r.json()) # signed, verifiable as-of replay
print(r.headers["X-PAYMENT-RESPONSE"]) # your on-chain settlement proofNo wallet yet? Any x402 client works. The quickest for an LLM agent is Coinbase's Agentic Wallet, npx @coinbase/payments-mcp plugs straight into Claude, Codex or Gemini and pays x402 endpoints like these. Fund it with a little USDC on Base and point it at any /v1/pro URL. A complete runnable Python example is in the repo at examples/paying-agent.
The boundary, on purpose.
Dynamic Feed is the merchant, it charges for its own data service, exactly like any API selling access. The x402 facilitator verifies the payment and settles it on the Base chain; Dynamic Feed only reads the settlement result. It holds no balance, runs no wallet for anyone else, takes no custody, and offers no refunds ledger, there is no money path through Dynamic Feed to capture. That is deliberate: it keeps the rail simple, keeps us out of money-transmission territory, and keeps the witness/notary side of the product neutral. The price stays at the floor while we watch real agent traffic; honest signal first, optimisation later.