Skip to main content

Read data

SDK reads return an ApiResponse<T>:
requestId is the correlation value to include in support reports. checkpoint identifies the indexed state when supplied. A cursor is opaque and must be returned unchanged.

Markets

Supported candle intervals are 60, 300, 900, 3,600, 14,400, and 86,400 seconds.

Accounts and portfolio

Addresses must be 20-byte EVM addresses. The SDK rejects malformed input before making a request.

Positions

positions.risk is a live execution-oriented read. Indexed position history and live risk may be observed at different blocks; use the response source/checkpoint and action preparation snapshot rather than merging them as if atomic.

Vault and staking

Vault account history includes deposits, withdrawals, and claims. Staking account history includes stake changes and rewards.

Orders and transactions

Order status is canonical onchain outcome data. Offchain automatic-intent and relayed-action lifecycle is accessed through the preparation/submission receipt APIs described in Relayed actions and Orders.

Direct snapshot reads

Action preparation constructs typed contract calls and runs them with ChainReader.readAtBlock. The native and provider adapters encode a Multicall3 aggregate3 request, pin it to one block, and decode named ABI results. The public API can supply this bounded action snapshot when no direct reader is configured. Native balance and transaction-receipt reads require a direct reader.

Pagination

Do not manufacture, decode, reorder, or share cursors across endpoints. A page may expose null when no further page exists.
Last modified on July 23, 2026