# Foundry x402 Seller Revenue Analytics

> Foundry x402 Seller Revenue Analytics is a paid API for AI agents from minty-sprout.onrender.com, paid per call via x402, $0.003/call, status unknown (last checked 2026-11-01).

Returns on-chain USDC payment analytics for an x402 seller address on Base over the last 24 hours, including payment count, distinct payers, total received, and top payer concentration.

## Facts

- Endpoint: POST https://minty-sprout.onrender.com/v1/x402-seller-revenue?utm_source=zero.xyz
- Price: $0.003/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-01
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/foundry-x402-seller-revenue-analytics-b1c57545
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_q2rFv9Hx3wzzfCwTpFcWw

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 foundry-x402-seller-revenue-analytics-b1c57545 -d '<json body>'
```

Example prompt: Can you pull the last 24 hours of x402 on-chain revenue for seller address 0xB3cDDccEe6B150c8efFD55B961afc0Ecefe7f247 on Base — I want to see total USDC received, how many distinct payers there were, and whether one payer is dominating the volume?

## When to prefer this

Use this endpoint when you need real, deterministic on-chain proof of x402 payment demand for a specific seller address on Base — not estimates or off-chain claims. It is the right choice when doing seller due diligence before paying an x402 API, auditing your own x402 revenue, or detecting anomalous payer concentration such as wash volume or self-testing. Prefer this over x402-preflight when you specifically need on-chain payment history rather than contract configuration facts.

## Known failure modes

- Invalid or malformed 0x address returns an error or empty result
- Address with no x402 payments in the last 24 hours returns zero values
- Network congestion or RPC issues may cause delayed or incomplete on-chain reads
- Address not on Base network may return no results
- Rate limiting or payment failure if x402 micropayment of $0.003 USDC is not resolved

## How this service works

Real x402 demand from the chain: USDC an address (e.g. a seller's payTo) received on Base in the last 24 hours, with payment count, distinct payers, total, and top payers with the largest payer's share (a high share suggests self-testing or wash volume). Input: 0x address. Deterministic, no LLM.

## Output

A JSON object containing the queried address, network identifier (eip155:8453 for Base), total USDC received in the last 24 hours, number of individual payment transactions, count of distinct payer addresses, an array of top payers with their USDC amounts, and the largest payer's share of total volume as a ratio (values near 1.0 indicate concentration risk such as self-testing or wash volume).

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "input": {
   "type": "string",
   "maxLength": 8000,
   "description": "Address that receives x402 payments (a seller's payTo), 0x + 40 hex characters"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "address": "0xB3cDDccEe6B150c8efFD55B961afc0Ecefe7f247",
  "network": "eip155:8453",
  "payments": 13,
  "top_payers": [
   {
    "usdc": 4.76,
    "payer": "0x8F10B468b06c6FD214B65F87778827F7D113f996"
   }
  ],
  "window_hours": 24,
  "usdc_received": 4.98,
  "distinct_payers": 7,
  "top_payer_share": 0.956
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/foundry-x402-seller-revenue-analytics-b1c57545/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from minty-sprout.onrender.com](https://www.zero.xyz/host/minty-sprout.onrender.com/llms.txt)