Back to Browse
ForgeMesh x402 Ads – Intent Demand Analytics
x402
ForgeMesh x402 Ads – Intent Demand Analytics is a paid API for AI agents from ads.forgemesh.io, paid per call via x402, $0.02/call, status unknown (last checked 2026-09-13).
Returns AI agent demand analytics and intent signals for a specific category across the x402 network, including probe counts, conversions, and agent-specific traffic.
Price / call$0.02
Success—
StatusUnknown
How this service works
Returns demand depth for one category: probe volume, distinct sources, buyer-class share, probed price points, and a daily time series. Use it to validate pricing before launching in that category.
Output
Returns a JSON object with a demand summary for the queried category, including total probe count (e.g. 42,000), conversion count (e.g. 900), and agent-specific probe count (e.g. 17,000), plus the category name.
Example use cases
Spot high-demand x402 categories
“Show me the intent demand data for the finance category on x402 — how many total probes and agent probes are happening, and what's the conversion count?”
Benchmark agent traffic for a new service
“Before I launch my x402 API in the data category, can you check the ForgeMesh demand analytics to see how active agent traffic is in that space?”
Monitor AI agent search trends
“I want to track what AI agents are probing most on the x402 network — pull me the demand signals for the AI tools category so I can see if interest is growing.”
Technical details
Endpoint
GEThttps://ads.forgemesh.io/api/intent/demandWhen to prefer
Use this endpoint when you need category-level intent and demand signals specifically from the x402 network — particularly to understand AI agent behavior, probe-to-conversion ratios, and agent vs. human traffic split. Prefer this over general web analytics tools when your question is specifically about what AI agents are seeking within the x402 ecosystem.
Side effects
- Invalid or unsupported category returns empty or error response
- Payment failure (insufficient USDC balance) results in 402 rejection
- Rate limiting if too many calls are made in a short window
- Stale data if analytics pipeline is lagging
- No data available for a newly created or very niche category
Input
Schema · Request body
| Field | Type | Description |
|---|---|---|
| inputrequired | object | |
| output | object |
Output
Schema · Response
{
"type": "json",
"example": {
"summary": {
"probes": 42000,
"conversions": 900,
"agent_probes": 17000
},
"category": "finance"
}
}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"