Annual energy
API · /hydropower-api
Hydropower 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 health
healthy- Uptime
- 100.00%
- Server probes · 24h
- Avg latency
- 89 ms
- Server probes · 24h
- Subscribers
- 3,555
- active
- Total calls
- 20
- last 7 days
Pricing
Pick a tier — billed monthly, cancel anytime.
Free
Free
- 2,400 calls / month
- 2 requests / second
- Hard cap (429 above quota, no overage)
- 2,400 calls/month
- 2 req/sec
- Power + sizing + annual energy
- No credit card
Starter
€9.00 /month
- 39,000 calls / month
- 6 requests / second
- Hard cap (429 above quota, no overage)
- 39,000 calls/month
- 6 req/sec
- Gross & net power, flow/head sizing
- Email support
Pro
€25.00 /month
- 265,000 calls / month
- 15 requests / second
- Hard cap (429 above quota, no overage)
- 265,000 calls/month
- 15 req/sec
- Feasibility & micro-hydro pipelines
- Priority support
Mega
€76.00 /month
- 1,750,000 calls / month
- 40 requests / second
- Hard cap (429 above quota, no overage)
- 1,750,000 calls/month
- 40 req/sec
- Platform scale
- Dedicated SLA
Built by
Related APIs
Other APIs with overlapping tags.
Wind Power 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
Solar Resource API
Solar irradiance and agroclimatology for any location on Earth — as an API over NASA POWER (Prediction Of Worldwide Energy Resources), derived from NASA satellite and reanalysis data. Get the solar resource needed to size and assess PV and CSP systems: global (GHI), direct-normal (DNI) and diffuse horizontal irradiance, clear-sky irradiance and the clearness index — either as long-term monthly climatology normals for quick site assessment, or as a daily time series for a date range (1981-present). The same call also serves meteorology — temperature, wind speed, relative humidity and precipitation — making it ideal for solar energy, agriculture, building-energy modelling and climate work. From cloudy Berlin to the Sahara, it turns a coordinate into bankable solar and climate data. A solar-resource / agroclimatology data source — distinct from PV-system energy simulation (PVGIS) and historical-weather records. Open data from NASA POWER.
api.oanor.com/solar-api
Solar PV (PVGIS) 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
Propane & LPG Tank 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
Frequently asked questions
Quick answers about pricing, quotas, and integration.
How do I get an API key for Hydropower API?
What's the rate limit for Hydropower API?
How much does Hydropower API cost?
Can I cancel my subscription anytime?
Is Hydropower API GDPR-compliant?
Pick an endpoint from the list on the left to see its details and try it.
Code snippets
Sign up to get an API key, then call any path under your slug.
curl https://api.oanor.com/hydropower-api/SOME_PATH \
-H "x-oanor-key: oanor_test_..."
const res = await fetch("https://api.oanor.com/hydropower-api/SOME_PATH", {
headers: { "x-oanor-key": "oanor_test_..." }
});
const data = await res.json();
$ch = curl_init("https://api.oanor.com/hydropower-api/SOME_PATH");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-oanor-key: oanor_test_..."]);
$response = curl_exec($ch);
import requests
r = requests.get(
"https://api.oanor.com/hydropower-api/SOME_PATH",
headers={"x-oanor-key": "oanor_test_..."},
)
print(r.json())
Ratings
Sign in to rate.
No reviews yet.
Discussion
Ask questions, share usage tips, get answers from the provider and other developers. Public — anyone can read.
Sign in to start a thread or reply.
Sign inNew thread
·
-
Provider answer
🔒 This thread is locked — no new replies.
-
·
- No threads yet — start the discussion.
Support
Private 1:1 support with the provider — billing questions, integration issues, account problems. Only you and the provider team can see these threads.
Sign in to open a support ticket.
Sign inOpen new ticket
Describe what you need help with. The provider team gets an email and replies on the ticket page.
-
·
Urgent - No tickets yet for this API.