# Beggar Bot Revenue Growth Analysis (Base Mainnet)

> Beggar Bot Revenue Growth Analysis (Base Mainnet) is a paid API for AI agents from beggar-bot-demand.beggarbot.workers.dev, paid per call via x402, $0.02/call, status unknown (last checked 2026-11-04).

Analyzes revenue growth metrics for addresses or tokens on the Base mainnet blockchain, paid via x402 at $0.02 USDC per call

## Facts

- Endpoint: GET https://beggar-bot-demand.beggarbot.workers.dev/v1/revenuegrowth?utm_source=zero.xyz
- Price: $0.02/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-04
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/beggar-bot-revenue-growth-analysis-base-mainnet-70a8f313
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_3X5a553Ue5VsE4OxH3DIV

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 beggar-bot-revenue-growth-analysis-base-mainnet-70a8f313
```

Example prompt: Can you pull the revenue growth analysis for the USDC contract 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Base mainnet using Beggar Bot?

## When to prefer this

Choose this endpoint when you need revenue growth computation specifically on Base mainnet (or optionally Base Sepolia testnet), and you want on-chain USDC-denominated revenue trend data. It is distinct from risk or verification endpoints in the same suite — use /v1/revenuegrowth when the goal is understanding revenue trajectory rather than verifying transactions or assessing wallet risk. Best when building DeFi dashboards, investor reports, or protocol monitoring agents that need growth-oriented financial metrics.

## Known failure modes

- Payment not provided or insufficient USDC — returns HTTP 402 requiring $0.02 USDC payment via x402
- Invalid or unrecognized address parameter — returns error or empty data
- Network parameter mismatch — if base-sepolia is specified but mainnet data is requested
- Rate limiting or Cloudflare Worker timeout — returns 5xx error
- No on-chain revenue data found for the queried address — returns empty or null metrics

## How this service works

Paid: /v1/verify, /v1/risk, /v1/receipt cost $0.01 USDC per call on Base mainnet via x402 (payTo 0x719227f384b66BFEF00093D6d8d32fA9dC2B40e7); utilities analyze Base mainnet (USDC 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913) by default, network=base-sepolia optional; /v1/receipt/verify and discovery files are free. Operator: Beggar Bot.

## Output

Returns JSON data containing revenue growth metrics for the queried address or token on Base mainnet, likely including growth rates, period-over-period comparisons, and trend indicators derived from on-chain USDC flows.

## Request schema (JSON Schema)

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

## Response schema (JSON Schema)

```json
{
 "type": "json"
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/beggar-bot-revenue-growth-analysis-base-mainnet-70a8f313/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from beggar-bot-demand.beggarbot.workers.dev](https://www.zero.xyz/host/beggar-bot-demand.beggarbot.workers.dev/llms.txt)