# Synapse API — Gnosis Chain Transaction History

> Synapse API — Gnosis Chain 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-14).

Retrieves paginated transaction history for addresses on the Gnosis blockchain network

## Facts

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

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-gnosis-chain-transaction-history-46cc973b -d '<json body>'
```

Example prompt: Pull me the last 25 transactions sent from 0xABC123... on Gnosis chain, sorted newest first, and include metadata so I can see token details.

## When to prefer this

Choose this endpoint when you need on-chain transaction history specifically for the Gnosis blockchain (xDai chain). It supports flexible filtering by address, block range, transaction category, and sort order with cursor-based pagination — ideal for auditing wallets, building portfolio trackers, or monitoring DeFi protocol activity on Gnosis. Not suitable for other chains like Ethereum mainnet, Polygon, or Arbitrum, which would require sibling endpoints.

## Known failure modes

- Invalid address format returns a validation error
- Block range too large may time out or return partial results
- Invalid category string causes a 400 bad request
- Missing both fromAddress and toAddress may return empty or error
- pageKey from a different query context may cause inconsistent pagination
- Network congestion or RPC node issues may cause latency spikes or 503 errors

## 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 Gnosis blockchain matching the specified filters, including sender/receiver addresses, block numbers, transaction hashes, and optionally full metadata such as token names, decimals, and values. A pageKey is included for cursor-based pagination through 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-gnosis-chain-transaction-history-46cc973b/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)