Cv / Kv / Av conversion
API · /valveflow-api
Valve Flow Coefficient API
Control-valve flow-coefficient (Cv / Kv) maths as an API, computed locally and deterministically. The liquid endpoint sizes a control valve for liquid service using Q = Kv·√(ΔP/SG): give any two of the flow rate (m³/h), the pressure drop across the valve (bar) and the flow coefficient Kv, and it returns the third — the required Kv to size a valve, the flow a valve passes, or the pressure drop it develops — together with the equivalent Cv. The convert endpoint converts between the three flow coefficients in use around the world: the metric Kv, the US Cv = 1.156·Kv, and the SI Av = 2.4e-5·Cv. The opening endpoint computes how far a valve must open to pass an operating Kv against its rated Kvs, for both a linear trim (opening = Kv/Kvs) and an equal-percentage trim (opening = 1 + ln(Kv/Kvs)/ln(R) for a rangeability R), so you can keep the valve in its controllable 20–80 % travel band. Everything is computed locally and deterministically, so it is instant and private. Ideal for process, instrumentation and HVAC engineering tools, control-valve selection and commissioning, hydronic-balancing and plant-design apps, and engineering education. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is control-valve sizing; for pump power and head use a pump API and for orifice-plate metering use an orifice API.
API health
healthy- Uptime
- 100.00%
- Server probes · 24h
- Avg latency
- 84 ms
- Server probes · 24h
- Subscribers
- 4,052
- active
- Total calls
- 32
- last 7 days
Pricing
Pick a tier — billed monthly, cancel anytime.
Free
Free
- 2,000 calls / month
- 2 requests / second
- Hard cap (429 above quota, no overage)
- Liquid-service Cv/Kv sizing
- Deterministic ISA/IEC-60534 maths
- 2 requests/sec
- Community support
Starter
€9.00 /month
- 15,000 calls / month
- 6 requests / second
- Hard cap (429 above quota, no overage)
- Liquid + gas/vapour sizing
- Cavitation & choked-flow flags
- 6 requests/sec
- Email support
Pro
€24.00 /month
- 80,000 calls / month
- 16 requests / second
- Hard cap (429 above quota, no overage)
- Full two-phase & gas sizing
- Piping-geometry & Reynolds corrections
- Cv↔Kv unit conversion
- 16 requests/sec
Mega
€74.00 /month
- 450,000 calls / month
- 40 requests / second
- Hard cap (429 above quota, no overage)
- Unlimited valve-sizing scenarios
- Batch sizing for whole valve schedules
- Priority compute, 40 requests/sec
- SLA-backed uptime & priority support
Built by
Related APIs
Other APIs with overlapping tags.
Viscosity API
Fluid-viscosity physics as an API, computed locally and deterministically. The sutherland endpoint gives the dynamic viscosity of a gas at any temperature from Sutherland’s law, μ(T) = μ_ref·(T/T_ref)^1.5·(T_ref+S)/(T+S), with built-in constants for air, nitrogen, oxygen, carbon dioxide, hydrogen, helium and argon (or your own μ_ref, T_ref and S) — air comes out at about 1.72×10⁻⁵ Pa·s at 0 °C, 1.84×10⁻⁵ at 25 °C and 2.17×10⁻⁵ at 100 °C, returned in Pa·s, micro-Pa·s and centipoise. The kinematic endpoint converts between dynamic viscosity μ and kinematic viscosity ν through the density, ν = μ/ρ and μ = ν·ρ, so water at 1.002 cP and 998 kg/m³ becomes about 1.004 cSt. The convert endpoint handles viscosity units both ways — dynamic between Pa·s, centipoise and poise (1 Pa·s = 1000 cP = 10 P) and kinematic between m²/s, centistokes and stokes (1 m²/s = 10⁶ cSt = 10⁴ St). Temperatures are in °C or kelvin. Everything is computed locally and deterministically, so it is instant and private. Ideal for fluid-mechanics, CFD, process-engineering, lubrication, HVAC and chemical-engineering app developers, viscosity-correlation and unit-conversion tools, and simulation software. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This computes viscosity; for the Reynolds number that uses it use a Reynolds API.
api.oanor.com/viscosity-api
Heat Exchanger LMTD API
Heat-exchanger LMTD and effectiveness-NTU maths as an API, computed locally and deterministically. The lmtd endpoint computes the log mean temperature difference, LMTD = (ΔT1 − ΔT2)/ln(ΔT1/ΔT2), the true average driving temperature of a heat exchanger, from the hot and cold stream inlet and outlet temperatures for either a counterflow or a parallel-flow arrangement, and flags a temperature cross. The duty endpoint applies Q = U·A·LMTD·F — the heat duty equals the overall heat-transfer coefficient times the area times the LMTD times an optional correction factor — and solves for whichever of the duty, the coefficient, the area or the LMTD you leave out, taking the LMTD directly or from the four temperatures. The effectiveness endpoint uses the effectiveness-NTU method: from the hot and cold heat-capacity rates (given directly or as mass flow times specific heat) and the number of transfer units NTU = U·A/Cmin, it returns the capacity ratio, the effectiveness for the arrangement, and — given the inlet temperatures — the maximum and actual heat duty and the outlet temperatures. Everything is computed locally and deterministically, so it is instant and private. Ideal for process, chemical and mechanical engineering tools, HVAC, refrigeration and thermal-design apps, and engineering education. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is two-stream heat-exchanger analysis; for the sensible heat of a single stream Q = m·c·ΔT use a specific-heat API.
api.oanor.com/lmtd-api
Particle Settling API
Particle settling-velocity maths as an API, computed locally and deterministically. The stokes endpoint computes the terminal settling velocity of a small spherical particle by Stokes' law, vt = (ρp − ρf)·g·d²/(18·μ), from the particle diameter and density, the fluid density and the dynamic viscosity, and checks the particle Reynolds number to tell you whether the creeping-flow assumption (Re < 1) still holds — a negative velocity means a buoyant particle that rises. The terminal endpoint computes the drag-based terminal velocity for larger, faster particles, vt = √(4·g·d·(ρp − ρf)/(3·Cd·ρf)), from a drag coefficient (≈0.44 in the turbulent Newton regime). The time endpoint computes the time for a particle to settle through a given depth, t = height/vt, taking the velocity directly or deriving it from the particle properties via Stokes. Everything is computed locally and deterministically, so it is instant and private. Ideal for water- and wastewater-treatment, mineral-processing and environmental-engineering tools, clarifier and settling-tank design, sediment and aerosol analysis, and engineering education. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is particle sedimentation; for pipe-flow Reynolds/Froude/Mach numbers use a Reynolds API.
api.oanor.com/settling-api
Reynolds Number API
Dimensionless flow-number maths for fluid-mechanics similitude as an API, computed locally and deterministically. The reynolds endpoint computes the Reynolds number, Re = v·L/ν = ρvL/μ — the ratio of inertial to viscous forces — from the velocity, a characteristic length (pipe diameter) and either the kinematic viscosity or the density and dynamic viscosity, and classifies the flow as laminar (< 2300), transitional (2300–4000) or turbulent (> 4000). The froude endpoint computes the Froude number, Fr = v/√(g·L) — the ratio of inertia to gravity used for open-channel and ship flows — together with the critical velocity, and tells you whether the flow is subcritical (tranquil), critical or supercritical (shooting). The mach endpoint computes the Mach number, M = v/c, with the sound speed taken directly or worked out from the air temperature, c = √(γRT), and classifies the speed as subsonic, transonic, supersonic or hypersonic. Everything is computed locally and deterministically, so it is instant and private. Ideal for fluid-mechanics, aerodynamics and hydraulics tools, model-scaling and wind-tunnel similitude, pipe-flow and open-channel analysis, and engineering education. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is dimensionless-number similitude; for pipe friction pressure drop use a Darcy-Weisbach API and for open-channel uniform flow use a Manning API.
api.oanor.com/reynolds-api
Frequently asked questions
Quick answers about pricing, quotas, and integration.
How do I get an API key for Valve Flow Coefficient API?
What's the rate limit for Valve Flow Coefficient API?
How much does Valve Flow Coefficient API cost?
Can I cancel my subscription anytime?
Is Valve Flow Coefficient 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/valveflow-api/SOME_PATH \
-H "x-oanor-key: oanor_test_..."
const res = await fetch("https://api.oanor.com/valveflow-api/SOME_PATH", {
headers: { "x-oanor-key": "oanor_test_..." }
});
const data = await res.json();
$ch = curl_init("https://api.oanor.com/valveflow-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/valveflow-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.