> ## Documentation Index > Fetch the complete documentation index at: https://docs.range.org/llms.txt > Use this file to discover all available pages before exploring further. # MCP Tools Reference > All 74 tools available in the Range MCP server, organized by category. The Range MCP server exposes **74 tools**, strictly read-only, across 9 categories: workspace and account data, alerts, counterparties, screening and risk, and blockchain analytics (address intelligence, transfers, network/token stats, and explorer utilities). Every tool returns JSON and handles errors gracefully — your AI client receives a clear error message rather than an exception when something goes wrong. **Endpoint:** `https://api.range.org/ai/mcp` **Auth:** `Authorization: Bearer ` (or `x-api-key: `) Tools marked **Workspace-scoped** require a workspace API key (`.`), not a legacy/global key. Calling a workspace-scoped tool with a legacy key returns a clear error asking for a workspace-scoped key instead of silently returning empty or wrong data. See the [Quickstart](/ai/quickstart) for details on key types. *** ## Workspace & Account Management Accounts, balances, groups, and connections tracked inside your Range workspace — wallets, exchange accounts, custodial accounts, multisigs, and bank accounts. List accounts tracked in the caller workspace: on-chain wallets, exchange accounts, custodial accounts, multisigs, and bank accounts. Supports filtering by group, account type, connection provider, chain, or connection id. Use this for portfolio/treasury overviews before drilling into a single account with `get_account`. **Workspace-scoped.** | Parameter | Type | Required | Description | | --------------- | ------- | -------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `cursor` | string | No | Opaque pagination cursor from a previous response `meta.next_cursor`. | | `size` | integer | No | Number of accounts to return (1–100). Default: `20`. | | `group_id` | string | No | Filter to accounts that are members of this group id. | | `type` | string | No | Filter by account type: `eoa`, `multisig`, `contract`, `custodian`, `exchange`, `bank`. | | `provider` | string | No | Filter to accounts held under a connection of this provider: `utila`, `kraken`, `plaid`, `squads`, `coinbase`, `realms`, `safe`, `wise`, `hyperliquid`, `cubist`, `anchorage`, `privy`, `dfns`. | | `chain` | string | No | Filter by network/chain identifier. Examples: `ethereum`, `solana`, `stellar`. | | `connection_id` | string | No | Filter to accounts held under this account-connection id. | Get a single account in the caller workspace by its id, including balances, connection details, and group membership. Returns null if no account with that id exists in the workspace. **Workspace-scoped.** | Parameter | Type | Required | Description | | --------- | ------ | -------- | ------------------------------------------- | | `id` | string | Yes | Account id, as returned by `list_accounts`. | Get current balances for every account stored in the caller workspace, grouped by address/network with per-asset amounts and USD values. Use for a quick total-holdings snapshot across the whole workspace. **Workspace-scoped.** No parameters. List all groups defined for the caller workspace, including built-in system groups. Groups are used to tag/organize accounts (e.g. "Finance", "Cold Storage") and can be passed as `group_id` to `list_accounts`. **Workspace-scoped.** No parameters. List account connections (linked custodian/exchange/bank/multisig integrations such as Utila, Kraken, Plaid, Safe, Squads) configured in the caller workspace. Only non-sensitive public metadata is returned — provider credentials and secrets are never exposed. **Workspace-scoped.** | Parameter | Type | Required | Description | | --------- | ------- | -------- | --------------------------------------------------------------------- | | `cursor` | string | No | Opaque pagination cursor from a previous response `meta.next_cursor`. | | `size` | integer | No | Number of connections to return (1–100). Default: `20`. | Get recent transactions merged across every connection-linked account in the caller workspace (e.g. Kraken trades, Utila custody transfers, bank transactions), sorted newest-first. This is a recent-activity overview, not a full paginated history. Connections whose provider doesn't support transactions, or that fail to fetch, are skipped. **Workspace-scoped.** | Parameter | Type | Required | Description | | --------- | --------- | -------- | ------------------------------------------------------------------------------------------------------------------------- | | `size` | integer | No | Maximum transactions to return after merging and sorting newest-first (1–100). Default: `20`. | | `tokens` | string\[] | No | Asset symbols to filter by, e.g. `["USDC", "ETH"]`. Matched case-insensitively against the transaction's displayed asset. | *** ## Workspace Admin & Plans Workspace identity and the global Range plan catalogue. Get the calling workspace's identity: workspace id and name, resolved server-side from the caller's API key. Use when the user asks about their own workspace. Per-workspace plan assignment is not yet accessible via the Range API, so no plan is returned — use `get_workspace_plans` for the global plan catalogue. Returns `found: false` if the workspace has no stored record yet. **Workspace-scoped.** No parameters. Get every Range subscription plan definition, with numeric rank and per-feature limits (max alert rules, trail/investigation tabs, tracked addresses). This is the global plan catalogue, not the caller workspace's current plan assignment. **Not workspace-scoped** — works with any valid API key. No parameters. *** ## Alerts & Rules Alert rules, fired events, templates, and delivery channels configured for your workspace. List the active alert rules configured for the authenticated workspace. An alert rule is a live subscription (created from a template) that fires alert events when its trigger condition is met. Filter by network, severity, or a name search. **Workspace-scoped.** | Parameter | Type | Required | Description | | --------------- | ------- | -------- | --------------------------------------------------------------------- | | `network` | string | No | Comma-separated network slugs to filter by. Examples: `eth,sol`. | | `severity` | string | No | Comma-separated severities to filter by. Examples: `low,medium,high`. | | `search_string` | string | No | Case-insensitive substring search against the rule name. | | `limit` | integer | No | Maximum rules to return (1–100). Default: `20`. | Get a single alert rule by id, including its parameters, trigger, version, subscribed channels, and the template it was created from. **Workspace-scoped.** | Parameter | Type | Required | Description | | --------- | ------ | -------- | ------------------ | | `rule_id` | string | Yes | The alert rule id. | List alert events (fired instances of alert rules) for the authenticated workspace, newest first. Filter by network, severity, exact transaction hash, a UTC date range, or a full-text search across the event caption and involved addresses. Cursor-paginated. **Workspace-scoped.** | Parameter | Type | Required | Description | | --------------- | ------- | -------- | ------------------------------------------------------------------------------------------------------------- | | `network` | string | No | Filter by network slug. Example: `ethereum`. | | `severity` | string | No | Comma-separated severities to filter by. Examples: `low,medium,high`. | | `tx_hash` | string | No | Filter by exact transaction hash. | | `start_date` | string | No | Start of date range, inclusive, UTC, `YYYY-MM-DD`. Example: `2026-05-01`. | | `end_date` | string | No | End of date range, inclusive, UTC, `YYYY-MM-DD`. Example: `2026-05-31`. | | `search_string` | string | No | Case-insensitive search across the event caption and involved addresses. | | `cursor` | string | No | Opaque pagination cursor from a previous response (`next_cursor`/`previous_cursor`). Omit for the first page. | | `limit` | integer | No | Maximum events to return in this page (1–100). Default: `20`. | Get a single alert event by id. Returns the fired event with its timestamp, severity, caption, involved addresses, structured details, and `access_type` (the caller workspace's relationship to the event). **Workspace-scoped.** | Parameter | Type | Required | Description | | ---------- | ------ | -------- | ------------------------------------ | | `event_id` | string | Yes | CUID of the alert event to retrieve. | List the alert rule templates available to the authenticated workspace, grouped by rule type with the networks each covers. A template is the blueprint an alert rule is created from. Filter by network, severity, tags, or a name/description search. **Workspace-scoped.** | Parameter | Type | Required | Description | | --------------- | ------- | -------- | --------------------------------------------------------------------------- | | `network` | string | No | Comma-separated network slugs to filter by. Examples: `eth,sol`. | | `severity` | string | No | Comma-separated severities to filter by. Examples: `low,medium,high`. | | `tag` | string | No | Comma-separated tags to filter by. Examples: `defi,transfer`. | | `search_string` | string | No | Case-insensitive search matched against the template label and description. | | `limit` | integer | No | Maximum template groups to return (1–100). Default: `20`. | Get a single alert rule template by id. Returns its message, severity, tags, trigger cadence, and the parameters required to turn it into an active alert rule. **Workspace-scoped.** | Parameter | Type | Required | Description | | ------------- | ------ | -------- | ---------------------------------------------------------- | | `template_id` | string | Yes | The alert rule template id (per-network template pointer). | List the alert delivery channels (Slack, Discord, PagerDuty, email, webhook, Telegram, incident.io, etc.) configured for the authenticated workspace, including disabled ones. Sensitive delivery params (email addresses, tokens) are redacted. **Workspace-scoped.** | Parameter | Type | Required | Description | | --------- | ------- | -------- | -------------------------------------------------- | | `limit` | integer | No | Maximum channels to return (1–100). Default: `20`. | Get a single alert delivery channel by id, including its type, enabled/connected status, and type-specific delivery params. Sensitive params are redacted — this never returns raw delivery secrets. **Workspace-scoped.** | Parameter | Type | Required | Description | | ------------ | ------ | -------- | --------------------- | | `channel_id` | string | Yes | The alert channel id. | *** ## Counterparties & Enrichment Vendors, customers, investors, and partners recorded in your workspace, plus the notes and categories attached to transfers. List counterparties (vendors, customers, investors, partners, exchanges, etc.) recorded for the workspace, with optional type/name filtering. Use this to find a counterparty before looking up its details, addresses, or bank accounts. **Workspace-scoped.** | Parameter | Type | Required | Description | | --------- | ------- | -------- | ---------------------------------------------------------------------------------------------- | | `type` | string | No | Filter by relationship type: `vendor`, `customer`, `investor`, `partner`, `exchange`, `other`. | | `search` | string | No | Case-insensitive substring search on counterparty name. | | `limit` | integer | No | Number of counterparties to return (1–100). Default: `20`. | | `cursor` | string | No | Pagination cursor from a previous response. | Get full details for a single counterparty by id: name, type, website, notes, linked addresses, bank accounts, and document metadata. Use `list_counterparties` first to find the id. **Workspace-scoped.** | Parameter | Type | Required | Description | | --------- | ------ | -------- | -------------------------------------------- | | `id` | string | Yes | Counterparty id, from `list_counterparties`. | Look up the workspace note and category recorded against a transfer, identified by its on-chain transaction hash and network. Returns an empty result if the transfer has not been enriched or cannot be found. **Workspace-scoped.** | Parameter | Type | Required | Description | | --------- | ------ | -------- | -------------------------------------------------------------------------------------------------- | | `tx_hash` | string | Yes | On-chain transaction hash. | | `network` | string | Yes | Blockchain network the transaction hash belongs to. Examples: `ethereum`, `solana`, `cosmoshub-4`. | List free-text notes the workspace has attached to transfers. Omit `transfer_id` to list all notes for the workspace, or pass it to fetch a single transfer's note. **Workspace-scoped.** | Parameter | Type | Required | Description | | ------------- | ------- | -------- | ---------------------------------------------------------------------------------------------------- | | `transfer_id` | string | No | If provided, return only the note for this transfer id. Otherwise, list all notes for the workspace. | | `limit` | integer | No | Maximum notes to return (1–100). Default: `20`. | List the accounting/spend categories the workspace has assigned to transfers (e.g. Payroll, Revenue, Gas Fees). Optionally filter to a single transfer or a set of category names. Use `get_risk_categories`/`list_risk_signals` for risk taxonomy instead — this is transfer bookkeeping, not risk. **Workspace-scoped.** | Parameter | Type | Required | Description | | ------------- | --------- | -------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `transfer_id` | string | No | If provided, return only the category assigned to this transfer id. | | `categories` | string\[] | No | Filter results to these category names: `Transfer`, `Revenue`, `Payroll`, `Contract Services`, `Software & Subscriptions`, `Legal & Professional Services`, `Taxes`, `Bank Fees`, `Payment Processing Fees`, `Interest Earned`, and other workspace-defined categories. | | `limit` | integer | No | Maximum categories to return (1–100). Default: `20`. | *** ## Screening & Risk The v2 screening pipeline (workspace-configurable attribution/exposure/behaviour signals) and the v1 graph-based risk tools (fixed scoring, no workspace configuration). Use `screen_address` when the workspace has customized its risk signals; use `get_address_risk` for the fixed graph-based score. Run the v2 screening pipeline against a single blockchain address: workspace-configurable attribution, exposure, and behaviour signals, reduced to an overall severity (`none`/`low`/`medium`/`high`/`severe`). Evidence is omitted by default; pass `include_evidence=true` for it inline, or fetch it later with `get_screening_evidence` using the returned `screen_id`. **Workspace-scoped.** | Parameter | Type | Required | Description | | ------------------ | ------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `address` | string | Yes | Blockchain address to screen. Accepts EVM (`0x...`), Solana (base58), Stellar (`G.../M...`), Cosmos bech32, and Tron formats. Network is derived automatically from the address format. | | `window` | string | No | Time window for analysis: `30d`, `90d`, `180d`, `365d`, or `all`. Accepted for parity with the REST endpoint; not yet wired into the scoring pipeline (all available history is currently considered regardless of this value). | | `include_evidence` | boolean | No | If true, include the full per-signal evidence breakdown inline. Solana addresses always include evidence regardless of this flag. Default: `false`. | Run the v2 screening pipeline (see `screen_address`) against up to 50 addresses in one call. Network is derived per-address from its format. Per-address failures do not fail the whole batch — check the response `meta` (total/scored/errors) for partial-failure counts. **Workspace-scoped.** | Parameter | Type | Required | Description | | ------------------ | --------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `addresses` | string\[] | Yes | Addresses to screen (1–50). Mixed networks are fine — network is derived per-address. | | `include_evidence` | boolean | No | If true, include the full per-signal evidence breakdown inline for each result. Solana addresses always include evidence regardless of this flag. Default: `false`. | List past v2 screening results (`screen_address` / `screen_addresses_batch` calls) for the calling workspace, most recent first. Use this to re-find a `screen_id` without re-running a screen. **Workspace-scoped.** | Parameter | Type | Required | Description | | --------- | ------- | -------- | -------------------------------------------------------- | | `offset` | integer | No | Number of records to skip, for pagination. Default: `0`. | | `limit` | integer | No | Page size (1–100). Default: `20`. | Get the full evidence breakdown for a previously issued `screen_id` (from `screen_address`, `screen_addresses_batch`, or `get_screening_history`), grouped by pillar (attribution, exposure, behaviour) and signal, alongside the original risk assessment. **Workspace-scoped** — the `screen_id` must belong to the calling workspace. | Parameter | Type | Required | Description | | ----------- | ------ | -------- | ----------------------------------------------------------------------------------------------- | | `screen_id` | string | Yes | `screen_id` returned by `screen_address`, `screen_addresses_batch`, or `get_screening_history`. | Get the calling workspace's active v2 risk configuration: which attribution signals, exposure signals, and behaviours are enabled and at what severity/thresholds. A workspace with no stored config gets a seeded default on first read. Use `list_risk_signals` to see the full catalogue available to configure. **Workspace-scoped.** No parameters. List the global catalogue of attribution signals, exposure signals, and behaviours available across all workspaces for the v2 screening pipeline. This is read-only reference metadata — it is not auto-applied to any workspace; see `get_screening_config` for what a specific workspace actually has enabled. **Not workspace-scoped** — works with any valid API key. No parameters. Get the calling workspace's v1 risk category settings (legacy category taxonomy used for address/entity labelling, e.g. sanctions, mixer, scam). This is a separate, older configuration surface from the v2 signals/behaviours exposed via `get_screening_config`/`list_risk_signals`. **Workspace-scoped.** No parameters. Get the calling workspace's v1 behavior pattern settings (legacy behaviour taxonomy, e.g. smurfing, structuring). This is a separate, older configuration surface from the v2 behaviours exposed via `get_screening_config`/`list_risk_signals`. **Workspace-scoped.** No parameters. Get the v1 risk score for a blockchain address. Returns a risk level (VERY\_LOW to CRITICAL), numeric score, reasoning, malicious addresses found in the transaction graph, and entity attribution. Often the first call in an investigation. | Parameter | Type | Required | Description | | --------- | ------ | -------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `address` | string | Yes | Blockchain address. EVM: `0x...` (42 chars). Solana: base58 (32–44 chars). Stellar: `G...` or `M...` (56 chars). Cosmos: network-prefixed bech32. | | `network` | string | No | Network ID. Examples: `eth`, `solana`, `stellar`, `cosmoshub-4`, `osmosis-1`, `dydx-mainnet-1`, `neutron-1`, `tron`. Auto-detected for EVM/Solana/Stellar if omitted. | Get the risk score for a transaction by hash. Evaluates all addresses involved and returns the highest risk score found with per-address risk details. | Parameter | Type | Required | Description | | ------------- | ------ | -------- | ----------------------------------------------------------------------------------------------------------- | | `transaction` | string | Yes | Transaction hash to assess. | | `network` | string | No | Network of the transaction. Examples: `solana`, `ethereum`, `cosmoshub-4`. Defaults to `solana` if omitted. | Assess the risk of a proposed cross-chain payment between two addresses. Analyzes sender/recipient risk, interaction history, address poisoning, malicious connections, and behavioral indicators. Returns `overall_risk_level` (LOW/MEDIUM/HIGH/UNKNOWN) with detailed risk factors. | Parameter | Type | Required | Description | | ------------------- | ------ | -------- | ----------------------------------------------------------------------------------------------------- | | `sender_address` | string | Yes | Sender blockchain address. | | `recipient_address` | string | Yes | Recipient blockchain address. | | `amount` | number | Yes | Payment amount in USD equivalent (must be > 0). | | `sender_network` | string | Yes | Sender network. Examples: `solana`, `ethereum`, `osmosis-1`. | | `recipient_network` | string | Yes | Recipient network. | | `sender_token` | string | No | Token/denom being sent (enables token risk). Example: `EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v`. | | `recipient_token` | string | No | Token/denom being received. | | `timestamp` | string | No | Payment timestamp (ISO 8601). Example: `2025-01-15T10:30:00Z`. | Get the risk score for a token/asset by its contract/mint address. Returns risk level, score, and reasoning for whether a token is associated with scams, rug pulls, or malicious activity. Currently supports Solana tokens. | Parameter | Type | Required | Description | | --------------- | ------ | -------- | --------------------------------------------------------------------------------------------------------- | | `asset_address` | string | Yes | Token contract or mint address. Example: `EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v` (USDC on Solana). | | `network` | string | No | Blockchain network. Currently only `solana` is supported. Default: `solana`. | Check if a blockchain address is OFAC sanctioned or blacklisted by token issuers (Tether USDT, Circle USDC, Coinbase, Paxos). Returns `is_ofac_sanctioned` and `is_token_blacklisted` flags with detailed event history. Supports Ethereum, Tron, and Solana. | Parameter | Type | Required | Description | | ----------------- | ------- | -------- | ---------------------------------------------------------------------------------------------- | | `address` | string | Yes | Blockchain address. Supports EVM (`0x...`), Solana (base58), and Tron (`T...`) formats. | | `network` | string | No | Filter by network: `ethereum`, `tron`, or `solana`. If omitted, checks all supported networks. | | `include_details` | boolean | No | Include full blacklist event history and attribution. Default: `true`. | *** ## Address Intelligence Labels, connections, transaction history, balances, and behavioral stats for any blockchain address. Get information about a blockchain address including labels, entity name, category, and tags. Identifies whether an address belongs to a known exchange, mixer, protocol, or other entity. | Parameter | Type | Required | Description | | --------- | ------ | -------- | ----------------------------------------------------------------------------- | | `address` | string | Yes | Blockchain address. | | `network` | string | Yes | Network ID. Examples: `eth`, `solana`, `stellar`, `cosmoshub-4`, `osmosis-1`. | Get counterparty addresses that a given address has interacted with. Essential for tracing money flows and building a transaction graph. Returns connected addresses with labels and transfer statistics. | Parameter | Type | Required | Description | | ------------ | ------- | -------- | ------------------------------------------------------------------------------ | | `address` | string | Yes | Blockchain address to find counterparties for. | | `network` | string | Yes | Network ID. | | `size` | integer | No | Number of counterparty addresses to return (1–100). Default: `10`. | | `start_time` | string | No | Filter connections from this time (ISO 8601). Example: `2024-01-01T00:00:00Z`. | | `end_time` | string | No | Filter connections until this time (ISO 8601). | Get transaction history for a blockchain address with optional filters by time range and status. Returns a paginated list of transactions with amounts, counterparties, and timestamps. | Parameter | Type | Required | Description | | ----------- | ------- | -------- | -------------------------------------------------------- | | `address` | string | Yes | Blockchain address. | | `network` | string | Yes | Network ID. | | `limit` | integer | No | Number of transactions to return (1–500). Default: `50`. | | `offset` | integer | No | Transactions to skip for pagination. Default: `0`. | | `startTime` | string | No | Filter from this time (ISO 8601). | | `endTime` | string | No | Filter until this time (ISO 8601). | | `status` | string | No | Filter by transaction status: `success` or `failed`. | | `msgTypes` | string | No | Filter by message types (comma-separated). | Get detailed statistical features for a blockchain address: transaction counts, volumes, token interactions, active duration, unique counterparties, and daily activity patterns. Use for behavioral analysis. | Parameter | Type | Required | Description | | --------- | ------ | -------- | ------------------- | | `address` | string | Yes | Blockchain address. | | `network` | string | Yes | Network ID. | Find the source of funds for a blockchain address — which address initially funded it, when, and with what amount. Critical for tracing the origin of funds in an investigation. | Parameter | Type | Required | Description | | --------- | ------ | -------- | -------------------------------------------------- | | `address` | string | Yes | Blockchain address to find the funding source for. | | `network` | string | Yes | Network ID. | Get current token balances for a blockchain address across all tokens it holds. | Parameter | Type | Required | Description | | ----------------- | ------ | -------- | --------------------------------------------------------------- | | `address` | string | Yes | Blockchain address. | | `network` | string | Yes | Network ID. | | `network_type` | string | No | Network architecture type. Examples: `evm`, `solana`, `cosmos`. | | `token_contracts` | string | No | Comma-separated token contract addresses to filter balances. | Get aggregate statistics for a blockchain address: total transaction count, total volume, unique counterparties, active days, and more. Useful for quickly profiling how active an address is. | Parameter | Type | Required | Description | | --------- | ------ | -------- | ---------------------------------------------------------- | | `address` | string | Yes | Blockchain address. | | `network` | string | Yes | Network ID. Examples: `ethereum`, `solana`, `cosmoshub-4`. | Get the payment history for a blockchain address. Payments are cross-chain and intrachain value transfers. Supports filtering by direction (incoming/outgoing), time range, counterparty address, and message type. | Parameter | Type | Required | Description | | ------------------ | ------- | -------- | -------------------------------------------------------------------------------- | | `address` | string | Yes | Blockchain address. | | `network` | string | No | Network ID. Examples: `ethereum`, `solana`, `cosmoshub-4`. | | `limit` | integer | No | Number of payments to return (1–500). Default: `50`. | | `offset` | integer | No | Payments to skip for pagination. Default: `0`. | | `direction` | string | No | Filter by payment direction: `incoming`, `outgoing`, or `both`. Default: `both`. | | `start_time` | string | No | Filter from this time (ISO 8601). Example: `2024-01-01T00:00:00Z`. | | `end_time` | string | No | Filter until this time (ISO 8601). | | `receiver` | string | No | Filter payments involving this counterparty address. | | `receiver_network` | string | No | Network of the counterparty address. | Get full details of a specific payment by its transaction hash. Returns sender, receiver, amounts, token details, and timestamps for a single payment event. | Parameter | Type | Required | Description | | --------- | ------ | -------- | --------------------------------------- | | `hash` | string | Yes | Payment or transaction hash to look up. | Get asset flow summary for a blockchain address showing net inflows and outflows per token. Useful for understanding which tokens an address has been accumulating or distributing over time. | Parameter | Type | Required | Description | | -------------- | ------ | -------- | --------------------------------------------------------------- | | `address` | string | Yes | Blockchain address. | | `network` | string | Yes | Network ID. Examples: `ethereum`, `solana`, `cosmoshub-4`. | | `network_type` | string | No | Network architecture type. Examples: `evm`, `solana`, `cosmos`. | Search for known blockchain entities and addresses by name or label. Find exchanges (Binance, Coinbase), mixers (Tornado Cash), protocols (Uniswap), and other labeled addresses. | Parameter | Type | Required | Description | | ------------- | ------ | -------- | ------------------------------------------------------------------------------------------ | | `search_term` | string | Yes | Name or partial name to search for. Examples: `"Binance"`, `"Coinbase"`, `"Tornado Cash"`. | | `networks` | string | No | Comma-separated blockchain networks to filter by. Examples: `ethereum,solana`. | *** ## Transfers & Transaction Detail Token transfer history and full transaction detail lookups. Get token transfer history for a blockchain address with rich filtering options. Returns transfers with sender, receiver, token symbol, USD amount, timestamp, and bridge type. Supports cross-chain and intrachain transfers. **Workspace-scoped when `only_workspace` is set to true** — otherwise usable with any valid API key. | Parameter | Type | Required | Description | | ---------------------- | ------- | -------- | ----------------------------------------------------------------------------------------------------------------------------- | | `address` | string | Yes | Blockchain address to get token transfers for. | | `network` | string | No | Filter by network. Examples: `solana`, `ethereum`, `cosmoshub-4`. | | `size` | integer | No | Number of transfers to return (1–10000). Default: `25`. | | `cursor` | string | No | Pagination cursor from previous response. | | `token_symbols` | string | No | Comma-separated token symbols. Examples: `USDC,DAI,SOL`. | | `status` | string | No | Comma-separated statuses: `SUCCEEDED`, `PENDING`, `ERROR_ON_DESTINATION`, `TIMEOUT`. | | `min_usd` | number | No | Minimum USD amount filter. | | `max_usd` | number | No | Maximum USD amount filter. | | `start_time` | string | No | Filter from this time (ISO 8601). Example: `2024-01-01T00:00:00Z`. | | `end_time` | string | No | Filter until this time (ISO 8601). | | `source_networks` | string | No | Comma-separated source networks. | | `destination_networks` | string | No | Comma-separated destination networks. | | `bridges` | string | No | Comma-separated bridge types. Examples: `ibc,cctp`. | | `only_workspace` | boolean | No | If true, only return transfers the authenticated workspace has labelled with a category. Requires a workspace-scoped API key. | Get all transfers directly between two specific blockchain addresses, even across different networks. Useful for investigating direct relationships and money flows between two wallets. | Parameter | Type | Required | Description | | ------------ | ------- | -------- | ------------------------------------------------------------------ | | `address_a` | string | Yes | First blockchain address. | | `network_a` | string | Yes | Network of address A. Examples: `solana`, `ethereum`, `osmosis-1`. | | `address_b` | string | Yes | Second blockchain address. | | `network_b` | string | Yes | Network of address B. | | `size` | integer | No | Number of transfers to return (1–100). Default: `10`. | | `start_time` | string | No | Filter from this time (ISO 8601). | | `end_time` | string | No | Filter until this time (ISO 8601). | | `types` | string | No | Transfer types (comma-separated). Examples: `ibc,cctp`. | | `cursor` | string | No | Pagination cursor. | Get full details of a blockchain transaction by network and hash. Returns sender, receiver, amounts, token transfers, fees, and timestamp. Use this to understand exactly what happened in a specific transaction. | Parameter | Type | Required | Description | | --------- | ------ | -------- | ------------------------------------------------------------------------------------------------------------------------- | | `network` | string | Yes | Blockchain network. Examples: `ethereum`, `solana`, `cosmoshub-4`, `osmosis-1`, `dydx-mainnet-1`, `neutron-1`, `stellar`. | | `hash` | string | Yes | Transaction hash to look up. | *** ## Network & Token Stats Aggregate network activity — whale moves, volume, active accounts, message-type breakdowns — and token supply/holder data. Get large-value transactions ("whale moves") on a blockchain network within a time range. Returns the biggest transfers sorted by USD value. Useful for identifying market-moving activity, suspicious large flows, or tracking major players. | Parameter | Type | Required | Description | | ------------ | ------- | -------- | ------------------------------------------------------------------------------- | | `network` | string | Yes | Blockchain network. Examples: `ethereum`, `solana`, `cosmoshub-4`, `osmosis-1`. | | `start_time` | string | Yes | Start of time range (ISO 8601). Example: `2024-01-01T00:00:00Z`. | | `end_time` | string | Yes | End of time range (ISO 8601). Example: `2024-01-07T23:59:59Z`. | | `limit` | integer | No | Number of whale moves to return (1–100). Default: `10`. | | `symbol` | string | No | Filter by token symbol. Examples: `USDC`, `ETH`, `SOL`. | Get total transaction volume for a blockchain network within a specific time range in USD. Useful for understanding overall network activity levels during an investigation time window. | Parameter | Type | Required | Description | | ------------ | ------ | -------- | ------------------------------------------------------------------ | | `network` | string | Yes | Blockchain network. Examples: `ethereum`, `solana`, `cosmoshub-4`. | | `start_time` | string | Yes | Start of time range (ISO 8601). | | `end_time` | string | Yes | End of time range (ISO 8601). | Get transaction counts for one or more blockchain networks, bucketed over time. Returns per-network time-series points (count, failed count) plus a running total. Useful for spotting activity spikes or comparing throughput across networks. | Parameter | Type | Required | Description | | ------------------ | ------- | -------- | -------------------------------------------------------------------------------- | | `networks` | string | Yes | Comma-separated list of networks. Examples: `ethereum,solana,cosmoshub-4`. | | `interval_seconds` | integer | Yes | Size of each time bucket, in seconds. Example: `3600`. | | `buckets` | integer | No | Number of time buckets to return, counting back from now (1–100). Default: `24`. | Get the count of distinct active accounts on a blockchain network within a time range. Useful for gauging user/address engagement on a network over a given window. | Parameter | Type | Required | Description | | ------------ | ------ | -------- | ------------------------------------------------------------------ | | `network` | string | Yes | Blockchain network. Examples: `ethereum`, `solana`, `cosmoshub-4`. | | `start_time` | string | Yes | Start of time range (ISO 8601). | | `end_time` | string | Yes | End of time range (ISO 8601). | Get the top sending and top receiving addresses on a network, ranked by an aggregated numeric field (e.g. transfer amount) within a time range. Returns two ranked lists: `topSenders` and `topReceivers`. | Parameter | Type | Required | Description | | ------------ | ------- | -------- | ------------------------------------------------------------------ | | `network` | string | Yes | Blockchain network. Examples: `ethereum`, `solana`, `cosmoshub-4`. | | `start_time` | string | Yes | Start of time range (ISO 8601). | | `end_time` | string | Yes | End of time range (ISO 8601). | | `limit` | integer | No | Number of addresses to return per list (1–100). Default: `20`. | | `field` | string | Yes | Numeric field to aggregate and sort by. Example: `amount`. | | `symbol` | string | No | Filter by token symbol. Examples: `USDC`, `ETH`, `SOL`. | Get the addresses holding the largest USD-denominated balances on a network, as of the latest snapshot. Useful for identifying whales or high-value holders on a chain. | Parameter | Type | Required | Description | | --------- | ------- | -------- | ------------------------------------------------------------------ | | `network` | string | Yes | Blockchain network. Examples: `ethereum`, `solana`, `cosmoshub-4`. | | `limit` | integer | No | Number of addresses to return (1–100). Default: `20`. | Get the distribution of message/transaction types seen on a network (e.g. Cosmos SDK Msg types), with counts. Useful for understanding what kinds of activity dominate a chain. | Parameter | Type | Required | Description | | --------- | ------ | -------- | --------------------------------------------------------- | | `network` | string | Yes | Blockchain network. Examples: `cosmoshub-4`, `osmosis-1`. | Search for a transaction by its hash across supported networks without knowing which network it belongs to. Returns matching hash/height/network/time records — use `get_transaction_details` afterwards for full transaction data once the network is known. | Parameter | Type | Required | Description | | --------- | ------ | -------- | ------------------------------- | | `hash` | string | Yes | Transaction hash to search for. | Get the latest indexed summary for a token (supply, holder count, etc.) on a given network. Returns `{ found: false }` if no summary has been indexed yet for the token/network pair. | Parameter | Type | Required | Description | | --------- | ------ | -------- | --------------------------------------------- | | `token` | string | Yes | Token symbol or identifier. Example: `USDtb`. | | `network` | string | Yes | Blockchain network. Example: `eth`, `solana`. | Get the on-chain total supply of a token, read live from the network. Supports Solana (SPL mint address) and EVM-compatible networks (ERC-20 contract address). Only a small set of tokens are currently mapped. | Parameter | Type | Required | Description | | --------- | ------ | -------- | ---------------------------------------------- | | `network` | string | Yes | Blockchain network. Examples: `eth`, `solana`. | | `token` | string | Yes | Token symbol. Example: `USDtb`. | Get mint and burn events for a token. For EVM networks these are Transfer events to/from the zero address; for Solana these are mintTo/burn SPL-token instructions. Useful for tracking supply inflation/deflation over time. | Parameter | Type | Required | Description | | --------- | ------- | -------- | ------------------------------------------------------------- | | `network` | string | Yes | Blockchain network. Examples: `eth`, `solana`. | | `token` | string | Yes | Token symbol. Example: `USDtb`. | | `limit` | integer | No | Maximum events to return (1–100). Default: `20`. | | `cursor` | string | No | Pagination cursor (`next_cursor` value from a previous page). | Get the top holders of a token, ranked by balance, from the latest indexed snapshot. Useful for concentration analysis (e.g. how much of supply is held by the top N wallets). | Parameter | Type | Required | Description | | --------- | ------- | -------- | --------------------------------------------------------------------------------------------------------------- | | `token` | string | Yes | Token symbol or identifier. Example: `USDtb`. | | `network` | string | Yes | Blockchain network. Example: `eth`. | | `size` | integer | No | Number of holders to return (1–100). Default: `20`. | | `cursor` | string | No | Pagination cursor. Use `"A"` for the first page, `"Z"` for the last page, or a cursor from a previous response. | *** ## Explorer Stats & Utilities Explorer-level leaderboards, cross-chain flow, transaction search, plain-language transaction explanation, and the entity directory. Get the top addresses on an explorer/network by transaction volume and by transaction count over a given duration. Returns two ranked lists (`topAddressesByVolume`, `topAddressesByTransactions`). | Parameter | Type | Required | Description | | ---------- | ------ | -------- | ----------------------------------------------------------------- | | `duration` | string | Yes | Lookback window. Examples: `1h`, `24h`, `7d`. | | `explorer` | string | No | Explorer/network key to scope results to. Example: `solana`. | | `assets` | string | No | Comma-separated asset symbols to filter by. Example: `USDC,USDT`. | Get the top protocols on an explorer/network by transaction volume and by transaction count over a given duration. Returns two ranked lists (`topProtocolsByVolume`, `topProtocolsByTransactions`). | Parameter | Type | Required | Description | | ---------- | ------ | -------- | ----------------------------------------------------------------- | | `duration` | string | Yes | Lookback window. Examples: `1h`, `24h`, `7d`. | | `explorer` | string | No | Explorer/network key to scope results to. Example: `solana`. | | `assets` | string | No | Comma-separated asset symbols to filter by. Example: `USDC,USDT`. | Get the top assets on an explorer/network ranked by transaction volume over a given duration. Useful for seeing which tokens are moving the most value right now. | Parameter | Type | Required | Description | | ---------- | ------ | -------- | ------------------------------------------------------------ | | `duration` | string | Yes | Lookback window. Examples: `1h`, `24h`, `7d`. | | `explorer` | string | No | Explorer/network key to scope results to. Example: `solana`. | Get cross-network transfer flow over a given duration: which network pairs are sending value to each other, broken down by transfer type. Useful for visualizing or reasoning about interchain money movement. | Parameter | Type | Required | Description | | ----------- | ------ | -------- | ------------------------------------------------------------------- | | `duration` | string | Yes | Lookback window. Examples: `1h`, `24h`, `7d`. | | `explorer` | string | No | Explorer/network key to scope results to. Example: `solana`. | | `protocols` | string | No | Comma-separated protocol names to filter by. Example: `cctp,union`. | | `assets` | string | No | Comma-separated asset symbols to filter by. Example: `USDC,USDT`. | Get cross-chain (interchain) transfer volume over time, grouped by a field (e.g. token) and bucketed into an interval. Returns periodic series per group plus totals, with smaller groups rolled into an "Others" bucket. | Parameter | Type | Required | Description | | ---------- | ------ | -------- | ----------------------------------------------------------------- | | `duration` | string | Yes | Lookback window. Examples: `1h`, `24h`, `7d`. | | `explorer` | string | No | Explorer/network key to scope results to. Example: `solana`. | | `assets` | string | No | Comma-separated asset symbols to filter by. Example: `USDC,USDT`. | | `group_by` | string | No | Field to group series by. Example: `token`. | | `type` | string | No | Aggregation type: `tx` for transaction counts, otherwise USD sum. | | `interval` | string | No | Calendar interval for the time series. Example: `1d`. | List all stablecoin token symbols tracked in the stablecoin transfers index. Useful as a reference lookup before filtering other tools (e.g. `get_top_assets`, `get_transfers`) to stablecoin activity only. No parameters. Get aggregate statistics for a named protocol (interchain payments type) within a time range: total transaction count, total USD volume, and a per-denom breakdown. | Parameter | Type | Required | Description | | ----------------- | ------ | -------- | ---------------------------------------------------------------- | | `protocol` | string | Yes | Protocol name to filter by. Example: `interchain_payments`. | | `begin_timestamp` | string | Yes | Start of time range (ISO 8601). Example: `2024-04-09T00:00:00Z`. | | `end_timestamp` | string | Yes | End of time range (ISO 8601). Example: `2024-04-10T00:00:00Z`. | Search/list transactions on a single network with optional filters (address, tx hash, message types, status, time range). Returns a cursor-paginated page of transactions. Use `get_transaction_details` instead if you already know the exact network+hash. | Parameter | Type | Required | Description | | ------------ | ------- | -------- | --------------------------------------------------------------- | | `network` | string | Yes | Blockchain network to search. Example: `cosmoshub-4`. | | `cursor` | string | No | Pagination cursor from a previous response. | | `types` | string | No | Filter by message/transaction type. Example: `ExecuteContract`. | | `size` | integer | No | Number of transactions to return (1–100). Default: `20`. | | `tx_hash` | string | No | Filter by an exact transaction hash. | | `address` | string | No | Filter to transactions involving this address. | | `status` | string | No | Filter by transaction status: `SUCCEEDED` or `ERROR`. | | `start_time` | string | No | Filter from this time (ISO 8601). | | `end_time` | string | No | Filter until this time (ISO 8601). | Explain a blockchain transaction in plain language. Given just a network and transaction hash, returns a human-readable narrative of what happened — the primary action (e.g. swap, transfer, stake, contract call), who the parties are, and any token or native-asset movements with resolved amounts and USD value. Supports Solana and EVM (Ethereum-family) networks. Use this when you need to describe a transaction to a person or triage an unfamiliar transaction quickly. | Parameter | Type | Required | Description | | --------- | ------ | -------- | --------------------------------------------------- | | `hash` | string | Yes | Transaction hash to explain. | | `network` | string | Yes | Blockchain network. Examples: `solana`, `ethereum`. | Get a single transfer by its opaque transfer id (as returned in transfer lists, e.g. from `get_transfers`). Returns full transfer detail including sender/receiver, token, USD amount, and bridge type. | Parameter | Type | Required | Description | | --------- | ------ | -------- | ------------------------------------------------- | | `id` | string | Yes | Transfer id, as returned by other transfer tools. | Get the busiest networks for transfers over the last 7 days, split into `sender_networks` and `receiver_networks` with counts. Useful for understanding which chains dominate transfer volume right now. | Parameter | Type | Required | Description | | ---------- | ------ | -------- | ------------------------------------------------------------ | | `explorer` | string | No | Explorer/network key to scope results to. Example: `solana`. | Get the most-transferred assets over the last 7 days, with counts. Useful for understanding which tokens dominate transfer activity right now. | Parameter | Type | Required | Description | | ---------- | ------ | -------- | ------------------------------------------------------------ | | `explorer` | string | No | Explorer/network key to scope results to. Example: `solana`. | Browse the curated entity directory: named organizations, protocols, exchanges, DAOs, bridges, and similar entities, each with tags, verification status, TVL, and monthly volume, sorted by monthly volume. Cursor-paginated, optionally filtered by network. Different from `search_entities`, which does free-text lookup over individually labeled addresses — this browses the entity-level registry itself. | Parameter | Type | Required | Description | | ---------- | ------- | -------- | ------------------------------------------------------------------ | | `cursor` | string | No | Pagination cursor from a previous response. | | `size` | integer | No | Number of entities to return (1–100). Default: `20`. | | `networks` | string | No | Comma-separated networks to filter by. Example: `ethereum,solana`. | Get an enriched block for a network at a given height (for Solana, the slot number). Returns the decoded block payload. Useful for inspecting everything that happened in a specific block. | Parameter | Type | Required | Description | | --------- | ------- | -------- | ------------------------------------------------------------------ | | `network` | string | Yes | Blockchain network. Examples: `ethereum`, `cosmoshub-4`, `solana`. | | `height` | integer | Yes | Block height (or Solana slot number). |