Energy produced over time
API · /windpower-api
Wind Power API
healthy
3,758 Subscribers
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
API health
healthy- Uptime
- 100.00%
- Server probes · 24h
- Avg latency
- 74 ms
- Server probes · 24h
- Subscribers
- 3,758
- active
- Total calls
- 76
- last 7 days
Pricing
Pick a tier — billed monthly, cancel anytime.
Free
Free
- 12,935 calls / month
- 2 requests / second
- Hard cap (429 above quota, no overage)
- 12,935 calls/month
- 2 req/sec
- Power + energy + swept area
- No credit card
Starter
€14.45 /month
- 22,550 calls / month
- 8 requests / second
- Hard cap (429 above quota, no overage)
- 22.55k calls/month
- 8 req/sec
- Betz limit, ms/mph/knots
- Email support
Pro
€34.35 /month
- 275,500 calls / month
- 20 requests / second
- Hard cap (429 above quota, no overage)
- 275.5k calls/month
- 20 req/sec
- Renewable / engineering pipelines
- Priority support
Mega
€72.35 /month
- 1,420,000 calls / month
- 50 requests / second
- Hard cap (429 above quota, no overage)
- 1.42M calls/month
- 50 req/sec
- Platform scale
- Dedicated SLA
Built by
Related APIs
Other APIs with overlapping tags.
Wood Pellet API
Wood-pellet heating maths as an API, computed locally and deterministically — the consumption, heat-output and storage numbers a homeowner, installer or heating planner sizes a pellet system by. The consumption endpoint gives the pellets to meet a heat demand = the demand ÷ the usable heat per kilo, where usable = the calorific value × the boiler efficiency: ENplus wood pellets hold about 4.8 kWh/kg and a modern pellet boiler runs ~90 %, so each kilo delivers roughly 4.3 kWh — a 10,000 kWh annual demand then needs about 2.3 tonnes of pellets, around 154 fifteen-kilo bags or a bulk delivery. The heat-output endpoint inverts it: the usable heat from a mass = mass × calorific value × efficiency, so a tonne of ENplus pellets is about 4,800 kWh gross of which a 90 % boiler delivers ~4,320 kWh — the equivalent of roughly 480 litres of heating oil or 432 m³ of natural gas. The storage-volume endpoint sizes the hopper or silo: storage = the pellet mass ÷ the bulk (poured) density, about 650 kg/m³ for ENplus, so 2.3 tonnes fill roughly 3.6 m³ — size the store for the full delivery plus headroom for the fill pipe. Everything is computed locally and deterministically, so it is instant and private. Ideal for pellet-heating and installer tools, home-energy and quoting apps, and renewable-heat calculators. Pure local computation — no key, no third-party service, instant. Uses standard ENplus figures — set your own for a specific pellet grade. 3 compute endpoints. For cordwood use a firewood API; for propane/LPG a propane API.
api.oanor.com/pellet-api
Solar Row Spacing API
Solar-array row-spacing and shading geometry as an API, computed locally and deterministically — the shadow-length, inter-row-spacing and ground-coverage numbers a PV designer or installer lays a ground-mount or flat-roof array out with. The shadow-length endpoint gives the shadow an object casts = its height ÷ tan(sun elevation), longer the lower the sun (which is why layouts are designed for the worst-case winter-solstice low sun), stretched by 1/cos(azimuth difference) when the sun is off-axis. The row-spacing endpoint gives the minimum row pitch (front edge to front edge) to stop a row shading the one behind = the module's horizontal base (length × cos tilt) + the shadow its back edge casts (module height ÷ tan of the minimum sun elevation) — a 1.7 m module at 30° tilt clearing a 20° winter sun needs about a 3.8 m pitch — and returns the resulting ground coverage ratio. The ground-coverage endpoint gives that GCR = module length ÷ row pitch, the packing density: fixed-tilt fields typically run 0.4–0.5, higher packs more kW per acre but loses winter yield to mutual shading, lower wastes land. Everything is computed locally and deterministically, so it is instant and private. Ideal for solar-design and layout tools, EPC and site-assessment apps, and renewable-energy calculators. Pure local computation — no key, no third-party service, instant. Geometric model — use the real worst-hour sun altitude. 3 compute endpoints. For solar position/altitude use a solar-position API; for irradiance a solar API; for off-grid sizing an off-grid API.
api.oanor.com/pvspacing-api
Off-Grid Solar Sizing API
Off-grid solar system-sizing maths as an API, computed locally and deterministically — the battery-bank, solar-array and charge-controller numbers an RV, cabin, boat or off-grid homeowner sizes a system with. The battery-bank endpoint gives the storage you need = (daily load × days of autonomy) ÷ (depth of discharge × round-trip efficiency), then ÷ the system voltage for amp-hours: the autonomy carries you through cloudy days and the depth-of-discharge limit protects the cells (lead-acid ~50 %, lithium 80–100 %, which is why lithium banks run smaller), so a 2 kWh/day load at 12 V with 2 days autonomy, 50 % DoD and 85 % efficiency needs about 785 Ah. The array endpoint gives the panels = daily energy ÷ (peak sun hours × system efficiency), where peak sun hours is the day's irradiance as equivalent full-sun hours (~3–6 by place and season) and the efficiency rolls up controller, wiring, heat and dust losses — about 670 W for that load at 4 sun hours and 75 %. The charge-controller endpoint sizes the controller = array watts ÷ battery voltage × a 1.25 safety factor, so a 700 W array on a 12 V bank wants roughly an 80 A controller. Everything is computed locally and deterministically, so it is instant and private. Ideal for solar-installer and DIY tools, RV/marine/cabin power planners, and renewable-energy calculators. Pure local computation — no key, no third-party service, instant. Size for the worst month. 3 compute endpoints. For solar irradiance and sun hours use a solar API; for battery runtime under load a battery API.
api.oanor.com/offgrid-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.oanor.com/hydropower-api
Frequently asked questions
Quick answers about pricing, quotas, and integration.
How do I get an API key for Wind Power API?
Sign up for free at oanor.com, generate an API key from the developer dashboard, and call Wind Power API with the x-oanor-key header. No credit card needed for the free tier.
What's the rate limit for Wind Power API?
Free tier allows 1 request per second. Paid plans scale up to 50 requests per second on the Mega tier. Hard limits return HTTP 429 above the quota — no surprise overage charges.
How much does Wind Power API cost?
Wind Power API has a free tier with 100 calls / month. Paid plans start at €14.45 / month with higher quotas and faster rate limits.
Can I cancel my subscription anytime?
Yes. Plans are billed monthly and you can cancel anytime from your billing dashboard. No long-term contracts and no cancellation fee.
Is Wind Power API GDPR-compliant?
All requests to Wind Power API go through our EU-based gateway. Your upstream API key never leaves our server and no personal data is shared with the upstream provider beyond the request you send.
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/windpower-api/SOME_PATH \
-H "x-oanor-key: oanor_test_..."const res = await fetch("https://api.oanor.com/windpower-api/SOME_PATH", {
headers: { "x-oanor-key": "oanor_test_..." }
});
const data = await res.json();$ch = curl_init("https://api.oanor.com/windpower-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/windpower-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
📌 Pinned
🔒 Locked
·
·
·
-
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.