get_address
ChatGPTOpenAPI operation getBlockchainAddress: GET /blockchains/{blockchain}/addresses/{address}. Retrieves address metadata such as label/name, risk assessment, custom scores, associated wallet, lists, and linked cases. This is a direct address lookup, not a real-time fund-flow score; use score_address for AML scoring analysis. Requires an exact blockchain and address. If the chain is unknown, call list_blockchains first.
get_address
ChatGPTOpenAPI operation getBlockchainAddress: GET /blockchains/{blockchain}/addresses/{address}. Retrieves address metadata such as label/name, risk assessment, custom scores, associated wallet, lists, and linked cases. This is a direct address lookup, not a real-time fund-flow score; use score_address for AML scoring analysis. Requires an exact blockchain and address. If the chain is unknown, call list_blockchains first.
get_address
ChatGPTOpenAPI operation getBlockchainAddress: GET /blockchains/{blockchain}/addresses/{address}. Retrieves address metadata such as label/name, risk assessment, custom scores, associated wallet, lists, and linked cases. This is a direct address lookup, not a real-time fund-flow score; use score_address for AML scoring analysis. Requires an exact blockchain and address. If the chain is unknown, call list_blockchains first.
get_address_assets
ChatGPTOpenAPI operation getBlockchainAddressCoins: GET /blockchains/{blockchain}/addresses/{address}/coins. Returns the list of assets (native coin and tokens) that the address owns currently or has owned at some point. For each asset it returns the current balance, the total amount received, the total amount sent, and the number of transactions involving that asset. Every amount is provided both in the asset's native unit (already converted using the asset's decimals) and in USD terms. The _metadata object reports the same metrics summed across all assets: total balance, total received, total sent (in USD), and total number of transactions. Use this to understand an address's holdings and lifetime asset activity, not the native-coin-only score in get_address.
get_address_assets
ChatGPTOpenAPI operation getBlockchainAddressCoins: GET /blockchains/{blockchain}/addresses/{address}/coins. Returns the list of assets (native coin and tokens) that the address owns currently or has owned at some point. For each asset it returns the current balance, the total amount received, the total amount sent, and the number of transactions involving that asset. Every amount is provided both in the asset's native unit (already converted using the asset's decimals) and in USD terms. The _metadata object reports the same metrics summed across all assets: total balance, total received, total sent (in USD), and total number of transactions. Use this to understand an address's holdings and lifetime asset activity, not the native-coin-only score in get_address.
get_address_assets
ChatGPTOpenAPI operation getBlockchainAddressCoins: GET /blockchains/{blockchain}/addresses/{address}/coins. Returns the list of assets (native coin and tokens) that the address owns currently or has owned at some point. For each asset it returns the current balance, the total amount received, the total amount sent, and the number of transactions involving that asset. Every amount is provided both in the asset's native unit (already converted using the asset's decimals) and in USD terms. The _metadata object reports the same metrics summed across all assets: total balance, total received, total sent (in USD), and total number of transactions. Use this to understand an address's holdings and lifetime asset activity, not the native-coin-only score in get_address.
get_address_funder
ChatGPTOpenAPI operation getBlockchainAddressFunder: GET /blockchains/{blockchain}/addresses/{address}/funder. Identifies the original funder of an address, including funder address and associated entity information when available. Useful for address provenance and forensic investigations. Minimal-coverage blockchains may not support this endpoint.
get_address_funder
ChatGPTOpenAPI operation getBlockchainAddressFunder: GET /blockchains/{blockchain}/addresses/{address}/funder. Identifies the original funder of an address, including funder address and associated entity information when available. Useful for address provenance and forensic investigations. Minimal-coverage blockchains may not support this endpoint.
get_address_funder
ChatGPTOpenAPI operation getBlockchainAddressFunder: GET /blockchains/{blockchain}/addresses/{address}/funder. Identifies the original funder of an address, including funder address and associated entity information when available. Useful for address provenance and forensic investigations. Minimal-coverage blockchains may not support this endpoint.
get_address_transactions
ChatGPTOpenAPI operation getBlockchainAddressTransactions: GET /blockchains/{blockchain}/addresses/{address}/transactions. Returns paginated transaction history for an address. Uses offset/limit pagination with limit max 50. Date filters are minDate and maxDate as UTC Unix timestamps in seconds, not ISO 8601 strings. API filters may only be available for addresses with fewer than 10,000 transactions.
get_address_transactions
ChatGPTOpenAPI operation getBlockchainAddressTransactions: GET /blockchains/{blockchain}/addresses/{address}/transactions. Returns paginated transaction history for an address. Uses offset/limit pagination with limit max 50. Date filters are minDate and maxDate as UTC Unix timestamps in seconds, not ISO 8601 strings. API filters may only be available for addresses with fewer than 10,000 transactions.
get_address_transactions
ChatGPTOpenAPI operation getBlockchainAddressTransactions: GET /blockchains/{blockchain}/addresses/{address}/transactions. Returns paginated transaction history for an address. Uses offset/limit pagination with limit max 50. Date filters are minDate and maxDate as UTC Unix timestamps in seconds, not ISO 8601 strings. API filters may only be available for addresses with fewer than 10,000 transactions.
get_asset_holders
ChatGPTOpenAPI operation getAssetHoldersAggregated: GET /blockchains/{blockchain}/assets/{chainId}/holders-aggregated. Returns aggregated ERC-20 holder data grouped by entity name or entity type, including balances, holder counts, and risk scores where available. Only ETHEREUM and POLYGON are currently supported by the API for this endpoint. groupBy must be name or type in the API; this tool accepts ENTITY_NAME and ENTITY_TYPE aliases and normalizes them.
get_asset_holders
ChatGPTOpenAPI operation getAssetHoldersAggregated: GET /blockchains/{blockchain}/assets/{chainId}/holders-aggregated. Returns aggregated ERC-20 holder data grouped by entity name or entity type, including balances, holder counts, and risk scores where available. Only ETHEREUM and POLYGON are currently supported by the API for this endpoint. groupBy must be name or type in the API; this tool accepts ENTITY_NAME and ENTITY_TYPE aliases and normalizes them.
get_asset_holders
ChatGPTOpenAPI operation getAssetHoldersAggregated: GET /blockchains/{blockchain}/assets/{chainId}/holders-aggregated. Returns aggregated ERC-20 holder data grouped by entity name or entity type, including balances, holder counts, and risk scores where available. Only ETHEREUM and POLYGON are currently supported by the API for this endpoint. groupBy must be name or type in the API; this tool accepts ENTITY_NAME and ENTITY_TYPE aliases and normalizes them.
get_transaction
ChatGPTOpenAPI operation getBlockchainTransaction: GET /blockchains/{blockchain}/transactions/{transactionHash}. Retrieves transaction details such as confirmations, fees, timestamp/status, involved operations, and blockchain-specific data. This is a direct transaction lookup; use score_address only for address scoring and use scoringAnalysis externally for transaction scoring if exposed later.
get_transaction
ChatGPTOpenAPI operation getBlockchainTransaction: GET /blockchains/{blockchain}/transactions/{transactionHash}. Retrieves transaction details such as confirmations, fees, timestamp/status, involved operations, and blockchain-specific data. This is a direct transaction lookup; use score_address only for address scoring and use scoringAnalysis externally for transaction scoring if exposed later.
get_transaction
ChatGPTOpenAPI operation getBlockchainTransaction: GET /blockchains/{blockchain}/transactions/{transactionHash}. Retrieves transaction details such as confirmations, fees, timestamp/status, involved operations, and blockchain-specific data. This is a direct transaction lookup; use score_address only for address scoring and use scoringAnalysis externally for transaction scoring if exposed later.
list_blockchains
ChatGPTOpenAPI operation getBlockchains: GET /blockchains. Returns every blockchain supported by Scorechain and its coverage level. FULL coverage supports all analytics tools; MINIMAL coverage is limited and may not support fund-flow, activity, or scoring-depth analysis. Use this before address, transaction, scoring, Sankey, or graph tools when the blockchain identifier is uncertain.
list_blockchains
ChatGPTOpenAPI operation getBlockchains: GET /blockchains. Returns every blockchain supported by Scorechain and its coverage level. FULL coverage supports all analytics tools; MINIMAL coverage is limited and may not support fund-flow, activity, or scoring-depth analysis. Use this before address, transaction, scoring, Sankey, or graph tools when the blockchain identifier is uncertain.
list_blockchains
ChatGPTOpenAPI operation getBlockchains: GET /blockchains. Returns every blockchain supported by Scorechain and its coverage level. FULL coverage supports all analytics tools; MINIMAL coverage is limited and may not support fund-flow, activity, or scoring-depth analysis. Use this before address, transaction, scoring, Sankey, or graph tools when the blockchain identifier is uncertain.
score_address
ChatGPTPOST /scoringAnalysis with objectType fixed to ADDRESS. Returns AML risk scoring for one blockchain address. Lower scores are riskier: 1 is highest risk and 100 is lowest risk. Use ASSIGNED for the address itself, INCOMING or OUTGOING for one direction, and FULL for both. Use coin=MAIN for native assets, coin=STABLE for stablecoins, coin=ALL for multi-asset, or a token contract address.
score_address
ChatGPTPOST /scoringAnalysis with objectType fixed to ADDRESS. Returns AML risk scoring for one blockchain address. Lower scores are riskier: 1 is highest risk and 100 is lowest risk. Use ASSIGNED for the address itself, INCOMING or OUTGOING for one direction, and FULL for both. Use coin=MAIN for native assets, coin=STABLE for stablecoins, coin=ALL for multi-asset, or a token contract address.
score_address
ChatGPTPOST /scoringAnalysis with objectType fixed to ADDRESS. Returns AML risk scoring for one blockchain address. Lower scores are riskier: 1 is highest risk and 100 is lowest risk. Use ASSIGNED for the address itself, INCOMING or OUTGOING for one direction, and FULL for both. Use coin=MAIN for native assets, coin=STABLE for stablecoins, coin=ALL for multi-asset, or a token contract address.
search
ChatGPTOpenAPI operation search: GET /search. Searches Scorechain blockchain intelligence and workspace data across addresses, transactions, entities, cases, investigations, address labels, and lists. The q query must contain 3 to 255 characters. Without type, the API returns up to 10 items per category, with a maximum of 70 total items. Set type to return one result category and enable offset/limit pagination; offset and limit are invalid unless type is set. Use hasActivity to filter address results to addresses with blockchain activity.
search
ChatGPTOpenAPI operation search: GET /search. Searches Scorechain blockchain intelligence and workspace data across addresses, transactions, entities, cases, investigations, address labels, and lists. The q query must contain 3 to 255 characters. Without type, the API returns up to 10 items per category, with a maximum of 70 total items. Set type to return one result category and enable offset/limit pagination; offset and limit are invalid unless type is set. Use hasActivity to filter address results to addresses with blockchain activity.
search
ChatGPTOpenAPI operation search: GET /search. Searches Scorechain blockchain intelligence and workspace data across addresses, transactions, entities, cases, investigations, address labels, and lists. The q query must contain 3 to 255 characters. Without type, the API returns up to 10 items per category, with a maximum of 70 total items. Set type to return one result category and enable offset/limit pagination; offset and limit are invalid unless type is set. Use hasActivity to filter address results to addresses with blockchain activity.
visualize_fund_flow
ChatGPTPOST /sankey for ADDRESS fund-flow visualizations. Returns hop-based flow data rendered as Mermaid sankey-beta. If no filter is provided, RISK_INDICATOR is sent by default. Use INCOMING for sources, OUTGOING for destinations, FULL for both. Filters: risk indicators, countries, entity types, counterparty score range, entity name. Dates are Unix timestamps in seconds. The output contains a pre-rendered mermaid block. Include it verbatim — never rewrite or recreate the diagram.
visualize_fund_flow
ChatGPTPOST /sankey for ADDRESS fund-flow visualizations. Returns hop-based flow data rendered as Mermaid sankey-beta. If no filter is provided, RISK_INDICATOR is sent by default. Use INCOMING for sources, OUTGOING for destinations, FULL for both. Filters: risk indicators, countries, entity types, counterparty score range, entity name. Dates are Unix timestamps in seconds. The output contains a pre-rendered mermaid block. Include it verbatim — never rewrite or recreate the diagram.
visualize_fund_flow
ChatGPTPOST /sankey for ADDRESS fund-flow visualizations. Returns hop-based flow data rendered as Mermaid sankey-beta. If no filter is provided, RISK_INDICATOR is sent by default. Use INCOMING for sources, OUTGOING for destinations, FULL for both. Filters: risk indicators, countries, entity types, counterparty score range, entity name. Dates are Unix timestamps in seconds. The output contains a pre-rendered mermaid block. Include it verbatim — never rewrite or recreate the diagram.
visualize_interactions
ChatGPTOpenAPI operation getGraphInteraction: POST /exploration/{blockchain}/interaction with required query direction and body baseElement + targets. Generates graph visualization data for multi-hop transactional relationships between a base address and specified targets, then renders it as a Mermaid flowchart. Targets can be exact addresses, entity names, numeric custom list IDs, or entity types. Provide at least one target. Use INCOMING to find paths where funds move toward the base address; use OUTGOING to find paths where funds move away from it. Optional minDate/maxDate are Unix timestamps in seconds. Optional minAmount maps to the API's amount query parameter. CRITICAL: The output contains a pre-rendered ``mermaid`` block. You MUST include it verbatim in your response. NEVER rewrite, reformat, or manually recreate the Mermaid diagram — the syntax is precise and any modification will cause rendering errors.
visualize_interactions
ChatGPTOpenAPI operation getGraphInteraction: POST /exploration/{blockchain}/interaction with required query direction and body baseElement + targets. Generates graph visualization data for multi-hop transactional relationships between a base address and specified targets, then renders it as a Mermaid flowchart. Targets can be exact addresses, entity names, numeric custom list IDs, or entity types. Provide at least one target. Use INCOMING to find paths where funds move toward the base address; use OUTGOING to find paths where funds move away from it. Optional minDate/maxDate are Unix timestamps in seconds. Optional minAmount maps to the API's amount query parameter. CRITICAL: The output contains a pre-rendered ``mermaid`` block. You MUST include it verbatim in your response. NEVER rewrite, reformat, or manually recreate the Mermaid diagram — the syntax is precise and any modification will cause rendering errors.
visualize_interactions
ChatGPTOpenAPI operation getGraphInteraction: POST /exploration/{blockchain}/interaction with required query direction and body baseElement + targets. Generates graph visualization data for multi-hop transactional relationships between a base address and specified targets, then renders it as a Mermaid flowchart. Targets can be exact addresses, entity names, numeric custom list IDs, or entity types. Provide at least one target. Use INCOMING to find paths where funds move toward the base address; use OUTGOING to find paths where funds move away from it. Optional minDate/maxDate are Unix timestamps in seconds. Optional minAmount maps to the API's amount query parameter. CRITICAL: The output contains a pre-rendered ``mermaid`` block. You MUST include it verbatim in your response. NEVER rewrite, reformat, or manually recreate the Mermaid diagram — the syntax is precise and any modification will cause rendering errors.
