RAID capacity
API · /raid-api
RAID Calculator API
RAID storage-array maths as an API, computed locally and deterministically. The capacity endpoint computes the usable and raw capacity, the storage efficiency and the fault tolerance of a RAID level — RAID 0 stripes for n×disk with no redundancy, RAID 1 mirrors to one disk and tolerates n−1 failures, RAID 5 gives (n−1)×disk with one-disk tolerance, RAID 6 gives (n−2)×disk with two-disk tolerance, and RAID 10 gives (n/2)×disk — and reports the minimum disks each level needs. The compare endpoint lays the levels side by side for the same disks and disk size so you can weigh capacity against redundancy. The rebuild endpoint estimates how long it takes to rebuild a single disk at a given rebuild speed, the window during which a second failure would lose data in RAID 5/6. Everything is computed locally and deterministically, so it is instant and private. Ideal for storage, NAS, server and IT-admin app developers, capacity-planning and procurement tools, and homelab calculators. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is RAID array sizing; for data-transfer time use a transfer API.
API health
healthy- Uptime
- 100.00%
- Server probes · 24h
- Avg latency
- 89 ms
- Server probes · 24h
- Subscribers
- 3,955
- 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)
- Usable + raw capacity for RAID 0/1/5/6/10
- Storage efficiency percentage
- 2 requests/sec
Starter
€6.00 /month
- 15,000 calls / month
- 5 requests / second
- Hard cap (429 above quota, no overage)
- All RAID levels incl. RAID 50/60
- Fault-tolerance + drive-loss analysis
- Mixed drive-size handling
- 5 requests/sec
Pro
€18.00 /month
- 80,000 calls / month
- 15 requests / second
- Hard cap (429 above quota, no overage)
- Bulk array comparison in one call
- Rebuild-time + parity overhead estimates
- Cost-per-usable-TB output
- 15 requests/sec
Mega
€59.00 /month
- 400,000 calls / month
- 40 requests / second
- Hard cap (429 above quota, no overage)
- High-volume capacity-planning automation
- Full RAID matrix + nested-array maths
- Priority support + 99.9% SLA
- 40 requests/sec
Built by
Related APIs
Other APIs with overlapping tags.
Humidor API
Cigar-humidor maths as an API, computed locally and deterministically — the numbers behind storing cigars right, so you buy the correct humidor and keep it at the perfect humidity. The capacity endpoint works out how many cigars an interior holds: interior volume × a packing efficiency ÷ one cigar's volume, where a cigar is a cylinder of its ring gauge (in 64ths of an inch) and length — a 9 × 7 × 3 inch interior holds about 40 Toros (ring 50, 6 inch) at a realistic 0.62 packing, leaving room for air and a humidification device. The media endpoint sizes the humidification: about one 60 g two-way pack per 25 cigars, replaced roughly every two months, so a 40-cigar humidor wants two packs. The seasoning endpoint covers a brand-new humidor — its Spanish cedar must absorb moisture for about two weeks at 84 % RH (one seasoning pack per 25-cigar capacity, or the distilled-water wipe-down) before any cigars go in, or the dry wood will rob them. Everything is computed locally and deterministically, so it is instant and private. Ideal for cigar-shop and tobacconist apps, humidor-maker product pages, cigar-aficionado and collection-tracker sites, and buying guides. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 compute endpoints. For room humidity or dew point use a psychrometric API.
api.oanor.com/humidor-api
Grain Bin API
Grain-bin storage maths as an API, computed locally and deterministically — the bushel and weight numbers a farmer or elevator sizes storage by. The bushels endpoint measures a round bin: floor area × grain depth gives the cubic feet, and a cubic foot holds about 0.8036 bushels, so an 18-foot bin filled 20 feet level holds roughly 4,090 bushels — and grain heaped to a peak adds a cone of (1/3) × floor area × peak height, so a 4-foot peak adds about 270 more. The weight endpoint converts bushels to weight by the crop’s standard test weight — corn and sorghum at 56 pounds a bushel, wheat and soybeans 60, oats 32, barley 48 — so those 4,090 bushels of corn weigh 229,040 pounds, about 114.5 US tons or 104 tonnes; pass a measured test weight for light or heavy grain. Everything is computed locally and deterministically, so it is instant and private. Ideal for agriculture, grain-elevator, farm-management and ag-tech app developers, storage-capacity and inventory tools, and harvest software. Pure local computation — no key, no third-party service, instant. US units (feet, bushels, pounds). Live, nothing stored. 2 compute endpoints.
api.oanor.com/grainbin-api
Queueing Theory API
Queueing-theory maths as an API, computed locally and deterministically. The littles-law endpoint applies Little's law, L = λ·W — the average number in a system equals the arrival rate times the average time in the system — and solves for whichever of the three you leave out; it holds for any stable system, from a checkout line to a request pipeline. The mm1 endpoint gives the full steady-state metrics of a single-server M/M/1 queue from the arrival rate λ and the service rate μ: the utilization ρ = λ/μ, the average number in the system and in the queue, the average time in the system and waiting, and the probability the system is empty — and it flags an unstable queue when ρ ≥ 1. The mmc endpoint extends this to a multi-server M/M/c queue with the Erlang-C waiting probability, returning the offered load in erlangs, the per-server utilization, the chance an arrival has to wait, and the same length and time metrics. Rates must share a time unit, and the times come out in that unit. Everything is computed locally and deterministically, so it is instant and private. Ideal for capacity-planning and operations tools, call-centre and staffing apps, server and throughput sizing, and operations-research education. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is queueing theory; for descriptive statistics on a list of numbers use a statistics API.
api.oanor.com/queue-api
chmod API
A Unix file-permission calculator as an API. Convert a symbolic permission string (rwxr-xr-x) to its octal mode (755) and back, and explain any mode in plain English with a per-class breakdown (owner / group / others, each read / write / execute). Full support for the special bits — setuid (4), setgid (2) and the sticky bit (1) — so 4755 ↔ rwsr-xr-x and 1777 ↔ rwxrwxrwt are handled correctly, including the capital S/T forms. Perfect for Dockerfiles and CI scripts, deployment and provisioning tooling, teaching, and any time you need to double-check a chmod value. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 4 endpoints. Distinct from anything that touches real files or networking.
api.oanor.com/chmod-api
Frequently asked questions
Quick answers about pricing, quotas, and integration.
How do I get an API key for RAID Calculator API?
What's the rate limit for RAID Calculator API?
How much does RAID Calculator API cost?
Can I cancel my subscription anytime?
Is RAID Calculator 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/raid-api/SOME_PATH \
-H "x-oanor-key: oanor_test_..."
const res = await fetch("https://api.oanor.com/raid-api/SOME_PATH", {
headers: { "x-oanor-key": "oanor_test_..." }
});
const data = await res.json();
$ch = curl_init("https://api.oanor.com/raid-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/raid-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.