# Onvexia Whale Wallet Transaction History

> Onvexia Whale Wallet Transaction History 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).

Retrieves the on-chain transaction history for a specific wallet address, enriched with whale-tracking and labelled-address analytics across multiple blockchains.

## Facts

- Endpoint: GET https://onvexia.com/v1/whales/wallets/%7Baddress%7D/transactions
- 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-wallet-transaction-history-52081486
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Sh7_WocKMoBqDLemOBHN7

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-wallet-transaction-history-52081486
```

Example prompt: Pull the full transaction history for wallet address 0x3f5CE5FBFe3E9af3971dD833D26bA9b5C936f0bE using Onvexia's whale analytics — I want to see every on-chain move that address has made.

## When to prefer this

Choose this endpoint when you need transaction history for a specific wallet address with the added context of Onvexia's whale labelling, address tagging, and multi-chain coverage. Prefer it over generic block explorers when you need enriched, analytics-ready transaction data rather than raw chain data, especially for known whale addresses or labelled institutional wallets.

## Known failure modes

- Invalid or malformed wallet address returns empty data array or 400 error
- Address not indexed on any supported chain returns empty data array
- Payment of 0.002 USDC not fulfilled results in 402 Payment Required
- Rate limiting or quota exceeded returns 429 error
- Network-specific address format mismatch may return no results

## 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 response containing a data array of on-chain transactions for the specified wallet address, including transfer details and metadata, plus a meta object with documentation links and the endpoint path. Transactions are enriched with Onvexia's labelled-address intelligence spanning multiple chains.

## 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/wallets/{address}/transactions"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/onvexia-whale-wallet-transaction-history-52081486/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)