# Synapse API — Katana Transaction History

> Synapse API — Katana 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-13).

Retrieves paginated transaction history for addresses on the Katana blockchain network, with filtering by block range, category, and address.

## Facts

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

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-katana-transaction-history-07de052e -d '<json body>'
```

Example prompt: Pull the last 100 transactions sent from wallet 0xAbC...123 on Katana, sorted newest first, including metadata and excluding zero-value transfers.

## When to prefer this

Choose this endpoint when you need historical transaction data specifically from the Katana blockchain network, with fine-grained control over block range, address direction, transaction categories, and result ordering. It is well-suited for agents performing on-chain audits, portfolio tracking, or building dashboards that require paginated access to wallet activity on Katana.

## Known failure modes

- Invalid or malformed address returns an error or empty result
- fromBlock greater than toBlock returns an error or no results
- Invalid category enum value may return an error
- Exceeding maxCount limits may result in truncated or errored responses
- pageKey from a different query context may produce unexpected results
- Network or upstream Katana RPC unavailability causes 5xx errors
- Payment failure via x402 protocol results in 402 response blocking the call

## 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 transactions on the Katana network matching the specified filters, including transaction details such as from/to addresses, block numbers, categories, and optionally full metadata. Supports cursor-based pagination via pageKey for large result sets.

## 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-katana-transaction-history-07de052e/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)