Marketplace preview

API marketplace

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

289–312 of 2045 APIs

Warframe Market API

The live player-to-player trading economy of Warframe, read keyless from warframe.market's public API. Warframe has no auction house in-game, so players trade prime parts, mods, relics and arcanes on warframe.market, posting buy and sell orders priced in platinum (the game's premium currency). Those orders form a real, liquid market — the de-facto price book the whole community uses to value items. The items endpoint searches the catalogue of tradeable items by name. The orders endpoint returns the live order book for one item — the buy and sell offers with their platinum price, quantity, mod rank and the seller's online status, sorted so the best deals come first. The price endpoint is the quick summary: the lowest sell and highest buy among players who are actually online (the actionable prices), the spread between them and how many are trading. This is the Warframe Market cut — a distinct gaming player-economy, separate from the official Warframe world-state feed and the other game and marketplace feeds in the catalogue. Prices are in platinum — the in-game premium currency, not real money; its real-world value floats. Only orders from online or in-game players are truly actionable, so the price summary uses those by default (offline players cannot trade). Counts and prices are the real, live numbers; a short cache fronts the upstream. Keyless.

#warframe #gaming #trading
P by PremiumApi
Uptime
100.0%
Latency
148ms
Subs
3,427
Server verified 12 probes/24h

api.oanor.com/warframemarket-api

Steam Community Market API

Live prices from the Steam Community Market (steamcommunity.com/market), the largest virtual-item economy in gaming, read keyless from Steam's public market endpoints. Every day millions of dollars of CS2 skins, Dota 2 items, Team Fortress 2 hats and other in-game items change hands on Steam's marketplace at real, floating prices — a genuine commodity market for digital goods. The popular endpoint lists the most-listed items on the market for a game — the busiest part of the economy, each with its current lowest sell price (USD) and listing count. The search endpoint finds items by name within a game, sorted by price or popularity. The price endpoint returns the live price overview for one specific item: its lowest asking price, median sale price and 24-hour sold volume. This is the Steam Market cut — a distinct gaming-economy / virtual-item trading platform, separate from the Steam store, player-count and review feeds (steamspy, steamreviews) and from the other gaming and marketplace feeds in the catalogue; it is the trading-price layer for virtual items, comparable to a commodity exchange for digital goods. Games are addressed by friendly alias (cs2, dota2, tf2, rust, pubg) or numeric Steam appid. Prices are in US dollars and are the real, live numbers Steam shows; Steam rate-limits market calls, so a protective cache fronts the upstream and stale data is served if the limit is hit. Keyless.

#steam #marketplace #gaming
P by PremiumApi
Uptime
100.0%
Latency
300ms
Subs
4,646
Server verified 12 probes/24h

api.oanor.com/steammarket-api

Habr Tech Community API

Articles, ratings and topic hubs from Habr (habr.com), the largest Russian-speaking technology community, read keyless from its public web API. Habr is where Russian-speaking engineers, scientists and companies publish deep technical articles, and where the community judges them with a signed rating (up-votes minus down-votes) — a score that can go negative, quite unlike a likes-only model. Alongside the rating, every article carries its read count, bookmarks (saves) and comments, and lives in one or more "hubs" (topic communities). The articles endpoint lists the top articles, ranked either by rating over a period (day/week/month/year/all-time) or by date, each with its signed score, vote count, reads, bookmarks, comments, author, hubs and reading time. The article endpoint returns one article in full by its numeric id. The hubs endpoint lists Habr's topic hubs with their subscriber counts and hub rating — the map of Russian tech's interests (AI, information security, programming and the rest). This is the Habr platform cut — a distinct social and developer platform, separate from the Western (dev.to) and Japanese (Qiita) developer communities in the catalogue, with its own signed-rating model and Russian-language community. Scores, reads and subscriber counts are the real, live numbers; a negative score is real, not an error. Titles and hubs are in Russian as Habr publishes them. A short cache fronts the upstream. Keyless.

#habr #russia #developers
P by PremiumApi
Uptime
100.0%
Latency
286ms
Subs
4,996
Server verified 21 probes/24h

api.oanor.com/habr-api

Qiita Developer Community API

Articles, engagement and trending tech tags from Qiita (qiita.com), Japan's largest developer knowledge-sharing community, read keyless from its public v2 API. Qiita is where Japanese engineers post how-tos, deep-dives and notes, and where the community signals quality with LGTM ("looks good to me") likes and "stocks" (saves) — the Japanese counterpart to dev.to or Medium's engineering side, with its own metrics and its own tech-topic rankings. The articles endpoint searches and lists articles, each with its title, LGTM likes, stocks (saves), comment count, tags and author — filterable by keyword, tag and a minimum-stocks threshold so you can surface the popular pieces. The article endpoint returns one article in full by its id. The tags endpoint ranks Qiita's tech tags by how many articles and followers they have — the live map of what Japanese engineers care about (Python, AWS, React and the rest). This is the Qiita platform cut — a distinct social and developer platform, separate from dev.to, Medium and the other blogging and social feeds in the catalogue, with its own LGTM/stock engagement model. Likes are LGTM up-votes and stocks are saves/bookmarks — two distinct Qiita signals; follower and article counts are the real, live community numbers. Titles and tags are in Japanese (and English) as Qiita publishes them. Qiita rate-limits unauthenticated callers, so a longer protective cache fronts the upstream and stale data is served if the limit is hit. Keyless.

#qiita #japan #developers
P by PremiumApi
Uptime
100.0%
Latency
1259ms
Subs
3,884
Server verified 21 probes/24h

api.oanor.com/qiita-api

Bangumi Media Database API

Subject ratings, rankings and collection stats from Bangumi (bgm.tv, "番组计划"), the Chinese cross-media community database for anime, books/manga, music, games and live-action drama, read keyless from its public v0 API. Bangumi is China's "Douban for ACG": a two-decade catalogue where users rate and collect titles across every medium and the community score and rank are what fans trust. Unlike the anime-first databases (MyAnimeList, AniList), Bangumi spans games, books, music and TV/film too, and exposes a collection breakdown — how many users wish for, are doing, have completed, put on hold or dropped each title — that is its own distinctive engagement signal. The search endpoint finds subjects by keyword, optionally filtered to one medium and sorted by rank, match or score. The subject endpoint returns one title's full profile by its Bangumi id: its Japanese and Chinese names, medium, date, community score and vote count, overall rank, the full collection breakdown, tags and summary. The calendar endpoint returns the anime airing each day of the week, with their scores. This is the Bangumi cut — a distinct social and reference platform, separate from the anime-first feeds and the other media databases in the catalogue, spanning all media with Chinese community metrics. Scores, ranks and collection counts are the real, live community numbers; rank is null for titles with too few votes to be ranked. Names and summaries are Japanese and Chinese as Bangumi publishes them; an nsfw flag is reported honestly and adult titles are excluded from search. Keyless, a short cache fronts the upstream.

#bangumi #china #anime
P by PremiumApi
Uptime
100.0%
Latency
148ms
Subs
3,796
Server verified 24 probes/24h

api.oanor.com/bangumi-api

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

Naver Webtoon API

Live data from Naver Webtoon (comic.naver.com), the world's largest webtoon platform, read keyless from Naver's public webtoon API. Naver Webtoon is where the modern vertical-scroll webtoon was born and where Korea's biggest series — Tower of God, Solo Leveling, Lookism and thousands more — are serialised; it is the centre of a global comics phenomenon. The weekday endpoint returns the webtoons that update on a given day (Monday to Sunday), ranked by readership, each with its title, author, reader star-rating and status flags (new, updated today, completed, on hiatus, 19+). The title endpoint returns one webtoon's full profile by its Naver title id: its synopsis, genre tags, age rating, the days it publishes, its subscriber (favourite) count and whether it has finished. This is the Naver Webtoon platform cut — a distinct social and creative platform, separate from the manga feeds (MangaDex) and the other comics and social feeds in the catalogue; webtoons are a distinct vertical-scroll format. Star ratings and subscriber counts are the real, live numbers Naver shows; titles, authors, genres and synopses are in Korean as Naver publishes them. Note: Naver does not expose raw view counts through this API, so none are reported — the subscriber count is the platform's popularity metric. A short cache fronts the upstream. Keyless.

#naver #webtoon #korea
P by PremiumApi
Uptime
100.0%
Latency
520ms
Subs
3,422
Server verified 18 probes/24h

api.oanor.com/naverwebtoon-api

pixiv Rankings & Artwork API

Live rankings and artwork engagement from pixiv (pixiv.net), Japan's dominant art-and-illustration social network, read keyless from pixiv's public ranking and artwork endpoints. pixiv is where millions of illustrators, manga artists and animators post their work and where fans drive it up the daily, weekly and monthly rankings with views and bookmarks — the platform at the centre of anime and illustration fan culture, far bigger in that world than DeviantArt or ArtStation. The ranking endpoint returns the official pixiv ranking for a mode (daily, weekly, monthly, rookie, original, and the male/female popularity cuts) — the top works ranked, each with its rank (and previous-day rank), title, artist, view count, ranking points (bookmark-weighted), work type and tags; pass a content filter (illust, manga, ugoira), a page (1-10, 50 per page) or a past date. The illust endpoint returns one artwork in full by its pixiv id: its view, bookmark, like and comment counts, tags, dimensions, page count, upload date and age-restriction flag. This is the pixiv platform cut — a distinct social and creative platform, separate from danbooru (an imageboard aggregator) and from the other social and art feeds in the catalogue. Only safe-for-work ranking modes are exposed; individual artworks carry an x_restrict flag so age-restricted works are clearly labelled, not hidden. Counts are the real, live numbers pixiv shows; a short cache fronts the upstream. Keyless.

#pixiv #illustration #art
P by PremiumApi
Uptime
100.0%
Latency
466ms
Subs
3,204
Server verified 9 probes/24h

api.oanor.com/pixiv-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