Skip to content
Intear docs

Intear API

The Intear API has prices, token data, charts, trades, transfers, balances and holders for every fungible token on NEAR. All of it comes live over one WebSocket, updated after every block, and the parts that answer once have plain HTTP endpoints too.

wss://api.intea.rs/ws
https://api.intea.rs

It’s built for apps that show token data:

  • You ask for only the fields you show, so responses stay small.
  • Updates can come after every block, or only once a value has moved by a threshold you pick.
  • History and live updates join up exactly, so a list of trades never misses or repeats one.

What you can do

Section titled “What you can do”

Token lists

Every token’s price, liquidity, volume, supply and more, filtered and sorted, updating live.

Charts

Candles in USD or NEAR, from 1 second to 1 week, with the latest candle updated live.

Trades and transfers

Every swap, transfer and transaction, as history and live, filtered by token, account or size.

Wallets

An account’s balances, and every token’s top holders and most profitable traders.

Conventions

Section titled “Conventions”
  • Tokens are identified by their contract’s account ID, like wrap.near.
  • Amounts in a token’s smallest units (balances, supplies, trade amounts) are decimal strings, since they don’t fit in a JSON number.
  • price_usd is USD per whole token. price_usd_raw is the unscaled form of 1 raw unit of the token in 1 raw unit of USDt, the indexer works in: price_usd = price_usd_raw * 10^(decimals - 6).
  • Prices and USD values sent as strings have more precision than what JSON numbers can represent. A token without a price (e.g. launched on unsupported launchpad and not bonded yet) has "0".
  • *_millis are Unix timestamps in milliseconds, and height is a NEAR block height.
  • In trades, native NEAR is always wrap.near due to historical reasons (Rhea doesn’t support native NEAR so most apps track native trades with wNEAR). In balances and transfers it’s near, in yoctoNEAR.

Next steps

Section titled “Next steps”
QuickstartFetch tokens over HTTP, keep a live token list over the WebSocket.
ConnectingHow messages, subscriptions and reconnects work.
Token fieldsEvery field a token has, and what it can be filtered and sorted by.

For agents

Section titled “For agents”

Every page is also Markdown, at its URL with .md in place of the trailing slash, like /api/reference/tokens.md, or at its URL itself for a request with Accept: text/markdown. /api/llms-full.txt has all the Intear API pages in one file, and /llms.txt lists every page of these docs.

The intear-api skill has the endpoints and rules of the Intear API for agents. To install it, save it as intear-api/SKILL.md in the agent’s skills folder, like ~/.claude/skills/ for Claude Code.