# Prysm Birdeye Provider — On-Chain Token Data via x402

> Prysm Birdeye Provider — On-Chain Token Data via x402 is a paid API for AI agents from prysm-kappa.vercel.app, paid per call via x402, $0.08/call, status unknown (last checked 2026-09-14).

Proxies Birdeye on-chain token analytics operations (e.g. token overview) to AI agents over the x402 micropayment protocol on Base mainnet for $0.08 USDC per call.

## Facts

- Endpoint: POST https://prysm-kappa.vercel.app/api/v1/providers/birdeye
- Price: $0.08/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/prysm-birdeye-provider-on-chain-token-data-via-x402-032e6820
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_-_5Ik-oWFVfNOstxcgBEc

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 prysm-birdeye-provider-on-chain-token-data-via-x402-032e6820 -d '<json body>'
```

Example prompt: Pull the Birdeye token overview for the token at address So11111111111111111111111111111111111111112 on Solana — I need price, market cap, volume, and liquidity stats.

## When to prefer this

Choose this endpoint when an AI agent needs real-time on-chain token analytics from Birdeye and wants to pay per-call via x402 micropayments on Base mainnet in USDC without managing a Birdeye API key directly. Ideal for agent workflows that need token overviews, price data, or liquidity metrics for DeFi research or portfolio monitoring.

## Known failure modes

- Invalid or unsupported operation name returns an error — only allowlisted Birdeye operations are accepted
- Malformed or non-existent token address returns empty or error data from Birdeye
- Insufficient USDC balance or failed x402 payment results in a 402 Payment Required response
- Rate limiting or Birdeye upstream outage may cause 5xx errors
- Missing required input parameters for the chosen operation causes a validation error

## How this service works

Prysm sells paid, agent-ready provider capabilities over x402 on Base mainnet using USDC.

## Output

Returns a JSON object with a 'data' field containing Birdeye's response for the requested operation (e.g. token_overview), plus 'provider' ('birdeye') and 'operation' fields confirming what was called. The data payload includes token metrics such as price, market cap, 24h volume, liquidity, holder count, and price change percentages.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "input": {
   "type": "object",
   "description": "Provider-specific operation parameters.",
   "additionalProperties": true
  },
  "operation": {
   "type": "string",
   "description": "Allowlisted operation for the selected provider."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "data": {},
  "provider": "birdeye",
  "operation": "token_overview"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/prysm-birdeye-provider-on-chain-token-data-via-x402-032e6820/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from prysm-kappa.vercel.app](https://www.zero.xyz/host/prysm-kappa.vercel.app/llms.txt)