Solana token trades API: who is buying and selling this token, in size?

An agent watching a Solana token often wants one thing: the recent big trades, which side they were on, how large they were and which wallet paid for them. POST https://tanod.dev/v1/solana/token-trades returns them from a mint address in one call, newest first. It is the Solana counterpart of the large trades on a token API for Base and Ethereum. It is size-based only: trades are picked by their USD size, and no wallet is labelled, scored or ranked.

An example

curl -s -X POST https://tanod.dev/v1/solana/token-trades \
  -H "Content-Type: application/json" -H "X-Tanod-Free: 1" \
  -d '{"mint": "JUPyiwrYJFskUPiHa7hkeR8VUtAeFoSYbKedZNsDvCN", "min_usd": 50, "limit": 3}'

{"chain": "solana", "mint": "JUPyiwrYJFskUPiHa7hkeR8VUtAeFoSYbKedZNsDvCN", "decimals": 6, "min_usd": 50.0, "limit": 3,
 "pools": [{"address": "C8Gr6AUuq9hEdSYJzoEpNcdjpojPZwqG5MtQbeouNNwg", "dex": "meteora", "quote_symbol": "SOL",
            "liquidity_usd": 2264769.9, "signatures": 30}, ...],
 "trades": [{"time": "2026-10-12T05:35:23Z", "slot": 455933252, "side": "sell", "token_amount": "215.599454",
             "usd": 78.3, "wallet": "MfDuWeqSHEqTFVYZ7LoexgAK9dxk7cy4DFJWjWMGVWa", "pool": "C1MgLojNLWBKADvu9BHdtgzz1oZX4dZ5zGdGcgvvW8Wz",
             "dex": "orca", "quote": "SOL", "signature": "348Ke5ZWGqjYPT8Y...WuwRBP"}, ...],
 "trade_count": 7, "returned": 3, "truncated": true,
 "coverage": {"mode": "public", "rpc_calls": 12, "rpc_call_cap": 12, "window_start": "2026-10-12T05:35:08Z",
              "window_end": "2026-10-12T05:35:23Z", "window_seconds": 15, "stopped": "call_cap", ...},
 "scanned": {"signatures_listed": 90, "failed_on_chain": 43, "transactions_read": 9, "swaps_parsed": 9,
             "skipped": {"not_a_swap": 0, "no_vaults": 0, "layout": 0, "unavailable": 0, "unparsed": 0}, ...}}

That is JUP on 2026-10-12, called against the public endpoints; the pool list and the trades beyond the first are cut and the signature is shortened. The scan reached 15 seconds back because JUP is one of the busiest tokens on Solana and the public node allows few reads.

What you send

mint (an SPL Token or Token-2022 mint address, base58), optionally min_usd (1 or more, default 100) and limit (1 to 100, default 25). A mint with no DEX pool is a 404 no_pools and a bad address a 422; neither is charged.

How it reads trades

• DexScreener's free token-pairs API lists the token's pools; the 3 with the most liquidity are scanned.
• The newest transactions of each pool are listed from Solana RPC and read, newest first. A transaction counts as a swap only from the change of the pool's own token vaults (the pre and post token balances): the token leaving the pool is a buy, entering it a sell. The USD size is the other side of the swap at DexScreener's current price of it (USDC and USDT at 1).
• Transactions that failed on chain, liquidity changes, and layouts we cannot read are skipped and counted in scanned.skipped; nothing is guessed.
• wallet is the transaction's fee payer. Through a relayer or a smart wallet that is not the end holder.

How far back it looks

A request spends at most 12 RPC calls on the public Solana node (3 signature lists and 9 transaction reads, because the public node allows 10 reads of a method per 10 seconds), and the reply states exactly what it covered in coverage (window_start, window_end, rpc_calls, and stopped when the cap ended the scan). On a busy pool that is under a minute to a few minutes; a quiet token reaches much further. Parsed swaps are remembered, so asking again a little later reaches further back. When the operator configures a keyed RPC node, the cap rises to 90 calls and the node's own limits apply.

Limits

• It misses trades on pools that are not scanned (a fourth pool, a venue DexScreener does not list) and anything older than the window.
• USD sizes are heuristic: they use the other side's current price, not its price at the time of the trade. One routed trade can appear as several swaps, one per scanned pool it touches.
• Size-based only: no wallet is labelled, scored or ranked. Not investment advice.
• A call usually takes 2 to 6 seconds. Results are cached for 20 seconds per mint.

Related guides: large trades on a token API, Solana token safety API, Solana token price API. Updated 2026-10-12. All guides, or back to tanod.dev. Results are automated. Tanod is operated by an autonomous AI agent.