# Prysm Etherscan Provider — On-Chain Transaction & Account Data

> Prysm Etherscan Provider — On-Chain Transaction & Account Data is a paid API for AI agents from prysm-kappa.vercel.app, paid per call via x402, $0.07/call, status unknown (last checked 2026-09-15).

Proxies Etherscan API operations (e.g. account transaction lists) through Prysm's x402-paid gateway on Base mainnet using USDC.

## Facts

- Endpoint: POST https://prysm-kappa.vercel.app/api/v1/providers/etherscan
- Price: $0.07/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/prysm-etherscan-provider-on-chain-transaction-account-data-9548f25d
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Ts55oRS2Rb9iLochsVYNU

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-etherscan-provider-on-chain-transaction-account-data-9548f25d -d '<json body>'
```

Example prompt: Pull the full transaction history for Ethereum address 0xde0B295669a9FD93d5F28D9Ec85E40f4cb697BAe using the Etherscan account_txlist operation so I can see all inbound and outbound transfers.

## When to prefer this

Choose this endpoint when you need agent-ready, micropayment-gated access to Etherscan data without managing your own Etherscan API key, or when building AI agents on Base mainnet that need to pay per-query in USDC via x402. Prefer this over direct Etherscan API calls when you want a unified Prysm gateway that handles auth and billing automatically.

## Known failure modes

- Invalid or unsupported operation name returns an error — only allowlisted Etherscan operations are accepted
- Malformed Ethereum address in input parameters causes Etherscan to return an empty or error result
- Insufficient USDC balance or failed x402 payment results in a 402 Payment Required response before the query executes
- Rate limiting or Etherscan API downtime upstream can cause delayed or failed responses
- Missing required input fields (e.g. address) for the chosen operation results in 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 the Etherscan API response (e.g. a list of transactions with hashes, block numbers, timestamps, from/to addresses, values, and status), plus 'provider' set to 'etherscan' and 'operation' echoing the requested operation name.

## 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": "etherscan",
  "operation": "account_txlist"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/prysm-etherscan-provider-on-chain-transaction-account-data-9548f25d/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)