# Onvexia Whale Exchange Flows

> Onvexia Whale Exchange Flows is a paid API for AI agents from onvexia.com, paid per call via x402, $0.002/call, status unknown (last checked 2026-09-19).

Returns on-chain whale exchange flow data — large transfers into and out of centralized exchanges — for tracked crypto assets across multiple blockchains.

## Facts

- Endpoint: GET https://onvexia.com/v1/whales/exchange-flows
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-19
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/onvexia-whale-exchange-flows-848ae610
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_CyDPe1gSLXldftoXXU-jL

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 onvexia-whale-exchange-flows-848ae610
```

Example prompt: Pull the latest whale exchange flow data for Bitcoin — I want to see whether large holders are depositing or withdrawing from exchanges right now, as a signal for near-term price direction.

## When to prefer this

Choose this endpoint when you need on-chain intelligence specifically about large holder (whale) movements into or out of centralized exchanges — a leading indicator of sell or buy pressure. Prefer it over generic price or volume APIs when the user wants behavioral signals from labelled on-chain addresses rather than market data. It is especially valuable for crypto research, trading signal generation, and risk monitoring workflows where whale intent matters.

## Known failure modes

- Empty data array returned if no whale flows match the query parameters or asset is not covered
- Invalid or unsupported asset/chain combinations return an error or empty result
- Payment failure (x402) if USDC micropayment of $0.002 is not correctly attached
- Malformed properties filter causes a 400 bad request
- Rate limiting if too many requests are made in quick succession

## How this service works

Thousands of assets across ten chains, half a million analysed documents, labelled addresses and supply-age history reaching back to 2008 — fused into one reading per asset. REST, SQL, GraphQL and MCP.

## Output

A JSON object with a `data` array containing whale exchange flow records (inflow/outflow volumes, labelled addresses, asset identifiers, chain, timestamps) and a `meta` object with documentation links and endpoint info.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "properties": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "data": [],
  "meta": {
   "docs": "https://onvexia.com/openapi.json",
   "endpoint": "/v1/whales/exchange-flows"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/onvexia-whale-exchange-flows-848ae610/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from onvexia.com](https://www.zero.xyz/host/onvexia.com/llms.txt)