Skip to main content
Realtime tools wrap Allium’s Realtime APIs as MCP tool calls. They’re the fastest path to current and recent on-chain state: no schema discovery, no SQL, no query queue.
Call realtime_get_supported_chains once per session before any other realtime tool, and cache the result. It returns a map of endpoint path → supported chain names, and it’s the only realtime tool that doesn’t consume credits. Passing an unsupported chain gives you a silent empty result or an error.

Available tools

Discovery

Prices

Wallets

Holdings & PnL

Tokens & assets

Hyperliquid trading data has its own five tools — see Hyperliquid.

Every tool names its own docs

Each realtime tool’s description ends with a browse_docs path pointing at the REST endpoint’s full documentation — supported chains, edge cases, pagination, and response shape.
That’s the authoritative reference for parameters. The examples below cover the shape of a call, not every field.

Batching

Most realtime tools take a list of targets in one call, but the field name isn’t the same everywhere — check the tool’s input schema, or this table:

Tool usage

Latest prices

One tool handles single and batch lookups — pass one entry or many in payloads.
with_liquidity_info: true adds total_liquidity_usd. See token liquidity filtering for when that matters.

Price history

Paginate with the cursor parameter.

Wallet balances

Multi-chain is just multiple entries in one call — there’s no separate multi-chain tool.

Transactions

Returns enriched activity — decoded activities, asset transfers, and address labels — not raw transaction rows.

DeFi positions

Holdings and PnL

realtime_holdings_history gives aggregated USD holdings over time. The four PnL tools split along two axes: current versus historical, and whole-wallet versus per-token.
The _history variants take start_timestamp, end_timestamp, and granularity alongside addresses. Of the holdings tools, only realtime_holdings_history paginates — the PnL history tools return their full range in one response.

SQL or realtime?

Use realtime tools

Current state, a specific wallet or token, recent history. Single-digit-second responses, no query queue.

Use SQL

Aggregations across many addresses, full history, joins across verticals, anything you want to chart. See SQL & queries.
All realtime tools except realtime_get_supported_chains consume Developer Units, at 20–60 DU per call, multiplied by the number of batched inputs. See Billing & limits.

Realtime APIs

The REST endpoints behind these tools

Prices API

Full prices reference

Wallets API

Full wallets reference

Hyperliquid tools

Perps info, fills, orders, orderbooks