# PayerProof Revenue Stats

> PayerProof Revenue Stats is a paid API for AI agents from payerproof-production.up.railway.app, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-17).

Returns verified on-chain USDC revenue analytics for a given x402 seller address on Base, including total received, transfer count, unique payers, top-payer concentration, and largest transfers over a configurable time window up to 30 days.

## Facts

- Endpoint: POST https://payerproof-production.up.railway.app/revenue?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-17
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/payerproof-revenue-stats-a37b796d
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_LNLZsC8CDsViX7fDbiS_i

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 payerproof-revenue-stats-a37b796d -d '<json body>'
```

Example prompt: Pull the on-chain USDC revenue stats for seller address 0xAbC123... over the last 48 hours — I want total received, number of unique payers, transfer count, and what share my top payer represents.

## When to prefer this

Choose this endpoint when you need cryptographically verifiable, on-chain USDC revenue metrics for a Base address that participates in the x402 micropayment protocol — particularly when you need payer diversity metrics (unique payers, top-payer concentration) that go beyond simple balance checks. Prefer this over generic blockchain explorers when you want pre-aggregated analytics without parsing raw transaction logs yourself.

## Known failure modes

- Invalid or malformed wallet address returns an error or empty result
- Window exceeding 720 hours may be rejected or capped
- Incomplete coverage flagged when blockchain indexing hasn't caught up (complete: false, hoursCovered < hours)
- Address with zero transactions returns zeroed stats
- Network or Railway hosting downtime causes 5xx responses
- Rate limiting or payment failure for the $0.01 USDC x402 fee blocks the request

## How this service works

Verified on-chain USDC revenue stats for any x402 seller address on Base: total received, transfer count, unique payers, top-payer concentration, largest transfers. Window up to 720h (30d), incremental coverage.

## Output

A JSON object containing: the queried seller address, a window object (hours requested, whether coverage is complete, hours actually covered), totalUsdcIn (sum of USDC received), uniquePayers (distinct sender count), topPayerShare (fraction from top single payer), and transferCount (total on-chain transfers in the window).

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "window": {
   "hours": 24,
   "complete": true,
   "hoursCovered": 24
  },
  "address": "0x...",
  "totalUsdcIn": 12.34,
  "uniquePayers": 18,
  "topPayerShare": 0.22,
  "transferCount": 210
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/payerproof-revenue-stats-a37b796d/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from payerproof-production.up.railway.app](https://www.zero.xyz/host/payerproof-production.up.railway.app/llms.txt)