Real-time charts for every market, in one place
Trade smarter with real-time market insight.
Every chart, every market, one workspace.
Fast, clean charts with built-in indicators, drawing tools, and layouts that just work.
Cryptocurrency Heatmap
Real-time market cap visualization for top crypto coins
See which cryptocurrencies are gaining or losing at a glance — bubble size reflects market cap, color reflects 24h price change.
API3 to USDT Converter
1 API3 = 0.246898 USDT · updated 06:19 UTC
Volume Bubbles Chart (1h)
Each 1-hour candle's volume is signed by its direction (up candles count as net buying, down candles as net selling) and drawn as a bubble at the closing price, green for buying and red for selling. Bubble size and colour intensity show how strong that flow is compared with the last 300 candles: the strongest 30% get full bubbles with their USD value, the rest stay as small dots. Unusually large bubbles flag aggressive buying or selling worth a closer look, often near breakouts, reversals or key levels.Seasonal Chart
Plots one line per calendar year showing the % change since the start of that year, with the current year highlighted against up to four previous years. Lining the years up on the same calendar shows whether the price tends to rise or fall in the same months, helping you spot recurring seasonal patterns. Treat it as context rather than a forecast: past seasonality does not guarantee future moves.Api3 Markets
Api3 Historical Data
About Api3 (API3)
API3 connects data providers directly with smart-contract applications through Airnode and dAPIs. Its token participates in a DAO staking and governance system, while OEV Rewards form a separate mechanism for qualifying applications.
First-party data feeds
API3 develops oracle infrastructure that connects data from API providers to blockchain applications. The Airnode docs describe a first-party oracle. The API provider runs the node that puts its data on-chain, rather than handing the job to an unrelated operator. API3’s data feeds are called dAPIs, and the project also documents a request-response protocol for contracts that request data directly. This design is the main technical context for API3; the token is one part of the ecosystem, not the data feed itself.
Airnode and dAPIs
Airnode is designed to run as a background service for an API provider. The docs explain how provider API operations map to endpoints and how data is supplied to on-chain beacons that support dAPIs. A distributed application can read a feed through a reader proxy, while the exact feed and contract address depend on the application and network. Airnode supplies first-party provider data; a dAPI exposes that data as an on-chain feed. Holding API3 does not itself integrate a particular feed into a smart contract.
What API3 holders can do
The API3 DAO docs say holders can stake tokens in the DAO pool to qualify for rewards and voting rights. Staking also connects participants to DAO decisions on staking incentives, collateralization parameters, and grants that transfer treasury assets to contributors. The same docs describe an adaptive reward rule. Rewards rise when the pool is below its stake target and fall when it is above that target. These are rules set by the DAO, not a fixed reward rate for every wallet.
Oracle Extractable Value
API3’s docs define Oracle Extractable Value, or OEV, as value tied to an oracle update that changes a smart contract’s state. API3’s OEV system allows searchers to compete for exclusive rights to execute certain updates. Apps using OEV-enabled feeds receive 80% of the resulting revenue as OEV Rewards. The developer docs say the protocol keeps the rest as a fee. This mechanism relates to qualifying feed integrations; it does not imply that every application or API3 holder receives OEV income.
Governance and setup details
API3 governance runs through its DAO, and the official governance docs require staked API3 to participate in votes on incentives, collateralization parameters, and grants. The OEV and Airnode docs describe distinct tools within the ecosystem. Airnode carries first-party API data, dAPIs expose on-chain feeds, and OEV auctions let qualifying dApps receive 80% of resulting revenue as OEV Rewards. Holding API3 does not itself integrate an oracle feed into an application.
Last reviewed: Oct 9, 2026
Api3 (API3) FAQ
What is the circulating supply of API3?
The live circulation figure for API3 is 147,601,762 tokens. The API3 DAO docs say tokens staked in its pool can qualify holders for rewards and voting rights. This market-supply field is not the same measure as the balance deposited in the DAO staking pool.
What is the current API3 price?
API3’s FMchart composite quote stands at $0.2465. Its Airnode model lets API providers run first-party oracle nodes and supply data to apps through dAPIs or direct requests. The market quote combines supported venues; it does not report feed freshness or the revenue earned by an app.
What does API3 do?
API3 builds oracle tools that bring API-provider data on-chain. Its Airnode documentation describes a first-party design where the provider operates the oracle node; dAPIs expose on-chain data feeds, and a request-response protocol supports direct requests from smart contracts. API3 Market lists feeds across supported EVM networks. Using the API3 token does not alone establish that an application has integrated a specific feed.
What is API3’s all-time high?
API3’s recorded market high is $10.3, dated Apr 6, 2021. Its ecosystem includes DAO staking and first-party oracle software: Airnode lets an API provider run the node that brings data on-chain. A price peak records token trading, not the number of active feeds or the validity of an oracle response.
How has API3 performed over time?
In FMchart's composite price history (since January 2022), API3’s strongest month was February 2022 (+120.6%); May 2022 (-42.7%) marks the weakest month. Positive annual returns were recorded in 1 of 4 full calendar years years. These price results do not show how many dApps use Airnode or how much OEV revenue eligible apps received.
What is an API3 dAPI?
A dAPI is an API3 data feed that makes API-provider information available on-chain. Airnode supplies data to provider beacons, which the API3 server contract can expose through feed contracts. The documentation also describes direct request-response calls, although it notes dAPIs are generally more efficient for common feed use. Which feed to use depends on the application and the supported blockchain.
How does API3 staking work?
API3’s DAO guide says tokens deposited into the staking pool make participants eligible for rewards and governance rights. Its adaptive system raises incentives when total stake is below the target and lowers them when the pool is above target. Staking therefore links token holders to protocol participation, but the documentation does not define one permanent reward rate that applies to every amount or every period.
What are API3 OEV Rewards?
API3 defines Oracle Extractable Value as value that can arise around an oracle update. Its OEV system lets searchers compete for exclusive rights to execute certain updates, and the documentation says 80% of associated revenue is paid to eligible dApps as OEV Rewards. The remainder is retained as a protocol fee. This revenue flow depends on supported integrations, not simply on holding API3.
Who makes API3 governance decisions?
The API3 DAO votes on issues such as staking incentives, collateralisation parameters for DAO contracts, and grant proposals that allocate treasury assets to contributors. The governance documentation says staking API3 in the pool is required to participate. Governance concerns the protocol’s shared decisions; it does not mean each token holder directly controls the data source or smart contract of every dApp using an API3 feed.
Does API3 data come from third parties?
API3’s Airnode design is described as first-party: the entity that owns the API operates its oracle node and supplies the data. This is different from a design where an unrelated operator relays the source’s information. Data still comes from an API provider, and a developer must integrate the correct dAPI or request endpoint for the target chain and application.