# ChainAnalyzer — Address Transaction Counterparties

> ChainAnalyzer — Address Transaction Counterparties is a paid API for AI agents from chain-analyzer.com, paid per call via x402, $0.25/call, status unknown (last checked 2026-10-21).

Returns the top transaction counterparties for a blockchain address, including entity labels, categories, per-counterparty transfer counts, and observed flow totals, with 24-hour result caching.

## Facts

- Endpoint: GET https://chain-analyzer.com/api/v1/x402/address/:address/counterparties?utm_source=zero.xyz
- Price: $0.25/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-21
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/chainanalyzer-address-transaction-counterparties-624c115f
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_9aiYVvkm14P_1Jjb_aoZO

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 chainanalyzer-address-transaction-counterparties-624c115f
```

Example prompt: Who are the top transaction counterparties for the Ethereum address 0xAbC123...def on chain ethereum — show me their entity labels, categories, and how much has flowed between them?

## When to prefer this

Use this endpoint when you need a quick, labeled summary of who a blockchain address has been transacting with — particularly for compliance checks, due diligence, or AML investigations — and want entity categories and flow totals without building your own graph analysis. Prefer this over raw transaction list endpoints when you need pre-resolved entity labels and ranked counterparty aggregation rather than raw tx data.

## Known failure modes

- Invalid or malformed blockchain address returns a 400 error
- Unsupported chain identifier returns an error or empty result
- Address with no transaction history returns an empty counterparty list
- Cache miss on a fresh address may add latency while a new scan runs
- Payment failure (x402) blocks the request from executing

## How this service works

Top transaction counterparties for an address with entity labels, category, per-counterparty transfer counts and observed flow totals. Reuses a scan of the same address from the last 24 hours when one exists, otherwise runs a fresh scan.

## Output

A ranked list of the top counterparties for the queried address, each annotated with entity label (e.g. Binance, Tornado Cash), entity category (e.g. exchange, mixer, DeFi protocol), number of transfers, and observed inflow/outflow totals. Results are served from a cached scan if one was run within the last 24 hours.

## Request schema (JSON Schema)

```json
{
 "properties": {
  "input": {
   "properties": {
    "queryParams": {
     "type": "object",
     "properties": {
      "chain": {
       "type": "string"
      }
     }
    }
   }
  },
  "output": {
   "properties": {
    "example": {}
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/chainanalyzer-address-transaction-counterparties-624c115f/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from chain-analyzer.com](https://www.zero.xyz/host/chain-analyzer.com/llms.txt)