#analytics

Live install analytics for Homebrew, the macOS and Linux package manager, from the public formulae.brew.sh feed — no key, nothing stored. The adoption view of the Homebrew ecosystem: how much each command-line formula and each desktop-app cask is installed, and the most-installed packages overall, distinct from the Homebrew formula-catalog API in the catalogue (which describes a package — this measures how much it is actually used). The formula endpoint returns a command-line tool's install counts over 30, 90 and 365 days plus install-on-request, with its version and description. The cask endpoint returns a desktop app's install counts. The top endpoint returns the most-installed formulae or casks over a chosen window, ranked. Build developer-tool popularity dashboards, "is this tool still maintained and used" widgets, package-trend trackers and ecosystem-health tools on top of real Homebrew analytics. Look up a formula by its name (wget, node, ffmpeg) or a cask by its token (google-chrome, visual-studio-code); counts come from Homebrew's opted-in user analytics.

api.oanor.com/brewanalytics-api

Live economic-activity metrics for Ethereum Layer-2 rollups — Arbitrum, Base, Optimism, zkSync, Linea, Scroll, Polygon and more — powered by the public growthepie.xyz feed, no key, nothing stored. This is the L2 fundamentals cut: not a single chain's block or gas data, but how much each rollup is actually used and what it earns. The chains endpoint lists the tracked rollups. The chain endpoint returns one rollup's latest metrics: daily active addresses, transaction count, fees paid, on-chain profit (the fees it keeps after paying Ethereum to post its data), median transaction cost, stablecoin supply, total value locked, market cap and fully-diluted valuation. The metric endpoint ranks every rollup by a single metric, so you can see at a glance which L2 leads on users, fees or profit and how the scaling race is shifting. Track the real adoption and economics of the rollup ecosystem as live JSON. This is the L2 activity / economics cut — distinct from the per-chain on-chain (block and gas) APIs and the TVL-only APIs in the catalogue.

api.oanor.com/growthepie-api

Live readership-trend data from the Wikimedia Pageviews API — the official measure of what the world is reading on Wikipedia and its sister projects. See the most-viewed articles on any Wikipedia language edition for a given day (the daily trending list); pull the daily or monthly pageview trend for any single article over a date range; read a whole project's total pageviews over a range as a barometer of overall traffic; or rank several articles head-to-head by total views for topic-engagement comparison. Special / namespace pages (Main Page, Search, Portal…) are filtered out by default so the trending list is real articles. Read live from Wikimedia, nothing stored — data lags about 1-2 days, so ranges default to ending two days back. This is the Wikipedia readership-trend and topic-engagement layer for any trends, research, newsroom or analytics app — distinct from Wikipedia content APIs: this is the pageview, trending and engagement signal of what people are actually reading and how it changes.

api.oanor.com/wikitrends-api

Live Bitcoin on-chain economics and network-activity statistics, built on the open blockchain.com dataset — the macro on-chain layer, not raw address or mempool lookups: a live network snapshot (24h transaction count and USD volume, hash rate, market price and cap, total mined supply, miners' revenue), the historical time series of any curated on-chain metric (active addresses, transaction volume, UTXO-set size, mempool size, miner revenue, fees and more), the catalog of available metrics, and Bitcoin's issuance state (total mined, share of the 21M cap, current block reward and estimated next halving).

api.oanor.com/bitcoinstats-api

Live Bitcoin mining and hashrate analytics, built on the open mempool.space dataset — the mining layer, not address or mempool data: the mining-pool dominance ranking by share of blocks mined over a period, the current network hashrate and difficulty plus their history, the history of difficulty adjustments with each retarget's percentage change, and block-reward economics over the last N blocks (total and average reward, fees and transactions).

api.oanor.com/mining-api

Live project, release and download data from SourceForge, the original open-source software forge and download host. Unlike a git forge, SourceForge is built around distributing release binaries to the world, so its signature data is who downloads what, from where. Get a project's profile — its name, summary, status, creation date, homepage, the categories it is filed under and its developer count. Pull the download statistics for a date range — the total, the daily series and the breakdown by operating system. See where in the world a project is downloaded, the per-country download counts that no git forge exposes. Get the project's best current release with its file, version, size and date, plus the recommended download for Windows, macOS and Linux. Live, no key, nothing stored. Distinct from GitHub, GitLab and Codeberg git-forge APIs and from package registries — this is SourceForge's project directory and its global download analytics. Perfect for software-directory, release-tracking, download-analytics and developer apps.

api.oanor.com/sourceforge-api

Steam game ownership and player analytics as an API, powered by SteamSpy — clean JSON, no key. Look up any Steam game by app id for its estimated owners, current concurrent players, average and median playtime (all-time and last two weeks), price and discount, positive/negative review counts and review score, developer, publisher, genre, languages and top community tags. Pull the top-100 lists — games by current players, by all-time playtime and by estimated owners — and list the top games in any genre or with any tag. Live market data straight from SteamSpy. Distinct from the Steam store: this is the ownership and engagement layer — ideal for game-market research, indie-dev competitor analysis, trend dashboards and charts. 6 data endpoints. Authenticated with an x-oanor-key; fair-use rate limits per plan.

api.oanor.com/steamspy-api

Basketball efficiency-stats maths as an API, computed locally and deterministically — the shooting-efficiency and box-score numbers an analyst, coach or sports app rates a performance by. The true-shooting endpoint folds twos, threes and free throws into one number: TS% = points ÷ (2 × (field-goal attempts + 0.44 × free-throw attempts)) × 100, where the 0.44 approximates how many possessions a free-throw trip really uses — 25 points on 18 field goals and 6 free throws is about 60.6 %, against a league average near 56–58 %. The effective-field-goal endpoint credits a three for being worth 50 % more than a two: eFG% = (field goals made + 0.5 × threes made) ÷ field-goal attempts × 100, so 9 makes including 3 threes on 18 attempts is 58.3 % versus a raw 50 %, the gap being the value of the long ball. The game-score endpoint computes John Hollinger's Game Score, a single-game productivity rating scaled like points — PTS + 0.4·FGM − 0.7·FGA − 0.4·(FTA−FTM) + 0.7·ORB + 0.3·DRB + STL + 0.7·AST + 0.7·BLK − 0.4·PF − TOV — where about 10 is an average game, 20+ excellent and 40+ historic, rewarding efficient scoring and all-round play while docking misses and turnovers. Everything is computed locally and deterministically, so it is instant and private. Ideal for basketball analytics and box-score tools, fantasy and commentary apps, and sports calculators. Pure local computation — no key, no third-party service, instant. 3 compute endpoints. For baseball stats use a baseball API; for cricket a cricket API.

api.oanor.com/basketball-api

Baseball sabermetrics as an API, computed locally and deterministically — turn raw counting numbers into the rate stats that actually rank players. The batting endpoint takes at-bats, hits, doubles, triples, home runs, walks, hit-by-pitch and sacrifice flies and returns the batting average (H/AB), on-base percentage ((H+BB+HBP)/(AB+BB+HBP+SF)), slugging percentage (total bases/AB), OPS (on-base plus slugging), isolated power (SLG−AVG) and, when strikeouts are supplied, BABIP — a classic .300/.366/.530 line comes straight out. The pitching endpoint takes innings pitched, earned runs, hits, walks, strikeouts and home runs and returns the earned run average (9·ER/IP), WHIP ((BB+H)/IP), strikeouts and walks per nine innings, the strikeout-to-walk ratio and FIP, the fielding-independent pitching estimator (13·HR + 3·(BB+HBP) − 2·K)/IP + constant. Innings pitched is a true decimal, with an exact "outs" input for the 6.1/6.2 box-score convention. Everything is computed locally and deterministically, so it is instant and private. Ideal for fantasy-baseball, sports-analytics, sabermetrics and box-score app developers, scouting and stat-line tools, and teaching material. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 2 compute endpoints. This computes the stats from your numbers; for live scores, standings, teams and players use a sports-data API.

api.oanor.com/baseball-api

Linear least-squares regression as an API, computed locally and deterministically. The linear endpoint fits the best straight line y = a + b·x through a set of x/y data points by ordinary least squares, returning the slope b = Σ((x−x̄)(y−ȳ))/Σ(x−x̄)², the intercept a = ȳ − b·x̄, the ready-to-use equation, the Pearson correlation r and the coefficient of determination R² (the fraction of variance the line explains), and the residual and slope standard errors — the points (1,2),(2,4),(3,5),(4,4),(5,5) fit to y = 2.2 + 0.6·x with R² = 0.6, and a perfectly linear set returns R² = 1. Pass a predict_x and it also extrapolates the fitted value at that point. The predict endpoint evaluates y = intercept + slope·x for a known line. The x and y lists may be given as comma-separated values (x=1,2,3&y=2,4,5) or as JSON arrays in a POST body and must be equal length. Everything is computed locally and deterministically, so it is instant and private. Ideal for data-science, analytics, BI, forecasting, machine-learning-preprocessing and statistics-education app developers, trend-line and best-fit tools, and dashboards. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 2 endpoints. This is the regression line; for the Pearson correlation alone or descriptive statistics use a statistics API and for probability distributions a probability API.

api.oanor.com/regression-api

Digital-marketing metrics maths as an API, computed locally and deterministically. The ads endpoint computes campaign KPIs from any two of the spend, impressions, clicks and conversions: the CPM (cost per thousand impressions), the CPC (cost per click), the CTR (click-through rate), the conversion rate and the CPA (cost per acquisition). The roas endpoint computes the return on ad spend, ROAS = revenue ÷ spend, the ROI percentage and the gross profit, and — given a gross margin — the break-even ROAS of 1 ÷ margin. The ltv endpoint computes the customer lifetime value, average order value × purchase frequency × lifespan × gross margin, and, with the marketing spend and number of new customers, the customer acquisition cost, the all-important LTV:CAC ratio and the CAC payback period in months. Everything is computed locally and deterministically, so it is instant and private. Ideal for marketing, advertising, e-commerce and growth app developers, campaign dashboards and reporting tools, and agency calculators. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is marketing-metrics maths; for percentage maths use a percentage API and for currency conversion use a currency API.

api.oanor.com/marketing-api

Marketing and advertising metrics as an API — the everyday campaign maths, computed locally and deterministically and entirely currency-agnostic. The funnel endpoint takes any of impressions, clicks, conversions, spend and revenue and computes every metric the inputs allow: click-through rate (CTR), cost per click (CPC), cost per mille (CPM), conversion rate, cost per acquisition (CPA), average order value, return on ad spend (ROAS), return on investment (ROI) and profit — anything not derivable is returned as null rather than guessed. The roas endpoint focuses on profitability: ROAS, ROI and profit, and — given a gross margin — the break-even ROAS and gross profit, with a profitable flag. The target endpoint reverse-plans a campaign: from a conversion or revenue goal and your known rates it works out the required clicks, impressions and budget and the expected revenue and ROAS. Everything is computed locally and deterministically, so it is instant and private. Rates such as conversion_rate and ctr are given as fractions (0.05 = 5%). Ideal for marketing dashboards and reporting, media-buying and bid tools, agency and campaign planners, and e-commerce analytics. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is advertising-metric maths; for loan and investment maths use a finance-calculator API.

api.oanor.com/admetrics-api

Run statistics on a list of numbers without a spreadsheet or a stats package. The describe endpoint returns a full summary of a dataset — count, sum, min, max, range, mean, median, mode, the first and third quartiles and interquartile range, population and sample variance and standard deviation, coefficient of variation, geometric and harmonic means, skewness and kurtosis. Get any percentile of a dataset, the Pearson correlation coefficient (and r²) between two equal-length series, and a simple linear regression (slope, intercept, r² and the line equation). Input is a raw array of numbers (JSON or a comma-separated list) — no CSV, no headers. Perfect for analytics, A/B test summaries, sensor and metrics data, dashboards and quick exploratory analysis. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 5 endpoints. Distinct from the mathjs expression engine and from CSV per-column summaries.

api.oanor.com/stats-api

Decentralized-finance analytics as an API, powered by DeFiLlama — the most-used, independent dashboard for tracking Total Value Locked (TVL) across the DeFi ecosystem. TVL is the dollar value of assets deposited in a protocol, the key measure of a DeFi protocol's size and health. This API wraps DeFiLlama's open data into clean, compact JSON. /v1/protocols ranks DeFi protocols by TVL and lets you filter by blockchain (chain=Ethereum) and by category (category=Lending, Dexes, Liquid Staking, CDP, Yield, Bridge and more) — each protocol with its slug, token symbol, category, the chains it runs on, its TVL in USD and 1-day and 7-day TVL change. /v1/protocol?slug=aave returns a single protocol's profile and its current TVL broken down by blockchain (real chains only, so the headline figure is not inflated by staking or borrowed aggregates). /v1/chains ranks every blockchain by the TVL deployed on it. /v1/stablecoins ranks stablecoins by circulating supply, with each coin's peg type and peg mechanism. All values are in US dollars and reflect the latest snapshot. Ideal for crypto and DeFi dashboards, portfolio and risk tools, market-research and analytics products, and Discord/Telegram bots. This is on-chain/DeFi analytics — distinct from token-price feeds. Use a protocol slug from /v1/protocols for the detail endpoint. Data from DeFiLlama (free and open).

api.oanor.com/defillama-api

Wikipedia pageview statistics as an API, live from the official Wikimedia REST API. See the most-viewed Wikipedia articles for any day — a real-time pulse of what the world is reading and searching for — with junk namespaces filtered out by default, and get the daily (or monthly) view counts and totals for any individual article over any date range. Works for any language edition (en.wikipedia, de.wikipedia, fr.wikipedia and 300+ projects) and any access method (desktop, mobile-web, mobile-app). Ideal for trend analysis, news, research, dashboards, SEO and content strategy. Public Wikimedia data.

api.oanor.com/pageviews-api

A fast, fully-local User-Agent parser: detect the browser (name and version), rendering engine, operating system (name and a friendly version), device type (desktop, mobile, tablet, TV, wearable or bot), a mobile flag, and bot/crawler identity (Googlebot, Bingbot, social-preview bots, GPTBot/ClaudeBot, curl and more). Bot detection is included on every plan. Pure server-side compute, no third-party upstream, so responses are instant and always available. Ideal for analytics, ad-tech, fraud and bot filtering, personalization and access logs.

api.oanor.com/useragent-api