Indexed Fetch.aiBlockchain Data

Fetch.ai is a Cosmos SDK chain whose validators run CometBFT under proof of stake, with a ledger binary that adds a decentralized random beacon and a compact multi-signature scheme to the standard stack. FET is the native token, counted in afet, and accounts are bech32 strings carrying a fetch prefix. Contracts are CosmWasm, compiled to WebAssembly, and one of them defines what the chain is for: the Almanac, a registry where autonomous agents record what they offer and how they can be reached, with entries that lapse unless they are renewed. Since the project joined the Artificial Superintelligence Alliance, its own documentation presents the network under the ASI name while FET remains the token that pays for blocks. IBC channels connect it to the Cosmos Hub and the wider interchain.

SonarX indexes what the chain records: blocks and transactions with their typed messages, CosmWasm instantiate and execute calls with the attributes they emit, staking and reward records, IBC transfers with the denominations they carry, and derived account balances. Everything is normalized into the model SonarX uses across every network it covers, so registry activity joins to the token flows that paid for it.

Full historical coverage is available today as a data-share or a file delivery. Real-time delivery is enabled on request.

The registry is state rather than a stream of transfers. A registration is an execute call against the Almanac with a lifetime attached, so the question worth asking is which agents were current at a given height, and that is answered by replaying the contract’s calls rather than by reading a balance. CosmWasm events are attribute pairs a contract chooses to emit, not logs decoded against an ABI, so decoding follows each contract’s own schema instead of a shared standard. FET also exists as an ERC-20 on Ethereum, so a supply figure from this chain alone is only one side of the token.

Reward and delegation accounting is the workload most institutions arrive with, because a position’s income has to be derived per period and per validator with commission netted out, and staking analytics covers that work across chains. Registry analysis is the one specific to this network: counting live entries over time, and seeing which of them are renewed, is a usage measure that no transfer series contains. Token accounting is the third, and it spans two ledgers, since FET circulates natively here and as an ERC-20 elsewhere. Desks studying machine-paid networks together usually hold Bittensor in the same warehouse.

Tell us the delivery target, how far back you need and how fresh it has to be, and the share is scoped against that. Fetch.ai coverage is provisioned on request, so tell us the history depth and the delivery target and we will scope it. Say whether contract state matters as much as transfers, because that changes what a backfill has to replay. The published coverage matrix for every network SonarX indexes lives in the data documentation, and the rest of the catalogue is at all indexed chains.