Availability & downtime
API · /reliability-api
Reliability Engineering API
Reliability-engineering maths as an API, computed locally and deterministically — the availability, MTBF and failure maths behind SLAs and dependable systems. The availability endpoint converts between MTBF and MTTR, a target availability and the SLA "nines": give it a mean time between failures and a mean time to repair and it returns the availability A = MTBF/(MTBF+MTTR) and the downtime per year, month, week and day; give it a number of nines and it returns the budget — three nines (99.9 %) is 8.76 hours of downtime a year, five nines (99.999 %) just 5.26 minutes. The reliability endpoint computes the probability a unit survives a mission time under the exponential model R(t) = e^(−λt) with its constant hazard λ = 1/MTBF, or the Weibull model R(t) = e^(−(t/η)^β) — β below one for infant mortality, one for random failures, above one for wear-out — returning the reliability, failure probability, hazard rate and the mean life η·Γ(1+1/β). The system endpoint combines component reliabilities into a system: series (the weakest link, ΠRᵢ), parallel redundancy (1−Π(1−Rᵢ)) or k-of-n voting. Everything is computed locally and deterministically, so it is instant and private. Ideal for SRE, DevOps, hardware-reliability, safety-engineering and SLA-planning app developers, uptime-budget and redundancy-design tools, and engineering education. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 compute endpoints. This is reliability and availability maths; for queue wait-times use a queueing API and for live uptime checks use a monitoring service.
API health
healthy- Uptime
- 100.00%
- Server probes · 24h
- Avg latency
- 83 ms
- Server probes · 24h
- Subscribers
- 4,656
- active
- Total calls
- 28
- last 7 days
Pricing
Pick a tier — billed monthly, cancel anytime.
Free
Free
- 4,150 calls / month
- 2 requests / second
- Hard cap (429 above quota, no overage)
- 4,150 calls/month
- 2 req/sec
- Availability + reliability + system
- No credit card
Starter
€6.40 /month
- 43,000 calls / month
- 6 requests / second
- Hard cap (429 above quota, no overage)
- 43,000 calls/month
- 6 req/sec
- MTBF/MTTR, nines, Weibull, k-of-n
- Email support
Pro
€16.90 /month
- 198,000 calls / month
- 15 requests / second
- Hard cap (429 above quota, no overage)
- 198,000 calls/month
- 15 req/sec
- SRE & SLA-planning pipelines
- Priority support
Mega
€51.00 /month
- 1,140,000 calls / month
- 40 requests / second
- Hard cap (429 above quota, no overage)
- 1,140,000 calls/month
- 40 req/sec
- Platform scale
- Dedicated SLA
Built by
Related APIs
Other APIs with overlapping tags.
Bearing Life API
Rolling-element bearing life maths (ISO 281) as an API, computed locally and deterministically. The life endpoint computes the basic rating life of a ball or roller bearing, L10 = (C/P)^p — where p is 3 for ball bearings and 10/3 for roller bearings — from the dynamic load rating C and the equivalent load P, reporting the life in millions of revolutions and, given a speed in rpm, in hours and days; it also works backwards, solving the minimum dynamic load rating needed for a target life, or the maximum load a bearing can carry to still reach it. The load endpoint computes the equivalent dynamic load P = X·Fr + Y·Fa from the radial and axial loads and the bearing X and Y factors, the single load value the life formula needs. The reliability endpoint applies the ISO 281 life-modification factor a1 to give the adjusted rating life Lna = a1·L10 for any survival probability from 90 % up to 99.95 %, interpolated from the standard reliability table. Everything is computed locally and deterministically, so it is instant and private. Ideal for mechanical-engineering, maintenance and reliability tools, machine and drivetrain design, predictive-maintenance and lifetime-costing apps, and engineering education. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is rolling-bearing rating life; for shaft torsion stress use a torsion API and for rotational energy use a flywheel API.
api.oanor.com/bearing-api
Media Bias API
Political-bias and factual-reporting ratings for 1,350+ news sources, sourced from AllSides and Media Bias/Fact Check. Look up any outlet by domain or name to get its left/center/right political lean (5-point scale) and high/mixed/low factual reliability — ideal for news aggregators, media-literacy tools and content moderation.
api.oanor.com/mediabias-api
Business Days API
Working-day date math. Count the business days between two dates, add or subtract a number of working days from a date (negative goes backwards), and check whether a given date is a business day — all skipping weekends and any holidays you supply. Configure which days count as the weekend (Saturday/Sunday by default, or e.g. Friday/Saturday) and pass a list of custom holiday dates to exclude. Perfect for SLA and support deadlines, delivery and lead-time estimates, payroll and invoicing periods, and financial settlement dates. Pure local UTC date math — no key, no third-party service, deterministic and instant. Live. 4 endpoints. Distinct from a calendar date toolkit (which counts calendar days) and a holidays directory (which lists holidays).
api.oanor.com/businessdays-api
Balloon Decor API
Party-balloon maths as an API, computed locally and deterministically — the helium-lift and balloon-count numbers a party planner or balloon artist decorates by. The helium endpoint gives a balloon’s lift from its inflated diameter: net lift is the inflated volume times the difference between air and helium density, about 1.046 grams per litre, so a fully inflated 11-inch latex balloon (around 11.4 litres) lifts roughly 12 grams gross and about 9 after its own weight, while a 36-inch giant lifts hundreds of grams. The float endpoint flips it around — how many balloons to float a payload = the weight divided by the net lift per balloon, rounded up, so a 50-gram card floats on six 11-inch balloons. The garland endpoint sizes an organic balloon garland or arch from its length: about 12 balloons per foot in a mix of sizes — roughly 40 % 5-inch, 45 % 11-inch and 15 % 16-inch for that full, textured look — so a 10-foot garland takes about 120 balloons, denser if you want it lush. Everything is computed locally and deterministically, so it is instant and private. Ideal for party-planning, event-decor, balloon-artist and celebration app developers, decor-estimator and shopping-list tools, and event software. Pure local computation — no key, no third-party service, instant. Inches and grams. Live, nothing stored. 3 compute endpoints.
api.oanor.com/balloon-api
Frequently asked questions
Quick answers about pricing, quotas, and integration.
How do I get an API key for Reliability Engineering API?
What's the rate limit for Reliability Engineering API?
How much does Reliability Engineering API cost?
Can I cancel my subscription anytime?
Is Reliability Engineering 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/reliability-api/SOME_PATH \
-H "x-oanor-key: oanor_test_..."
const res = await fetch("https://api.oanor.com/reliability-api/SOME_PATH", {
headers: { "x-oanor-key": "oanor_test_..." }
});
const data = await res.json();
$ch = curl_init("https://api.oanor.com/reliability-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/reliability-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.