# ForgeMesh Network x402 Intent Stats

> ForgeMesh Network x402 Intent Stats is a paid API for AI agents from ads.forgemesh.io, paid per call via x402, $0.005/call, status unknown (last checked 2026-09-14).

Returns network-wide x402 protocol statistics including event totals, service activity, user-agent classification splits, and ad activity across the ForgeMesh network

## Facts

- Endpoint: GET https://ads.forgemesh.io/api/network/stats
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/forgemesh-network-x402-intent-stats-1b4aaaf8
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_OizOJGyNsa5FCskUR3J0O

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability forgemesh-network-x402-intent-stats-1b4aaaf8
```

Example prompt: Can you pull the latest network-wide x402 stats from ForgeMesh — I want to see the event totals, ad activity, and how the user-agent classification is split right now?

## When to prefer this

Use this endpoint when you need a high-level, network-wide view of x402 protocol activity — event volumes, ad transactions, and autonomous-agent vs human traffic classification — rather than stats for a specific endpoint or category. Prefer this over the sibling 'top requested endpoints' endpoint when you want aggregate totals and UA split rather than ranked lists.

## Known failure modes

- Payment not provided or insufficient — 402 Payment Required response, endpoint requires $0.005 USDC per call
- Network or service unavailability — 500 or 503 error
- Rate limiting if too many calls in quick succession — 429 Too Many Requests
- Empty or stale stats if no recent x402 events have occurred on the network

## How this service works

Returns network-wide totals: total x402 events, service count, and a UA classification breakdown (agent vs browser vs bot). Use it to benchmark your service's agent-traffic share against the network.

## Output

Returns a JSON object with: totals (aggregate event counts across the x402 network), ad_activity (metrics about advertising transactions or impressions), and classification (array breaking down traffic by user-agent type, e.g. autonomous agents vs humans vs bots)

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "properties": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "totals": {
   "events": 190214,
   "services": 3
  },
  "classification": [
   {
    "n": 69000,
    "ua_class": "agent"
   }
  ]
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/forgemesh-network-x402-intent-stats-1b4aaaf8/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from ads.forgemesh.io](https://www.zero.xyz/host/ads.forgemesh.io/llms.txt)