What problem does it solve? Fetching on-chain data from the Internet Computer normally requires deploying a canister or running an agent, but many read-only queries only need public HTTP endpoints. This Skill documents the five public REST APIs behind dashboard.internetcomputer.org so off-chain scripts and agents can retrieve canister metadata, token data, SNS proposals, and network metrics without deployment or cycles. ## Core Features & Use Cases - Five documented API surfaces: IC API (canisters, subnets, NNS proposals), ICRC API (non-ICP ledgers like ckBTC), SNS API (SNSes, proposals, neurons), Ledger API (mainnet ICP accounts and supply), and Metrics API (cycles, governance, ICP/XDR rates). - Cursor-based pagination guidance: Explains v2+/v4 endpoints using after, before, and limit with next_cursor/previous_cursor, and warns against legacy offset-based endpoints. - Pitfall prevention: Covers canister ID format rules, Unix-second timestamps, account identifier hex encoding, and the critical distinction that mainnet ICP lives on the Ledger API, not the ICRC API. - Use Case: An analyst wants to track ckBTC transactions and ICP total supply in a nightly script. Using this Skill, they call the ICRC API v2 transactions endpoint for ckBTC and the Ledger API supply endpoint for ICP, paginating with cursors. ## Quick Start Ask the AI to list the ten most recent transactions for the ckBTC ledger using the ICRC API v2 endpoint with curl.