Pinax API

Quick reference for AI agents using Pinax API. The authoritative machine-readable contract is GET /openapi.

• Base URL: https://api.pinax.network
• OpenAPI spec: GET /openapi — authoritative reference, use for schema details
• x402 discovery: GET /.well-known/x402 — payment discovery metadata; x402 enforcement is handled at the proxy layer
• Docs: https://app.pinax.network/docs
• FAQ: https://app.pinax.network/help
• Canonical skill file: GET /SKILL.md

All responses are JSON: { "data": [...], ... } for data endpoints, or a top-level object for monitoring. Errors follow { "status": <code>, "code": "<slug>", "message": "<text>" }.

Authentication

Most endpoints require a Bearer token from The Graph Market:

Authorization: Bearer <your-token>

An X-Api-Key: <your-api-key> header is accepted as an alternative.

Unauthenticated endpoints (no header required, no usage charge):

• GET /llms.txt
• GET /openapi
• GET /.well-known/x402
• GET /SKILL.md
• GET /v1/health
• GET /v1/version
• GET /v1/networks
• GET /v1/evm/dexes
• GET /v1/svm/dexes
• GET /v1/tvm/dexes
• GET /v1/polymarket/markets
• GET /v1/hyperliquid/dexes
• GET /v1/hyperliquid/markets

Errors

Error responses share a common envelope:

{
  "status": 400,
  "code": "bad_query_input",
  "message": "Invalid network ID"
}

Common codes: bad_query_input (400), authentication_failed (401), route_not_found (404), bad_database_response (500), database_connection_failed (503).

Capabilities

Map a goal to the relevant dataset and endpoint family:

• Token API: look up wallet balances and transfer history — /v1/{evm,svm,tvm}/balances, /v1/{evm,svm,tvm}/transfers
• Token API: track balance changes over time — /v1/evm/balances/historical, /v1/evm/balances/historical/native
• Token API: resolve token metadata — /v1/{evm,svm,tvm}/tokens, /v1/{evm,svm,tvm}/tokens/native
• Token API: find holders of a token — /v1/{evm,svm}/holders, /v1/evm/holders/native, /v1/evm/nft/holders
• Token API: trace DEX swaps and liquidity pools — /v1/{evm,svm,tvm}/swaps, /v1/{evm,svm,tvm}/pools, /v1/{evm,svm,tvm}/dexes
• Token API: get OHLC time-series — /v1/{evm,svm,tvm}/pools/ohlc
• Token API: list a wallet's NFT holdings and activity — /v1/evm/nft/ownerships, /v1/evm/nft/transfers, /v1/evm/nft/sales, /v1/evm/nft/items, /v1/evm/nft/collections
• Prediction Markets: discover markets, OI, and per-user PNL — /v1/polymarket/markets, /v1/polymarket/markets/ohlc, /v1/polymarket/markets/oi, /v1/polymarket/markets/activity, /v1/polymarket/users, /v1/polymarket/users/positions, /v1/hyperliquid/outcomes, /v1/hyperliquid/outcomes/ohlc, /v1/hyperliquid/outcomes/trades, /v1/hyperliquid/outcomes/users, /v1/hyperliquid/outcomes/users/positions, /v1/hyperliquid/outcomes/users/activity
• Perp Exchanges: discover markets, OHLC, OI, liquidations, and per-user PnL — /v1/hyperliquid/markets, /v1/hyperliquid/markets/ohlc, /v1/hyperliquid/markets/oi, /v1/hyperliquid/markets/liquidations, /v1/hyperliquid/users, /v1/hyperliquid/users/positions, /v1/hyperliquid/vaults
• Discover supported chains and protocols (free) — /v1/networks, /v1/{evm,svm,tvm}/dexes, /v1/hyperliquid/dexes

Common patterns

These conventions apply across the data endpoints unless overridden.

Pagination

Batched filters

Any parameter marked "supports multiple" accepts either a repeated query param (?contract=0x..&contract=0x..) or a comma-separated list (?contract=0x..,0x..). This applies to most ID-shaped filters (address, contract, mint, token_id, pool, transaction_id, signature, etc.).

Time ranges

Event and historical endpoints accept either block or time windows:

• start_time / end_time — ISO 8601 or Unix timestamp (seconds)
• start_block / end_block — integer block number (slot for SVM)

Intervals

Historical and OHLC endpoints use an interval enum: 1h, 4h, 1d (default), 1w. A few endpoints accept additional values (e.g. /v1/polymarket/users supports 30d); the OpenAPI per-endpoint schema is authoritative.

Network discovery

Call GET /v1/networks first to enumerate supported network IDs (mainnet, base, bsc, solana, tron, …) and see how current each indexer is via indexed_to.

Worked example

Fetch WETH balances for a wallet on Ethereum:

1. GET /v1/networks                              → confirm "mainnet" is indexed
2. GET /v1/evm/tokens?network=mainnet
        &contract=0xc02aaa39b223fe8d0a0e5c4f27ead9083c756cc2
                                                 → resolve WETH metadata
3. GET /v1/evm/balances?network=mainnet
        &address=0x<wallet>
        &contract=0xc02aaa39b223fe8d0a0e5c4f27ead9083c756cc2
                                                 → current balance
4. GET /v1/evm/balances/historical?network=mainnet
        &address=0x<wallet>
        &contract=0xc02aaa39b223fe8d0a0e5c4f27ead9083c756cc2
        &interval=1d&start_time=2026-01-01       → time-series

Monitoring

EVM endpoints

Ethereum and compatible chains (Ethereum, Base, BSC, Polygon, Arbitrum, …).

Tokens (ERC-20)

Balances

Transfers

Holders

DEX / swaps / pools

Swap response includes several address fields:

• transaction_from — onchain transaction initiator
• caller — account or contract that invokes the swap
• user — normalized user-oriented swap address; prefer this for new integrations
• sender, recipient — legacy fields, slated for deprecation in a future major release

NFTs

SVM endpoints

Solana Virtual Machine chains.

Tokens (SPL)

Balances

Transfers

Holders

In /v1/svm/holders, the owner field is the wallet and token_account is the Associated Token Account (ATA).

DEX / swaps / pools

Account owner

TVM endpoints

TRON Virtual Machine chains. Balances and holders are not yet exposed.

Tokens (TRC-20)

Transfers

DEX / swaps / pools

TVM swap address fields follow the same user / sender / recipient convention as EVM (prefer user).

Polymarket

Prediction-market data for the Polygon-based Polymarket CTF exchange. Outcome token prices are quoted in USDC per share (0–1).

Markets

Users

Platform

Aggregate volume, open interest, and fees across all Polymarket markets.

Hyperliquid

Trading data for the Hyperliquid L1 — core perps, @N-indexed spot pairs, builder-deployed DEXes (xyz, cash, …), and HIP-4 prediction-market outcomes. The coin parameter is the canonical identifier across all /v1/hyperliquid/markets/* and /v1/hyperliquid/users/* endpoints: unprefixed for core perps (BTC), @N for spot (@107), and <dex>:<symbol> for builder DEXes (xyz:SILVER). Discover the live DEX set via GET /v1/hyperliquid/dexes.

HIP-4 outcome markets are served by the dedicated /v1/hyperliquid/outcomes/* family — #N coin values and dex=outcome are rejected on the markets/users endpoints. Outcome coins use #<outcome_id*10 + side_index> encoding (side_index is 0 or 1, e.g. #1720 = outcome 172 / "Yes", #1721 = outcome 172 / "No").

Markets

Users

Vaults

Outcomes (HIP-4 prediction markets)

Platform

Cross-coin, cross-DEX time-series of volume (taker-derived buy_volume / sell_volume), fees, trade counts (true match count), and a liquidation slice.