Managed Data API
Canonical snapshots, customer API keys, dataset versions, delivery quotas and measured freshness.
Open a working application, inspect its source and understand its limits. Managed customer APIs and institutional services are identified separately.
Four public-data apps, source receipts, CSV/JSON exports and notebook continuation.
Data is read when you open a view or request a refresh. Upstream availability and publication cadence apply.
| Application | What it measures | Coverage boundary | Access |
|---|---|---|---|
| USDC across chainsDefiLlama + public RPC | Reported circulating tokens; separate USD distribution; selected contract totalSupply | All chains reported by DefiLlama. Contract spot checks cover curated deployments, not every issued or bridged contract. | Open app |
| Stablecoin explorerDefiLlama + public RPC | USD-pegged asset distribution; USDT/USDC dated supply history | Provider-reported circulation. Authorized, issued and minted supply remain distinct. | Open app |
| DeFi TVL monitorDefiLlama | Chain TVL, public history and global protocol rankings | Provider-defined USD TVL. A chain filter selects protocols active there; their reported TVL is still global. | Open app |
| Tokenized asset monitorPublic RPC + issuer references | BUIDL, OUSG and USDY supply on selected deployments | Exact token/share counts from contracts. No NAV, asset backing or global AUM is inferred. | Open app |
These endpoints support the research apps. They are public source proxies with receipts, not a contracted customer Data API.
Normalized DefiLlama protocol data and its source receipt.
GET /api/llama/protocolsUp to 366 dated source observations, with token and USD values separated.
GET /api/llama/stablecoin-supply/2The same bounded history format, with a request and response hash.
GET /api/llama/stablecoin-supply/1Successful responses can be cached for up to ten minutes. Their source fetch time is retained. These routes have no customer accounts, commercial quotas or contractual service levels. Other supported contract and API reads run directly in the browser.
Canonical snapshots, customer API keys, dataset versions, delivery quotas and measured freshness.
Quoted archive jobs, resumable backfills, spending caps and an auditable usage ledger.
Shared workspaces, roles, private data access and audit logs. Additional controls will follow agreed pilot requirements.
Managed ingestion and customer billing are not operational in the current product. No enterprise SLA or compliance certification is claimed. Public-source history and current app exports remain free.
These are planning prices, not offers available for checkout. Institutional engagements require an agreed dataset, coverage, delivery volume and support scope.