Scorechain

Look up who/what an address is: its label/name, entity type, any custom scores, associated wallet, lists, and linked cases. Use this for identity and attribution; use score_address when you need the AML risk score and fund-flow analysis. [API: GET /blockchains/{blockchain}/addresses/{address}]

get_address

See what an address holds: every asset (native coin and tokens) it owns now or owned before, with current balance, lifetime received, lifetime sent, and transaction count per asset. Amounts come in both the asset's native unit and USD; the _metadata object totals these across all assets. Use this for holdings and lifetime asset activity — concentration, dormant balances, or an unusual asset mix. [API: GET /blockchains/{blockchain}/addresses/{address}/coins]

get_address_assets

Find where an address's funds originally came from: its first funder, with that funder's entity info when known. Use this for provenance — the 'who funded this wallet?' question. Some minimal-coverage blockchains do not support it. [API: GET /blockchains/{blockchain}/addresses/{address}/funder]

get_address_funder

List an address's transaction history (most recent first), to inspect activity, recency, amounts, and counterparties or check whether it is still active. Paginated with offset/limit (limit max 50); narrow by time with minDate/maxDate (Unix timestamps in seconds). Date filtering may be unavailable for addresses with 10,000+ transactions. [API: GET /blockchains/{blockchain}/addresses/{address}/transactions]

get_address_transactions

Break down who holds an ERC-20 token, grouped by entity name or entity type, with balances, holder counts, and risk scores where available — useful for profiling a token's holder base. [API: GET /blockchains/{blockchain}/assets/{chainId}/holders-aggregated]

get_asset_holders

List the entity types Scorechain recognizes, each with its name and default risk score (remember the inverse scale: lower score = higher risk). Call this to get the exact entity-type names to pass to visualize_fund_flow (filterEntityTypes) or visualize_interactions (an ENTITY_TYPE target), and to read the type field returned in a score_address breakdown. [API: GET /riskSettings/entityTypes]

get_entity_types

Look up the details of a single transaction: confirmations, fees, timestamp/status, the operations it contains, and chain-specific data. This is a raw transaction lookup. To assess risk, score the addresses involved with score_address. [API: GET /blockchains/{blockchain}/transactions/{transactionHash}]

get_transaction

List every blockchain Scorechain supports and its coverage level, so you know the exact blockchain value to pass to the other tools and whether a chain supports full analytics. Call this first whenever the blockchain identifier is uncertain. [API: GET /blockchains]

list_blockchains

Get the AML risk score for a blockchain address — the usual first step for any risk or compliance question. Scores run 1–100 on an INVERSE scale: 1 is the highest risk (CRITICAL), 100 is the lowest (NO_RISK). Pick analysisType by the question: FULL for an overall picture, INCOMING for where funds came from, OUTGOING for where they went, ASSIGNED for the address's own label without tracing. Leave depth unset to trace every reachable hop (the API default is its maximum); set a small depth only for a deliberately shallow view. Leave coin unset for an all-asset score; set MAIN, STABLE, or a token contract address to score one asset. [API: POST /scoringAnalysis]

score_address

Find something by text across addresses, transactions, entities, cases, investigations, labels, and lists — e.g. resolve an entity or label name to its addresses before scoring. q must be 3–255 characters. Without type, returns up to 10 items per category (70 max total); set type to focus one category and unlock offset/limit pagination. [API: GET /search]

search