#energy

Live continuous front-month (1!) quotes for the major liquid futures across every asset class, with no key: precious & base metals (gold, silver, copper, platinum), energy (WTI crude, natural gas, gasoline, heating oil), grains (wheat, corn, soybeans), softs (coffee, sugar, cocoa, cotton), livestock, equity-index (E-mini S&P 500, Nasdaq, Dow, Russell), interest-rate (2/5/10/30-year Treasuries) and FX futures from COMEX, NYMEX, CBOT, CME, CME_MINI and ICE US. Get a per-contract quote by short code (GC, CL, ES, ZW) with last price, % change and intraday OHLC, a full cross-asset board, or a per-category cut — a curated board of the contracts that actually trade.

api.oanor.com/cmefutures-api

What is moving across the commodity complex right now, computed live from Yahoo Finance futures (no key, nothing stored). Just as stock, FX and crypto traders watch the day's biggest gainers and losers, commodity traders want the same board for energy, metals, grains, softs and livestock. For every commodity this measures the change on the day, the week and the month, the day's high and low, the 52-week high and low and where the price sits in that 52-week range. The movers endpoint returns the whole complex ranked by daily change — the top gainers and losers — plus the weekly and monthly leaders, and can be filtered to one sector. The commodity endpoint returns one commodity's full performance card. The commodities endpoint lists what is covered. The commodity movers / performance-board cut — distinct from the commodity-momentum API (which ranks by a blended multi-month momentum factor and trend regime), the commodity-price feed, the commodity-spreads and the seasonality APIs. It answers what moved today, across the complex.

api.oanor.com/commoditymovers-api

The calendar patterns commodity traders position around, computed live from ~10 years of Yahoo Finance monthly futures data (no key, nothing stored). Commodities are the most seasonal market there is: natural gas tends to rally into winter heating demand, gasoline into the summer driving season, grains around the planting and harvest calendar. This measures it directly — for each commodity it takes a decade of monthly returns, groups them by calendar month, and returns the average return in each of the twelve months, the share of years that month was positive (the win rate), and the historically strongest and weakest months. The seasonality endpoint returns one commodity's full 12-month seasonal profile plus the current month's historical bias. The month endpoint flips it around: for a given calendar month it ranks every commodity by its historical average return, so you can see what is seasonally bullish or bearish right now. The commodities endpoint lists what is covered. The commodity-seasonality / calendar-pattern cut — distinct from the FX-seasonality API (currencies), the commodity-price feed, the commodity-spreads and the commodity-momentum APIs. It answers what a commodity usually does this month, not what it costs today.

api.oanor.com/commodityseasonality-api

Which corner of the commodity complex is leading and which is lagging, ranked by trailing momentum, computed live from Yahoo Finance futures (no key, nothing stored). A price tells you where a commodity is; momentum tells you where the money is flowing. This scores every major commodity — crude, Brent, natural gas, gasoline and heating oil in energy; gold, silver, copper, platinum and palladium in metals; corn, wheat and soybeans in grains; coffee, sugar, cocoa, cotton and orange juice in softs; live cattle and lean hogs in livestock — by its return over five horizons (1 week, 1 month, 3 months, 6 months and a ~1-year proxy), blends them into a single momentum score and ranks the whole complex into leaders and laggards. The screener endpoint returns that ranked table with a relative-strength rank and trend regime for each. The momentum endpoint drills into one commodity: its multi-horizon returns, where it sits versus its 50- and 200-day averages, and a trend label. The commodities endpoint lists what is covered. The cross-commodity momentum / relative-strength factor cut — distinct from the commodity-price feed (front-month prices), the commodity-spreads API (crack/crush/ratios) and the precious-metals spot API. It answers what is leading the complex, not what one thing costs.

api.oanor.com/commoditymomentum-api

Live European wholesale (day-ahead) electricity prices and the live power-generation mix, from the Fraunhofer ISE Energy-Charts public data. Electricity is one of Europe's largest traded commodities: each bidding zone (Germany, France, the Nordics, Iberia, Italy …) clears a day-ahead auction priced in EUR/MWh, and the resulting curve drives industrial costs and energy-stock moves. The price endpoint returns a zone's day-ahead price right now plus the day's min/max/average; the prices endpoint returns the full hourly day-ahead curve; the zones endpoint lists the supported bidding zones; the power endpoint returns a country's current generation mix by source with the renewable share. Read live, nothing stored. This is Europe's own wholesale-electricity price and generation layer — distinct from fuel/metal commodity feeds and from FX or equity APIs.

api.oanor.com/electricity-api

Live commodity futures prices as an API — the energy, grain, soft and livestock commodity complex, served from Yahoo Finance. For any commodity it returns the front-month futures price, the previous close, the absolute and percentage change on the day, the day's high and low and the 52-week high and low, with the price's currency and quoting unit (e.g. USD per barrel, US cents per bushel). Look a commodity up by name or alias (crude oil, Brent, natural gas, gasoline, corn, wheat, soybeans, coffee, sugar, cocoa, cotton, orange juice, live cattle, lean hogs and more), pull a category board (energy, grains, softs, livestock) ranked by the day's move, or get the whole board in one call. The commodity-quote layer for trading, markets and dashboard apps. Live, no key. Distinct from the precious-metals API — this is the energy, agricultural and soft-commodity complex.

api.oanor.com/commodities-api

Live on-chain data for Energy Web Chain — an EVM Layer 1 for energy-sector decentralised applications — via its public Blockscout explorer (no wallet, no key). The stats endpoint returns chain-wide totals (blocks, transactions, addresses, average block time, gas used); gas gives the current gas-price oracle (slow/average/fast). Blocks lists the latest blocks, and a single block resolves by height or by hash with its transaction count, gas, validator and timestamp. The address endpoint returns any account's EWT balance, nonce, contract flag and token holdings; transaction resolves a tx by hash with its from/to, value in EWT, fee, status and block. The token endpoint returns an ERC-20 token's metadata (name, symbol, decimals, total supply, holders) by contract address, and search runs a universal lookup across addresses, tokens, blocks and transactions. Gas, balances, values and fees are denominated in EWT, the native coin. Real on-chain data straight from the explorer, refreshed every call — no key. 9 endpoints. For multi-chain coverage combine with the other oanor chain APIs (Ethereum, Base, Arbitrum and more).

api.oanor.com/energyweb-api

Battery-pack design maths as an API, computed locally and deterministically — the voltage, capacity, energy, current and charge-time numbers an EV, e-bike, solar or robotics pack builder lays out a battery with. The configuration endpoint turns a series-parallel cell layout into the pack: cells in series add their voltages (the series count sets the pack voltage) and cells in parallel add their amp-hours (the parallel count sets the capacity), with the energy in watt-hours = voltage × capacity — a 13S4P pack of 3.6 V / 3.5 Ah cells is 46.8 V, 14 Ah and about 655 Wh from 52 cells, and it also reports the full-charge voltage (series × 4.2 V for Li-ion) to size the charger and BMS. The c-rate endpoint relates current to capacity both ways — give a C-rate to get the current, or a current to get the C-rate — because 1C draws or charges the whole capacity in an hour, so a 14 Ah pack at 2C is 28 A, and it returns the power if you pass the pack voltage. The charge-time endpoint gives the time to charge between two states of charge from the charge current. Everything is computed locally and deterministically, so it is instant and private. Ideal for EV and e-bike builders, solar and off-grid storage tools, robotics and drone packs, and battery-engineering apps. Pure local computation — no key, no third-party service, instant. Pack-design estimates — real cells taper on charge and sag under load. 3 compute endpoints. For runtime under a load use a battery API; for EV charging an EV-charging API.

api.oanor.com/batterypack-api

Heat-pump and refrigeration performance maths as an API, computed locally and deterministically — the efficiency numbers an HVAC engineer, energy auditor or heat-pump installer actually works with. The cop endpoint gives the coefficient of performance and the US EER rating from the thermal capacity and the electrical power: a unit moving 7 kW of heat on 2 kW of electricity has a COP of 3.5 (an EER of 12), meaning 3.5 units of heating or cooling for every unit of electricity — which is why a heat pump beats resistance heating, where the COP is exactly 1. The carnot endpoint gives the unbeatable ideal limit set only by the absolute temperatures — heating = Th ÷ (Th − Tc), cooling = Tc ÷ (Th − Tc) in kelvin, where heating COP always equals cooling COP plus one — and, given a real COP, the second-law efficiency that says how close the machine runs to that ceiling; the smaller the temperature lift, the higher the limit, which is why ground-source and low-temperature systems beat air-source on a cold day. The capacity endpoint turns electrical power and a COP into the delivered heating or cooling in kilowatts, BTU per hour and tons of refrigeration — the extra energy over the electricity is pulled from the outside air, ground or water. Everything is computed locally and deterministically, so it is instant and private. Ideal for HVAC and refrigeration engineers, energy auditors, heat-pump and building-performance tools, and sustainability dashboards. Pure local computation — no key, no third-party service, instant. Estimates at the stated conditions — real COP falls as the temperature lift rises. 3 compute endpoints. For room sizing use an HVAC BTU API; for moist-air properties use a psychrometric API.

api.oanor.com/heatpump-api

Steam-boiler engineering maths as an API, computed locally and deterministically — the three numbers a boiler operator, plant engineer or steam-system designer actually works with. The boiler-hp endpoint converts a required heat output into boiler horsepower (heat ÷ 33,475 BTU/hr, the standard definition), the equivalent steam output in pounds per hour "from and at" 212 °F (34.5 lb/hr per BHP) and the output in kilowatts — a 1,000,000 BTU/hr load is about 29.9 BHP or 1,031 lb/hr of steam. The factor-of-evaporation endpoint gives the real capacity for your feedwater: the factor = (the total heat of the steam − the feedwater heat) ÷ 970.3, always greater than one because the boiler must add the sensible heat to bring water up to boiling, so a boiler rated "from and at" 212 °F actually makes less with 60 °F feedwater — which is exactly why preheating feedwater with an economiser raises capacity and saves fuel. The blowdown endpoint gives the continuous blowdown rate to hold the boiler water within its dissolved-solids limit: blowdown = steam × feedwater TDS ÷ (boiler limit − feedwater TDS), with the cycles of concentration and the blowdown as a percentage of feedwater — better feedwater means more cycles, less blowdown and less wasted hot water. Everything is computed locally and deterministically, so it is instant and private. Ideal for boiler operators, steam-plant and HVAC engineers, energy auditors, water-treatment specialists and process-engineering tools. Pure local computation — no key, no third-party service, instant. Engineering estimates — verify against the manufacturer data and local code. 3 compute endpoints. For moist-air properties use a psychrometric API; for compressed air use a compressor API.

api.oanor.com/boiler-api

Electric-vehicle charging maths as an API, computed locally and deterministically — the three numbers every EV driver and charging app actually needs. The charge-time endpoint gives how long a session takes: from the battery size and the gap between the starting and target state of charge it works out the energy to add and the time at a given charger power and efficiency — a 60 kWh battery from 20 % to 80 % on a 7.2 kW home charger at 90 % efficiency takes about 5.6 hours, and it reminds you that DC fast charging slows sharply above 80 % so road trips should be planned around the fast part of the curve. The range-added endpoint turns a charging session into miles: from the charger power, the minutes plugged in and the car's miles per kWh it gives the energy and range added, plus the handy "miles per hour of charging" figure — a 7 kW home charger adds roughly 22 mi/hr, a 150 kW DC station hundreds. The cost endpoint gives what a charge costs, correctly billing the energy drawn from the grid (the energy to the battery divided by the charging efficiency) times the price per kWh, with the effective cost per usable kWh — home overnight rates make EV miles very cheap while DC fast chargers cost several times more. Everything is computed locally and deterministically, so it is instant and private. Ideal for EV apps, route and trip planners, fleet and charging-station tools, charge-cost calculators and dashboards. Pure local computation — no key, no third-party service, instant. Estimates — real DC charging tapers above 80 % and cold weather cuts range. 3 compute endpoints. For battery runtime use a battery API; for generic energy cost use an energy-cost API.

api.oanor.com/evcharging-api

Solar-thermal (solar hot water) maths as an API, computed locally and deterministically — the collector, sizing and storage numbers a solar installer or homeowner designs a hot-water system with. The output endpoint gives the useful daily heat a collector makes: area × the daily solar energy on it × the collector efficiency (flat-plate ~40–60 %, evacuated tubes higher), so a 40 ft² collector under 1,800 BTU/ft²/day at 50 % delivers about 36,000 BTU (10.5 kWh) — a family's hot water on a good day. The area endpoint sizes the collector for a demand: area = (daily gallons × 8.34 × the temperature rise) ÷ (irradiance × efficiency), so 60 gallons raised 70 °F needs about 39 ft² — sized for an average day with a backup heater, since a 60–80 % solar fraction is the economic sweet spot. The tank endpoint sizes solar storage at about 1.5 gallons per square foot of collector, big enough to bank a sunny afternoon without stalling the collector. Everything is computed locally and deterministically, so it is instant and private. Ideal for solar-installer and renewable-energy apps, hot-water-system design tools, home-energy calculators, and sustainability sites. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 compute endpoints. For the local solar resource use a solar-irradiance API; for pool heating use a pool API.

api.oanor.com/solarthermal-api

Pipe-insulation heat-loss maths as an API, computed locally and deterministically — the radial heat loss, thickness and energy-cost numbers a mechanical engineer or energy auditor sizes lagging with. The heat-loss endpoint gives the loss per linear foot through cylindrical insulation, Q/L = 2π·(k/12)·ΔT ÷ ln(r2/r1), where k is the insulation conductivity (BTU·in/hr·ft²·°F, ~0.25 for fibreglass), r1 the pipe radius and r2 the outer radius — a 2-inch line at 300 °F with one inch of fibreglass loses about 43 BTU/hr per foot, and because the relationship is logarithmic, doubling the thickness does not halve the loss. The thickness endpoint inverts it for a target loss: ln(r2/r1) = 2π·(k/12)·ΔT ÷ target, then thickness = r2 − r1, showing the economic-thickness point beyond which more material rarely pays. The annual-cost endpoint turns loss per foot into the yearly heat lost and fuel cost over a run of pipe, the number that justifies the lagging. Everything is computed locally and deterministically, so it is instant and private. Ideal for mechanical-design and energy-audit apps, insulation-contractor and process-piping tools, building-services calculators, and engineering aids. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 compute endpoints. Ignores the outer air film (real loss slightly lower). For flat walls and roofs use a U-value API.

api.oanor.com/pipeinsulation-api

Propane and LPG tank maths as an API, computed locally and deterministically — the usable-fill, energy and burn-time numbers a homeowner, RV-er, grill-master or HVAC tech works out at the tank. The tank endpoint turns a tank size into real numbers: liquid propane is 4.24 lb per gallon and holds 91,452 BTU per gallon (about 21,569 BTU per pound), so a 20 lb barbecue cylinder carries roughly 4.7 gallons and 431,000 BTU. It knows the two ways tanks are sized — a portable cylinder (20, 30, 40 lb) is rated by the propane weight it holds, while a bulk tank (100, 250, 500, 1000 gal) is filled to only 80 % of its water capacity to leave room for expansion, so a 500-gallon tank actually holds 400 gallons of propane and about 36.6 million BTU. The burntime endpoint divides that energy by an appliance’s BTU-per-hour input rating to give run time: that same 20 lb cylinder runs a 30,000 BTU/hr patio heater about 14 hours, and an optional hours-per-day turns it into days. The refill endpoint costs a fill from a price per gallon, gives the cost per 100,000 BTU so you can compare propane to natural gas or electricity, and — with an appliance rating — the running cost per hour. Everything is computed locally and deterministically, so it is instant and private. Ideal for home-energy, HVAC, RV, off-grid, grilling and outdoor-living app developers, fuel-cost and tank-monitor tools, and propane-delivery calculators. Pure local computation — no key, no third-party service, instant. US units. Live, nothing stored. 3 compute endpoints. For vehicle fuel economy or the ideal gas law use a different API.

api.oanor.com/propane-api

Hydroelectric-power engineering maths as an API, computed locally and deterministically. The power endpoint computes the electrical power a hydro plant generates with P = ρ·g·Q·H·η, from the water flow rate, the net head (the effective drop), the overall turbine-generator efficiency (typically 0.80–0.92) and the water density, returning both the gross power at 100 % efficiency and the net electrical output. The sizing endpoint inverts the relation to size a scheme — given a target power it solves the flow rate needed at a known head, or the head needed at a known flow, Q = P/(ρ·g·H·η). The annual-energy endpoint computes the yearly energy from the rated power and a capacity factor (typically 0.3–0.6 for hydro, accounting for water availability and downtime), E = P × 8760 h × capacity factor, and an optional revenue from an electricity price. Flow is in cubic metres per second, head in metres, efficiency 0–1, power in watts, kilowatts and megawatts. Everything is computed locally and deterministically, so it is instant and private. Ideal for renewable-energy, micro-hydro, civil-engineering, feasibility and sustainability app developers, run-of-river and reservoir tools, and energy education. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is hydroelectric generation; for wind-turbine power use a wind-power API, for solar resource a solar API and for pump (energy-consuming) duty a pump API.

api.oanor.com/hydropower-api

Capacitor maths as an API, computed locally and deterministically. The energy endpoint computes the stored energy and charge of a capacitor from any two of the capacitance, the voltage and the charge — E = ½CV² = ½QV and Q = CV — in joules, millijoules and coulombs. The charging endpoint models the RC charging and discharging transient: the time constant τ = RC, the voltage at a given time, V(t) = Vs(1 − e^(−t/RC)) when charging or V(t) = V₀·e^(−t/RC) when discharging, and the percent charged, or — given a target voltage — the time to reach it; a capacitor reaches about 63 % of the way in one time constant and over 99 % in five. The combination endpoint computes the total capacitance of capacitors in series (1/C = Σ1/Cᵢ) or parallel (C = ΣCᵢ). Capacitance accepts farads or the handy µF/nF/pF units. Everything is computed locally and deterministically, so it is instant and private. Ideal for electronics, maker, embedded and circuit-design app developers, power-supply and timing tools, and electronics education. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is capacitor maths; for AC reactance and resonance use a resonance API and for LED resistor sizing an LED-resistor API.

api.oanor.com/capacitor-api

Building-fabric thermal maths — U-value, R-value and heat loss — as an API, computed locally and deterministically. The rvalue endpoint takes a wall, roof or floor build-up as a list of layers (each given as a thickness and a thermal conductivity, or a thickness and a named material from a built-in table, or a direct R-value) and adds the interior and exterior surface resistances to return the total thermal resistance R = Rsi + ΣR_layer + Rse and the thermal transmittance U = 1/R, in both metric (RSI, m²K/W and W/m²K) and imperial (R-value) units, with a per-layer breakdown. The layer endpoint gives the R-value of a single material from its thickness and conductivity, R = thickness/conductivity, and solves for whichever of the three you leave out, with conductivities for concrete, brick, timber, plasterboard, mineral wool, EPS, XPS, PIR and more. The heatloss endpoint computes the steady-state heat loss through an element, Q = U·A·ΔT, in watts, BTU per hour and kWh per day from a U-value (or R-value), an area and a temperature difference (direct or as indoor minus outdoor), and an annual figure from heating degree days. Everything is computed locally and deterministically, so it is instant and private. Ideal for building-energy and retrofit tools, architecture and construction apps, insulation and SAP/Passivhaus calculators, and energy-assessment software. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is building-fabric thermal performance; for rule-of-thumb HVAC equipment sizing use an HVAC API.

api.oanor.com/uvalue-api

Wind-turbine power maths as an API, computed locally and deterministically. The power endpoint applies the wind-power equation P = ½ · ρ · A · v³ · Cp: from the wind speed, the rotor (given as swept area, diameter or blade length) and an optional air density and power coefficient, it returns the total power in the wind, the Betz maximum (the theoretical 16/27 ≈ 59.3 % limit) and the power actually extracted at the chosen coefficient — in watts, kilowatts, megawatts and horsepower. The energy endpoint multiplies power by time and an optional capacity factor to give the energy produced in watt-, kilowatt- and megawatt-hours, taking the power directly or deriving it from the wind and rotor. The sweptarea endpoint is a geometry helper: swept area from a diameter, radius or blade length, plus the blade-tip speed and tip-speed ratio from an rpm. Wind speed accepts metres per second, km/h, mph or knots; air density defaults to 1.225 kg/m³ at sea level. Because power scales with the cube of wind speed and the square of rotor diameter, small changes move it a lot — the API shows every intermediate value. Everything is computed locally and deterministically, so it is instant and private. Ideal for renewable-energy and engineering tools, education and physics apps, site-assessment and feasibility calculators, and STEM projects. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is wind-turbine power physics; for the Beaufort wind scale use a wind-scale API and for solar arrays use a solar API.

api.oanor.com/windpower-api

Electricity cost maths as an API, computed locally and deterministically and entirely currency-agnostic. The cost endpoint works out an appliance's energy use and running cost from its power (watts or kilowatts), the hours used per day and a per-kilowatt-hour tariff — returning the kilowatt-hours and the cost per day, week, month and year, with an optional quantity of identical devices. The compare endpoint pits two appliances against each other: it computes each one's annual energy cost, the saving from the more efficient one, and — given the extra purchase price of the better model — the payback period in years and months. The convert endpoint relates watts, hours and kilowatt-hours: give any two and it returns the third, plus the cost at a tariff. Everything is computed locally and deterministically, so it is instant and private. Kilowatt-hours equal power in kilowatts times hours, and cost equals kilowatt-hours times the rate; months use 365/12 days. Ideal for energy-saving and smart-home apps, appliance comparison and retail tools, sustainability dashboards, and budgeting software. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is energy-cost maths; for battery capacity and runtime use a battery API.

api.oanor.com/energycost-api

Great Britain\x27s electricity grid carbon intensity as an API, from the official National Grid ESO Carbon Intensity service. Get the live national carbon intensity in grams of CO2 per kWh with its index (very low to very high), the current generation mix showing exactly how much of the grid is gas, wind, solar, nuclear, biomass, hydro, coal and imports right now (with the renewable and zero-carbon percentages worked out for you), today\x27s half-hourly intensity timeline, the carbon intensity of all 18 GB regions, the intensity and fuel mix for any UK postcode, and the gCO2/kWh emission factor of each fuel type. This is exactly the data you need to shift EV charging, heat pumps, laundry and batteries to the greenest, cheapest half-hours. Perfect for smart-home and energy apps, EV-charging schedulers, sustainability dashboards, carbon-aware computing and climate tools. Covers Great Britain. No accounts, no upstream key.

api.oanor.com/carbonintensity-api

Solar photovoltaic potential for any location on Earth, powered by the EU JRC PVGIS (Photovoltaic Geographical Information System). Estimate how much energy a solar PV system would produce at a given coordinate — yearly and month-by-month output in kWh, the in-plane solar irradiation and a breakdown of system losses (angle-of-incidence, spectral, temperature) — for any panel size, fixed tilt and azimuth; find the optimal panel tilt and orientation that maximises annual output; and read the long-term monthly global horizontal solar irradiation. Covers most of the world (excluding polar and open-ocean areas) from years of satellite-based solar data. Ideal for solar installers and calculators, renewable-energy planning, home-energy and roof-potential tools, and climate / sustainability apps. Open data from EU JRC PVGIS.

api.oanor.com/pvgis-api

The WRI Global Power Plant Database as an API — 34,900+ power stations across 167 countries (~5,700 GW total capacity). Look up any plant by its WRI/GPPD id (e.g. WRI1000452 → Three Gorges Dam, 22,500 MW hydro); search by name, country, fuel type or capacity range; or find every power station within a radius of any coordinate (great-circle distance, optional fuel filter). Each record carries the installed capacity (MW), primary fuel (Solar, Hydro, Wind, Gas, Coal, Nuclear, …), country, latitude/longitude, commissioning year and owner. Ideal for energy dashboards, ESG/climate analytics, grid and infrastructure tools.

api.oanor.com/powerplants-api