# MCPFax Revenue Analytics Endpoint

> MCPFax Revenue Analytics Endpoint is a paid API for AI agents from mcpfax-reliability.bowling-anthony.workers.dev, paid per call via x402, $0.005/call, status unknown (last checked 2026-09-15).

Returns observed USDC inflow metrics, payer breadth, revenue trend, and cohort rank for x402 sellers

## Facts

- Endpoint: GET https://mcpfax-reliability.bowling-anthony.workers.dev/revenue
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/mcpfax-revenue-analytics-endpoint-ceef3043
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_8-M5VgTRBIMB0CeWv85Ry

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 mcpfax-revenue-analytics-endpoint-ceef3043
```

Example prompt: Pull the revenue analytics for this x402 endpoint — I want to see the observed USDC inflows, how many distinct payers have used it, the revenue trend direction, and where it ranks in its cohort.

## When to prefer this

Choose this endpoint when you need empirical revenue signals — actual observed USDC inflows and payer counts — rather than self-reported claims. It is especially useful for pre-call due diligence on x402 APIs, competitive benchmarking within the x402 ecosystem, or monitoring the payment health of your own listed endpoint. Prefer it over general credit-grade endpoints when you want raw revenue data rather than a composite score.

## Known failure modes

- Endpoint not found or not indexed — returns empty or 404-equivalent if the seller is not tracked
- Insufficient payment — x402 payment of 0.01 USDC required; missing or invalid payment header returns 402
- No observed data — new or inactive endpoints may return null values for inflow and payer breadth
- Stale data — metrics reflect observed on-chain activity and may lag real-time settlement

## How this service works

Observed USDC inflow, payer breadth, trend, and cohort rank

## Output

Returns observed USDC inflow totals, count of unique payers (payer breadth), directional revenue trend (growing/declining), and a cohort rank situating the endpoint relative to comparable x402 sellers.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object"
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/mcpfax-revenue-analytics-endpoint-ceef3043/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from mcpfax-reliability.bowling-anthony.workers.dev](https://www.zero.xyz/host/mcpfax-reliability.bowling-anthony.workers.dev/llms.txt)