API · /radiant-api

Radiant Floor API

healthy 3,688 Subscribers

Radiant-floor and hydronic heating maths as an API, computed locally and deterministically — the output, tubing and flow numbers an installer or DIYer designs a warm floor with. The output endpoint gives the heat a warm floor puts out: about 2 BTU/hr per square foot for every °F the floor surface is above the room, so an 85 °F floor in a 70 °F room delivers roughly 30 BTU/hr/ft² — about 9,000 BTU/hr over 300 ft², the comfort ceiling since the floor is held at ~85 °F. The tubing endpoint gives the tube and loops for an area at a spacing: field tubing = area × 12 ÷ spacing, so 300 ft² at 9-inch spacing needs 400 feet of tube, split into loops kept under ~300 feet (two 200-foot loops) so the pump can push them. The flow endpoint gives the loop flow rate for a heat load, GPM = load ÷ (500 × ΔT) where 500 is water's constant and ΔT is the supply-to-return drop — 9,000 BTU/hr at a 20 °F ΔT wants 0.9 GPM. Everything is computed locally and deterministically, so it is instant and private. Ideal for radiant-heating and plumbing apps, hydronic-design and PEX-layout tools, HVAC contractor calculators, and DIY-build sites. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 compute endpoints. Estimates — verify with a full heat-loss calc. For building load use an HVAC API; for pipe velocity use a flow-rate API.

#radiant #hydronic #heating #hvac #plumbing #developer-tools

api.oanor.com/radiant-api

Get an API key Try in playground → Contact provider

Machine-readable spec so AI agents can integrate this API.

/api/radiant-api/openapi.json

/api/radiant-api/llms.txt

Discovery: GET /api/index.json lists every API.

API health

healthy

Uptime: 100.00%; Server probes · 24h
Avg latency: 86 ms; Server probes · 24h
Subscribers: 3,688; active
Total calls: 0; last 7 days

Full status page → · 4 probes/24h

Pricing

Pick a tier — billed monthly, cancel anytime.

Free

470 calls / month
2 requests / second
Hard cap (429 above quota, no overage)
470 calls/month
2 req/sec
Output + tubing + flow
No credit card

Starter

€5.65 /month

12,700 calls / month
6 requests / second
Hard cap (429 above quota, no overage)
12,700 calls/month
6 req/sec
Loop layout & GPM
Email support

Pro

€17.40 /month

80,500 calls / month
15 requests / second
Hard cap (429 above quota, no overage)
80,500 calls/month
15 req/sec
Design & layout pipelines
Priority support

Mega

€52.20 /month

262,000 calls / month
36 requests / second
Hard cap (429 above quota, no overage)
262,000 calls/month
36 req/sec
Platform scale
Dedicated SLA

Built by

PremiumApi

Related APIs

Other APIs with overlapping tags.

Pool Heating API

Swimming-pool and spa heating maths as an API, computed locally and deterministically — the thermodynamics a pool owner, builder or service tech sizes a heater and budgets a heat-up with. The heat-time endpoint gives the hours to warm a body of water: energy = gallons × 8.34 lb/gal × the temperature rise in °F (that many BTU), divided by the heater's BTU/hr output — raising 20,000 gallons by 10 °F is 1,668,000 BTU, about 4.2 hours on a 400,000 BTU/hr gas heater before surface losses. The heater-size endpoint inverts it: the output you need to hit a temperature rise within a target time, so the same job in 24 hours wants only about 69,500 BTU/hr. The heat-pump endpoint gives a heat pump's electricity and cost — kWh = thermal BTU ÷ 3412 ÷ the COP (5–6 for pool units in mild weather) — so that 1,668,000 BTU costs about 89 kWh at a COP of 5.5, a fraction of resistance heat. Pass the temperature rise directly, or a current and target temperature. Everything is computed locally and deterministically, so it is instant and private. Ideal for pool-builder and service apps, heater-sizing and quote tools, spa and hot-tub calculators, and energy-comparison sites. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 compute endpoints. Ideal figures — add for surface and wind losses. For pool chemistry use a pool-chemistry API.

api.oanor.com/poolheat-api

Degree Day API

Heating and cooling degree-day maths as an API, computed locally and deterministically. The daily endpoint computes the heating degree days, HDD = max(0, base − mean), and the cooling degree days, CDD = max(0, mean − base), for a single day from a base temperature and the daily mean — or the minimum and maximum, since the mean is taken as their average. The period endpoint sums the degree days over a list of daily temperatures (means or min/max pairs), returning the total HDD and CDD, the count of heating and cooling days and the average temperature — the standard way to characterise a heating or cooling season. The energy endpoint turns degree days into an energy estimate: the heat delivered is UA·DD·24/1000 kWh from the building heat-loss coefficient, the fuel or electricity input is that divided by the boiler efficiency (or a heat-pump COP), and — with an energy price — the cost. Everything is computed locally and deterministically, so it is instant and private. Ideal for building-energy, HVAC and facilities tools, heating-bill and fuel-budget estimation, weather-normalisation and energy-benchmarking apps, and engineering education. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is degree-day demand estimation; for U-value and heat-loss fabric calculations use a U-value API.

api.oanor.com/degreeday-api

HVAC BTU Calculator API

HVAC sizing maths as an API, computed locally and deterministically from standard rule-of-thumb factors. The cooling endpoint estimates the air-conditioner load for a room — in BTU per hour, tons of cooling and kilowatts — from the floor area (in square feet or metres, or length × width) using a baseline of about 20 BTU/h per square foot, with adjustments for the number of occupants, a kitchen, sun exposure and ceiling height. The heating endpoint estimates the heating load from the area and a climate zone (mild through very cold) or a custom BTU per square foot. The convert endpoint converts between BTU per hour, tons of cooling, kilowatts and watts (one ton = 12,000 BTU/h ≈ 3.517 kW). Everything is computed locally and deterministically, so it is instant and private. These are rule-of-thumb estimates in the EnergyStar style — a proper Manual J load calculation accounting for insulation, windows and local climate is recommended for a real installation. Ideal for HVAC and home-improvement tools, air-conditioner and heater sizing guides, smart-home and energy apps, and contractor quoting. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is HVAC sizing; for appliance running cost use an energy-cost API.

api.oanor.com/hvac-api

Firewood Calculator API

Firewood maths as an API, computed locally and deterministically. The volume endpoint turns a wood-stack's length, height and depth (in feet or metres) into its volume in cubic feet and cubic metres, full cords, face cords and steres — a full cord being 128 cubic feet (a 4×4×8 ft stack) and a face cord being an 8×4 ft stack by the piece (log) length. The convert endpoint converts a quantity between cords, face cords, steres, cubic metres and cubic feet, using the piece length for the face-cord relationship. The heat endpoint estimates the heating value of a number of cords by wood species — returning the millions of BTU and the equivalent gallons of heating oil, therms of natural gas and kilowatt-hours — from a built-in table of typical seasoned-wood values (oak, hickory, maple, ash, birch, pine and more) or a custom figure. Everything is computed locally and deterministically, so it is instant and private. Heat values are typical seasoned figures (around 20% moisture) and vary with species, dryness and stove efficiency. Ideal for firewood sellers and delivery tools, heating and homestead apps, and forestry and woodlot calculators. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is firewood volume and energy; for general volume or unit conversion use a unit-conversion API.

api.oanor.com/firewood-api

Frequently asked questions

Quick answers about pricing, quotas, and integration.

How do I get an API key for Radiant Floor API?

Sign up for free at oanor.com, generate an API key from the developer dashboard, and call Radiant Floor API with the x-oanor-key header. No credit card needed for the free tier.

What's the rate limit for Radiant Floor 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 Radiant Floor API cost?

Radiant Floor API has a free tier with 100 calls / month. Paid plans start at €5.65 / 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 Radiant Floor API GDPR-compliant?

All requests to Radiant Floor 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.

Radiant 3

Meta 1

Pick an endpoint from the list on the left to see its details and try it.

GET /v1/flow

Loop flow rate

Playground

Parameters

Custom headers

Language: Client:

GET /v1/output

Floor heat output

Playground

Parameters

Custom headers

Language: Client:

GET /v1/tubing

Tubing and loops

Playground

Parameters

Custom headers

Language: Client:

GET /v1/meta

Spec

Playground

Custom headers

Language: Client:

Code snippets

curl https://api.oanor.com/radiant-api/SOME_PATH \
  -H "x-oanor-key: oanor_test_..."

const res = await fetch("https://api.oanor.com/radiant-api/SOME_PATH", {
  headers: { "x-oanor-key": "oanor_test_..." }
});
const data = await res.json();

$ch = curl_init("https://api.oanor.com/radiant-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/radiant-api/SOME_PATH",
    headers={"x-oanor-key": "oanor_test_..."},
)
print(r.json())

Ratings

No reviews yet.

Discussion

Ask questions, share usage tips, get answers from the provider and other developers. Public — anyone can read.

New thread

📌 Pinned 🔒 Locked

· ·

🔒 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.

Open new ticket

Describe what you need help with. The provider team gets an email and replies on the ticket page.

No tickets yet for this API.

Subscription active — calls can start immediately.

Send your first request —

Subscription active — copy a snippet and fire off your first call.

Pick a key

Plaintext is shown once at creation — use the prefix as a reminder.

Radiant Floor API

API health

Pricing

Built by

Related APIs

Pool Heating API

Degree Day API

HVAC BTU Calculator API

Firewood Calculator API

Frequently asked questions

Parameters

Parameters

Parameters

Code snippets

Ratings

Discussion

New thread

📌 🔒

Support

Open new ticket

Your cookie choices