Documentation

The data truth layer for Arc.

Isogram reads Arc mainnet directly and turns it into network activity, project metrics, token and DEX data and DeFi scores, through a dashboard, a public API and an embeddable badge. Every number says where it came from; every gap is shown as a gap.

Why it exists

Arc mainnet launched on 16 September 2026 with USDC as its native gas asset and no public place to answer simple questions: what is deployed, what is being used, how much USDC gas is being spent and where, and which projects are alive. Isogram is that place. It is built for three kinds of reader:

  • Builders who want to see their own contracts and their peers, and embed a badge in a README.
  • The Arc ecosystem team and reviewers who want a fast read on chain health.
  • Anyone curious who wants a clear, open way to browse a brand-new chain.

How it works

Arc mainnetPublic RPC, chain ID 5042
IngestionFollows the tip, one receipts call per block
Daily rollupsPostgres, one row per metric per UTC day
APIRead-only, rate limited, open CORS
Dashboard, badge, your appAll clients of the same API

Isogram follows Arc mainnet block by block and keeps one summary row per metric per UTC day, never individual transactions. Those daily numbers are combined with live contract balances to produce TVL and the Arc Native Score, and with third-party market data where it exists. One read-only API serves all of it. The dashboard and the badge are ordinary clients of that API, and so can you be.

Where the numbers come from

DataSourceRefresh
Transactions, failures, USDC gas, deployments, active addresses, USDC movement, per-project usageArc mainnet RPC, directlyContinuous (seconds behind the tip)
TVLLive token balances of DeFi contracts, read on-chainEvery 4 hours
Arc Native ScoreComputed by Isogram from the aboveEvery 4 hours
Token price, volume, liquidity, FDVGeckoTerminal (CoinGecko), third partyHourly
DEX and launch venue volumeGeckoTerminal, third partyHourly
Holder countsArc explorerAbout every 12 hours
Website and social linksHand-set for verified projects; token deployers' self-reported links otherwiseWeekly

Third-party figures are labelled as such wherever they appear on the dashboard and in the API (source).

Principles

  • Missing is not zero. A figure that was not measured is a dash in the dashboard and null in the API.
  • Partial is marked. The current UTC day is hatched. Days the pipeline did not cover are left out, never filled in.
  • Third party is labelled. On-chain activity and market data have different trust levels and are never blended silently.
  • Listed is not endorsed. Projects are discovered automatically; only verified ones were checked by a person. Names are chosen by deployers and can be misleading.
  • Research, not advice. Nothing here is a trading signal or financial advice.

Where to go next

  • Methodology: exact definitions, the score formula, filters and known limits.
  • API reference: every endpoint, rate limits and how to get a free key.
  • Badges: embed a project's score in a README.
  • Source code: ingestion, scoring, API and dashboard, all open.