# Synapse API — Berachain Transaction History

> Synapse API — Berachain Transaction History is a paid API for AI agents from synapse-api-brown.vercel.app, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-15).

Retrieves paginated transaction history for addresses on the Berachain blockchain network

## Facts

- Endpoint: POST https://synapse-api-brown.vercel.app/api/berachain/tx/history
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/synapse-api-berachain-transaction-history-76e9f973
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_eWseGo5DSMfI-Fl5r5ThX

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 synapse-api-berachain-transaction-history-76e9f973 -d '<json body>'
```

Example prompt: Pull the last 25 transactions from Berachain address 0xAbC...123, including both sent and received transfers, ordered from newest to oldest, and include token metadata.

## When to prefer this

Use this endpoint when you need on-chain transaction history specifically for the Berachain network with flexible filtering by address, block range, asset category, and pagination. Prefer this over generic blockchain explorers when you need structured, programmatic access to Berachain tx data with metadata, and when pay-per-call pricing via x402 fits your usage pattern better than a subscription.

## Known failure modes

- Invalid or malformed address returns a 400 error
- Unsupported category value causes a validation error
- Invalid block range (fromBlock > toBlock) returns an error
- Expired or invalid pageKey may return an empty or incorrect result set
- Payment not received (x402 flow incomplete) returns 402 Payment Required
- Rate limiting or service downtime returns 500 or 503 error

## How this service works

High-speed API suite for AI processing, web scraping, and smart data utilities across 57+ blockchain networks. Pay-per-call via x402.

## Output

Returns a paginated list of transaction records for the queried Berachain address(es), including asset transfer details, block numbers, transaction hashes, token metadata (if requested), and a pageKey for fetching subsequent pages.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "order": {
   "enum": [
    "asc",
    "desc"
   ],
   "type": "string"
  },
  "pageKey": {
   "type": "string"
  },
  "toBlock": {
   "type": "string"
  },
  "category": {
   "type": "array",
   "items": {
    "type": "string"
   }
  },
  "maxCount": {
   "type": "number"
  },
  "fromBlock": {
   "type": "string"
  },
  "toAddress": {
   "type": "string"
  },
  "fromAddress": {
   "type": "string"
  },
  "withMetadata": {
   "type": "boolean"
  },
  "excludeZeroValue": {
   "type": "boolean"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/synapse-api-berachain-transaction-history-76e9f973/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from synapse-api-brown.vercel.app](https://www.zero.xyz/host/synapse-api-brown.vercel.app/llms.txt)