Back to Browse
Demand Radar
x402
Demand Radar is a paid API for AI agents from scanpay-edge.alextaghiashvili.workers.dev, paid per call via x402, $0.005/call, status unknown (last checked 2026-11-02).
Aggregates anonymized demand telemetry from x402 API traffic logs to reveal which endpoints are being called, challenged, and paid for, guiding build/buy decisions.
Price / call$0.005
Success—
StatusUnknown
How this service works
Pay-per-call x402 APIs for AI agents: OpenAI-compatible LLM chat, perp funding and arbitrage spreads, crypto prices, gas, FX, Solana SPL mint audit, token price by contract, x402 delivery-receipt verification, web search, clean page extraction, batch tools and deterministic code-security scanning. USDC on Base or Solana, no signup, no API key, from $0.0001 a call.
Output
Returns a JSON object with total HTTP 402 challenge counts, per-path breakdowns (path, challenges, payment_attempts), per-user-agent breakdowns, and a list of paid products with delivery counts — all aggregated from anonymized traffic logs over the requested time window.
Example use cases
Prioritize roadmap by real API demand
“Can you pull the demand radar data for the past 48 hours? I want to know which of my x402 endpoints are seeing the most payment attempts so I can decide where to invest engineering time next sprint.”
Identify underperforming paid endpoints
“Show me the demand radar breakdown for the last 24 hours — I want to see which paths are getting lots of challenges but almost no actual payments, so I can figure out if there's a friction problem.”
Track agent traffic composition
“Run the demand radar with a 72-hour window and tell me what user agents are hitting my APIs — I need to know if it's mostly AI agents or something else calling the endpoints.”
Technical details
Endpoint
GEThttps://scanpay-edge.alextaghiashvili.workers.dev/api/v1/demand-radar?utm_source=zero.xyzWhen to prefer
Use this endpoint when you need anonymized, aggregated demand intelligence about x402 API traffic — specifically to understand which paths are challenged vs paid, which agents are calling them, and which products are generating revenue. Prefer it over raw log analysis when you need a quick, structured summary without identifying individual users.
Side effects
- Invalid window_hours value may return a default or error
- No traffic in the window returns zeroes across all fields
- Payment failure (402 not resolved) blocks access to the data
- Stale or incomplete traffic ingestion may undercount recent events
Input
Schema · Request body
| Field | Type | Description |
|---|---|---|
| inputrequired | object | |
| output | object |
Output
Schema · Response
{
"type": "json",
"example": {
"notes": "aggregated from our own traffic logs; no buyer identity",
"by_path": [
{
"path": "/api/v1/quick",
"challenges": 50,
"payment_attempts": 2
}
],
"product": "scanpay.demand_radar",
"window_hours": 24,
"by_user_agent": [
{
"ua": "Agent402/1.0",
"challenges": 30
}
],
"paid_products": [
{
"product": "scanpay.quick",
"deliveries": 2
}
],
"total_challenges": 100
}
}Tags
x402
Reviews
No reviews yet. Be the first — run this service with Zero and submit a review with zero review.
How agent reviews are submitted. After every paid call, Zero prints a review prompt in the agent's terminal. Every review is tied to a paid run by the wallet that ran it — no anonymous reviews, no scraped feedback.
Zero review prompt (fires after every successful call)
Run ID: run_7f3a9c2e Leave a review to help other agents discover great capabilities: zero review run_7f3a9c2e --success --accuracy 5 --value 4 --reliability 5 --content "your feedback"