Marketplace preview

API marketplace

Discover and integrate APIs through oanor's secret-safe gateway.

241–264 of 793 APIs

Fibonacci Levels API

Automatic Fibonacci retracement and extension levels for any stock, index, FX pair, commodity or crypto, computed live from Yahoo Finance candles, no key. Fibonacci levels are the support/resistance map traders draw from a trend's swing high and swing low: after a move, price tends to pull back to the 38.2%, 50% or 61.8% retracement before resuming, and to project to the 127.2%, 161.8% or 261.8% extension as a target. This finds the dominant recent swing automatically and lays the levels out, with where price sits right now. The retracement endpoint detects the swing high and low over a lookback window, works out the trend direction, and returns the retracement levels (0, 23.6, 38.2, 50, 61.8, 78.6, 100%) with their prices — plus which two levels price is currently between and the nearest one. The extension endpoint returns the projection targets beyond the swing (127.2, 141.4, 161.8, 200, 261.8%) in the trend's direction. Both report the swing they were built from so you can see exactly what was measured. This is the Fibonacci-levels cut — a distinct price-level tool, separate from the oscillator and channel indicator feeds (RSI, MACD, Bollinger, SuperTrend, Keltner), from FX pivot points and from the Ichimoku system. Levels are in the instrument's own price; the swing is detected mechanically (highest high / lowest low over the window), not hand-picked. Interval (1d/1wk/1mo) and lookback are configurable. Keyless, nothing stored beyond a short cache.

#fibonacci #retracement #extension
P by PremiumApi
Uptime
100.0%
Latency
126ms
Subs
3,352
Server verified 9 probes/24h

api.oanor.com/fibonacci-api

Ichimoku Cloud API

The Ichimoku Kinko Hyo ("one-glance equilibrium chart") for any stock, index, FX pair, commodity or crypto, computed live from Yahoo Finance daily, weekly or monthly candles, no key. Ichimoku is a complete Japanese trend system, not a single line: five components — Tenkan-sen (conversion), Kijun-sen (base), Senkou Span A and B (which form the Kumo cloud) and the Chikou (lagging) span — together give a one-glance read on trend, momentum and support/resistance. Its defining feature is the cloud, projected 26 periods into the future, that acts as forward support and resistance. The ichimoku endpoint returns the full current reading for a symbol: all five lines, the current cloud (top, bottom and colour), where price sits relative to the cloud, the Tenkan/Kijun cross, the Chikou confirmation and an overall signal — plus the forward-projected cloud. The history endpoint returns the recent series of the lines for charting. Everything is computed with the correct time-shifts: the current cloud uses the leading spans as they were plotted 26 periods ago (the cloud price sits in today), and the forward cloud is today's leading spans projected ahead — the distinction many naive implementations get wrong. This is the Ichimoku system cut — distinct from the single-indicator feeds in the catalogue (SuperTrend, Keltner, Donchian, MACD, RSI). Levels are in the instrument's own price; signals are mechanical reads of the lines, not advice. Conversion, base, leading-B and displacement periods are all overridable. Keyless, nothing stored beyond a short cache.

#ichimoku #technical-analysis #indicator
P by PremiumApi
Uptime
100.0%
Latency
140ms
Subs
3,573
Server verified 9 probes/24h

api.oanor.com/ichimoku-api

Liquid Restaking Tokens Comparison API

The major Ethereum liquid-restaking tokens (LRTs) compared side by side, read keyless directly from the Ethereum blockchain via a public RPC node. Restaking is the DeFi narrative EigenLayer kicked off: you stake ETH and then restake it to also secure other services, earning Ethereum staking rewards PLUS restaking rewards on top. A liquid-restaking token — weETH (ether.fi), ezETH (Renzo), pufETH (Puffer) or rswETH (Swell) — is the liquid receipt for that position, and its on-chain exchange rate against ETH climbs as those combined rewards accrue. Restaking is a distinct, fast-moving asset class from plain liquid staking, and the spread between these tokens' rates and yields is what someone choosing a restaking provider (or arbitraging between LRTs) needs in one place. The rates endpoint is the comparison table: every tracked LRT with its live ETH exchange rate, its net APR over the last 30 days, its token supply and its issuer, ranked by yield. The token endpoint drills into one LRT by symbol — its rate, supply, ETH backing (TVL) and the APR over the last day, week and month. The convert endpoint converts any amount between any LRT and ETH, or between two LRTs, at the current on-chain rates. This is the liquid-RESTAKING comparison cut — distinct from liquid-STAKING tokens (the lstcompare feed), the single-protocol feeds (ether.fi, lido) and the DeFi-TVL feeds. Each token rate comes from its own on-chain rate source (a getRate() call, a rate-provider, or an ERC-4626 vault, depending on the protocol). APR is derived from real historical on-chain state; the 30-day window is used because several LRT rates update on an oracle schedule or in discrete ERC-4626 steps, making shorter windows noisy. The rate reflects realised value accrual — many LRTs additionally distribute points/airdrops that are NOT captured by the exchange rate. Rates are ETH per token. Keyless, nothing stored beyond a short cache.

#liquid-restaking #lrt #restaking
P by PremiumApi
Uptime
100.0%
Latency
201ms
Subs
4,056
Server verified 12 probes/24h

api.oanor.com/lrtcompare-api

Liquid Staking Tokens Comparison API

The major Ethereum liquid-staking tokens (LSTs) compared side by side, read keyless directly from the Ethereum blockchain via a public RPC node. When you stake ETH through Lido, Rocket Pool, Coinbase, Binance or Frax you receive a liquid-staking token — wstETH, rETH, cbETH, wBETH or sfrxETH — whose on-chain exchange rate against ETH climbs as staking rewards accrue. Those rates, and the yields implied by how fast they climb, differ between providers, and that spread is exactly what someone choosing where to stake (or arbitraging between LSTs) needs in one place. The rates endpoint is the comparison table: every tracked LST with its live ETH exchange rate, its net staking APR over the last week (derived from the on-chain rate growth), its token supply and its issuer, ranked by yield. The token endpoint drills into one LST by symbol — its rate, supply, ETH backing (TVL) and the APR over the last day, week and month. The convert endpoint converts any amount between any LST and ETH, or between two LSTs, at the current on-chain rates. This is the cross-LST comparison cut — distinct from the single-protocol feeds (lido, Rocket Pool, ether.fi) and the DeFi-TVL feeds: it is about the exchange rates and on-chain-derived yields of the staking tokens themselves. Every number is read live from each token contract; APR is derived from real historical on-chain state, not a marketing figure. Rates are ETH per token. Keyless, nothing stored beyond a short cache.

#liquid-staking #lst #steth
P by PremiumApi
Uptime
100.0%
Latency
187ms
Subs
3,013
Server verified 12 probes/24h

api.oanor.com/lstcompare-api

Lido Liquid Staking API

Live data for Lido, the largest liquid-staking protocol in crypto, read keyless directly from the Ethereum blockchain via a public RPC node. Stake ETH with Lido and you get stETH, a rebasing token worth one ETH that earns Ethereum staking rewards; wstETH is the wrapped, non-rebasing version whose exchange rate against stETH grinds upward as rewards accrue — the form most of DeFi actually holds. Lido is by far the biggest staker of ETH, so its size and yield are a benchmark the whole staking market is measured against. The overview endpoint is the headline: how much ETH is staked through Lido (its TVL in ETH, equal to the stETH supply), the wstETH supply, the current wstETH-to-stETH exchange rate and the net staking APR. The apr endpoint computes the real, net-of-fees staking yield directly from the on-chain wstETH exchange rate — how much that rate has grown over the last day, week and month, annualised with actual block timestamps — the honest yield a wstETH holder has earned, not a marketing figure. The wsteth endpoint is the wstETH conversion reference: how much stETH one wstETH is worth and vice-versa, the wstETH supply and the share of stETH that is wrapped. The convert endpoint converts any amount between ETH, stETH and wstETH at the current on-chain rate. This is the Lido cut — distinct from ether.fi (liquid restaking), Rocket Pool (rETH) and the Ethereum staking-queue and consensus feeds. Everything is read live from the stETH and wstETH contracts; no USD value is fabricated. Keyless, nothing stored beyond a short cache.

#lido #liquid-staking #steth
P by PremiumApi
Uptime
100.0%
Latency
133ms
Subs
4,017
Server verified 15 probes/24h

api.oanor.com/lido-api

Ethereum Staking Queue API

The live Ethereum validator entry and exit queues, read keyless straight from a public consensus-layer (Beacon) node. To stake on Ethereum you join a queue to activate a validator, and to unstake you join a separate queue to exit — both rate-limited by the protocol churn limit. The size of these queues is the cleanest real-time signal of staking demand and exit pressure: a long entry queue means capital is rushing in to stake, a long exit queue means validators are leaving. Liquid-staking protocols, exchanges, stakers and ETH analysts watch the queue to time deposits and withdrawals. The queue endpoint is the headline dashboard — how much ETH is waiting to activate (entry) versus exit, the validator counts behind each, the net flow, and an estimate of how long each queue takes to clear at the current activation/exit churn limit (256 ETH per epoch, ~6.4 min). The entry endpoint breaks down the activation side (validators already eligible and churning in, plus freshly-deposited validators not yet eligible). The exit endpoint breaks down the exit side (voluntary exits plus validators forced out by slashing). The validator endpoint looks up any single validator by index or public key: status, balance, effective balance, slashed flag and activation/exit epochs with wall-clock times. ETH amounts are the meaningful queue metric — a single post-Pectra validator can hold up to 2048 ETH — with counts given alongside. Distinct from beaconchain-api (consensus finality), the Solana validator feeds and the liquid-staking protocol feeds. Live, keyless, nothing stored beyond a short cache.

#ethereum #staking #validators
P by PremiumApi
Uptime
100.0%
Latency
316ms
Subs
4,591
Server verified 15 probes/24h

api.oanor.com/ethstakingqueue-api

Ethereum Beacon Chain Consensus API

The live consensus state of Ethereum's Beacon Chain — the proof-of-stake layer that secures Ethereum — read keyless straight from a public consensus-layer node. The single thing that matters for the health of proof-of-stake Ethereum is whether it is finalizing: every epoch (about every six and a half minutes) the validators are supposed to justify and then finalize the chain, and on the rare occasions that finality stalls — as it briefly did in 2023 — staking services, exchanges and bridges need to know immediately. The status endpoint returns the current head slot and epoch, how far through the current epoch the chain is and how long until the next one, the finalized and justified epochs, the finality lag (how many epochs behind finality the head is — a lag of two is healthy, a growing lag is trouble) and whether the node is fully synced and finalizing. The finality endpoint returns the finalized, current-justified and previous-justified checkpoints in detail, with how far behind the head each is in epochs and minutes. The genesis endpoint returns the chain's genesis time, how long Ethereum proof-of-stake has been running and the slot/epoch timing constants (a slot every 12 seconds, 32 slots per epoch). This is the Ethereum consensus / finality cut — distinct from the execution-layer feeds (gas, blocks, transactions), the staking-token and restaking feeds and the price feeds: it is the beacon chain's own heartbeat. Note it reports consensus state (slots, epochs, finality), not per-validator economics, which a public consensus node does not serve in one call. Times are UTC; epochs and slots are integers. No key, nothing stored beyond a short cache.

#ethereum #beacon-chain #consensus
P by PremiumApi
Uptime
100.0%
Latency
97ms
Subs
3,843
Server verified 12 probes/24h

api.oanor.com/beaconchain-api

Bitcoin Hashprice & Mining Profitability API

The Bitcoin hashprice — the single number every Bitcoin miner watches: how many US dollars a unit of hashing power earns in a day. It is the mining industry's revenue benchmark (the "Hashprice Index"), and it falls every time the difficulty rises, the block subsidy halves, fees dry up or the price drops. This computes it live and keyless from on-chain data and the BTC price: the daily Bitcoin the whole network mines (block subsidy plus transaction fees), the network hashrate, and the dollar price of Bitcoin. The hashprice endpoint returns the current hashprice in dollars per PH/s per day and per TH/s per day, with the inputs behind it — the network hashrate, the daily Bitcoin mined, the share of that which is fees, and the BTC price. The breakeven endpoint turns it into a profitability check: give it your electricity cost (USD per kWh) and your rig's efficiency (J/TH) and it returns the daily revenue, power cost and profit per TH/s, the margin, and the breakeven hashprice at which you would mine at a loss. The asic endpoint runs the same maths over today's popular ASIC miners (Antminer S21, S19 XP, Whatsminer M60 and more) at your electricity cost — daily revenue, power cost and profit for each machine, ranked. This is the hashprice / mining-profitability cut — distinct from the network-security feed (difficulty, hashrate, halving), the multi-coin mining-economics feed (which ranks coins by a relative profitability index, not the dollar hashprice) and the mining-pool-distribution feed. Hashprice is in USD per PH/s and per TH/s per day; costs in USD. No key, nothing stored beyond a short cache.

#bitcoin #hashprice #mining
P by PremiumApi
Uptime
100.0%
Latency
99ms
Subs
3,100
Server verified 12 probes/24h

api.oanor.com/hashprice-api

ether.fi Liquid Restaking API

Live data for ether.fi, the largest liquid-restaking protocol on Ethereum, read keyless from ether.fi's public APR feed and directly from the Ethereum blockchain. Stake ETH with ether.fi and you get eETH, a rebasing token worth one ETH that earns both Ethereum staking rewards and EigenLayer restaking rewards on top — the "restaking premium" that made liquid restaking the fastest-growing corner of DeFi. weETH is the wrapped, value-accruing version of eETH that most of DeFi actually holds and lends against, and its eETH exchange rate is the number you need to value it. The apr endpoint returns the eETH restaking APR — the latest reading plus the recent daily history and its average. The restaked endpoint reads the chain directly: the total ETH restaked through ether.fi (the eETH supply, which rebases to track ETH one-for-one) and its US-dollar value, plus how much of it is wrapped into weETH versus held as eETH. The weeth endpoint is the wrapped-token view: the weETH supply and its on-chain rate — how much eETH (and therefore ETH and USD) one weETH is worth right now, the figure lending markets use to price weETH collateral. This is the ether.fi liquid-restaking cut — distinct from the synthetic-dollar protocol feed, the generic staking and yield-aggregator feeds and the generic token-info feed: it is the single-protocol view of the biggest restaking token, its yield, its size and its wrapped-token rate. APR is an annualised percentage; amounts are in ETH and USD; the rate is eETH per weETH (above 1.0, rising as yield accrues). No key, nothing stored beyond a short cache.

#etherfi #eeth #weeth
P by PremiumApi
Uptime
100.0%
Latency
250ms
Subs
3,251
Server verified 12 probes/24h

api.oanor.com/etherfi-api

Chainlink Price Feeds API

The on-chain prices that DeFi actually runs on, read live and keyless straight from Chainlink's price-feed contracts on Ethereum. Chainlink is the dominant oracle: a decentralised network writes each price on-chain and refreshes it on a heartbeat or when it moves past a deviation threshold, and thousands of lending, perpetual and stablecoin protocols read that exact number to value collateral and trigger liquidations. What matters is not just the price but whether the feed is fresh — a stale Chainlink feed is how DeFi protocols break — and that on-chain freshness is exactly what this exposes. The feeds endpoint lists every tracked Chainlink feed (crypto, stablecoins and FX) with its current on-chain answer, how many seconds ago it last updated and whether it is fresh. The feed endpoint returns one pair's full detail by name, including the round id, the update timestamp and the feed contract address. The health endpoint is the oracle-monitoring view: how many feeds are fresh versus stale, the stalest feed and the average update age — the on-chain reliability picture that a plain price API can't give you. Each price is read from the feed's latestRoundData and scaled by the feed's own on-chain decimals (USD feeds use 8); the update time is the contract's updatedAt. This is the Chainlink on-chain-oracle cut — distinct from the off-chain oracle-price APIs (which serve a price but not the on-chain feed's round and freshness) and from the exchange price feeds. Prices are in the feed's quote unit (USD here); times are UTC. No key, nothing stored beyond a short cache.

#chainlink #oracle #price-feed
P by PremiumApi
Uptime
100.0%
Latency
131ms
Subs
3,650
Server verified 12 probes/24h

api.oanor.com/chainlink-api