oanor
Sign up free
Marketplace Pricing Features Sign in

API · /queue-api

Queueing Theory API

healthy 3,808 Subscribers

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.

#queueing-theory #littles-law #operations-research #erlang #capacity-planning #developer-tools
api.oanor.com/queue-api
Get an API key Try in playground → Contact provider

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

/api/queue-api/openapi.json
/api/queue-api/llms.txt

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

API health

healthy
Uptime
100.00%
Server probes · 24h
Avg latency
85 ms
Server probes · 24h
Subscribers
3,808
active
Total calls
44
last 7 days
status Full status page → · 24 probes/24h

Pricing

Pick a tier — billed monthly, cancel anytime.

Free

Free

  • 2,000 calls / month
  • 2 requests / second
  • Hard cap (429 above quota, no overage)
  • Little's law L = lambda * W endpoint
  • Deterministic local compute, no upstream latency
  • 2,000 calls/month for prototyping
Sign in to subscribe

Starter

€9.00 /month

  • 40,000 calls / month
  • 5 requests / second
  • Hard cap (429 above quota, no overage)
  • M/M/1 and M/M/c queue metrics
  • Erlang B/C blocking & wait probabilities
  • 40,000 calls/month
  • Email support
Sign in to subscribe

Pro

€24.00 /month

  • 250,000 calls / month
  • 15 requests / second
  • Hard cap (429 above quota, no overage)
  • Full capacity-planning suite (utilization, Lq, Wq)
  • Multi-server staffing optimization
  • 250,000 calls/month
  • Priority support
Sign in to subscribe

Mega

€75.00 /month

  • 1,543,000 calls / month
  • 40 requests / second
  • Hard cap (429 above quota, no overage)
  • Unlimited queueing-model endpoints
  • High-throughput batch capacity planning
  • 1,500,000 calls/month
  • SLA-backed support
Sign in to subscribe

Built by

P
PremiumApi

Related APIs

Other APIs with overlapping tags.

Hex API

The Elixir and Erlang package ecosystem — Hex (hex.pm) — as an API. Look up any Hex package for its description, licenses, latest version, GitHub / docs / changelog links, owners and download counts (all-time and recent); read a package's complete release history with publication dates; get a single release's dependency list, Elixir version constraint and build tools; and search the entire Hex registry by keyword. Covers the Elixir/Erlang (BEAM) ecosystem from Phoenix, Ecto and Plug to Jason, Absinthe and Nerves. Live from the official hex.pm API. Ideal for package dashboards, dependency and supply-chain tooling, Elixir developer portals and BEAM ecosystem analytics. Open data from Hex.

api.oanor.com/hex-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.oanor.com/raid-api

Air Compressor API

Compressed-air maths as an API, computed locally and deterministically — the receiver, pump-up and SCFM numbers a pneumatics tech or shop owner sizes a system with. The receiver-size endpoint gives the tank you need to ride out a demand burst: volume = demand (free-air CFM) × minutes × 14.7 ÷ the usable pressure window (max − min) — pulling 20 CFM for a minute over a 175-to-100 psi window wants about a 30-gallon receiver, the buffer that lets the pump catch up. The pumpup endpoint gives the time to raise a receiver from one pressure to another: volume × pressure rise ÷ (14.7 × compressor CFM), so a 60-gallon tank from 100 to 175 psi on a 15 CFM compressor takes about 2.7 minutes. The scfm endpoint corrects actual CFM to standard CFM for the inlet conditions — SCFM = ACFM × (inlet pressure ÷ 14.696) × (528 ÷ inlet temperature in Rankine) — so a compressor at 5,000 feet delivers about 17 % fewer SCFM than at sea level, the reason you size tools on SCFM, not the nameplate. Everything is computed locally and deterministically, so it is instant and private. Ideal for pneumatics and shop-air apps, compressor-sizing and tool-demand tools, industrial-air calculators, and trade aids. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 compute endpoints. Estimates — duty cycle and the pump curve shift real numbers.

api.oanor.com/compressor-api

Tire Calculator API

Tire maths as an API, computed locally and deterministically — the size, pressure and speedometer numbers a driver, fitter or fleet manager works out before fitting a tyre. The size endpoint turns a P-metric spec into the real dimensions: overall diameter = rim + 2 × the sidewall (section width × aspect ratio), so a 225/45R17 stands about 25 inches tall, rolls a 78-inch circumference and turns roughly 808 times a mile — the numbers behind fitment, gearing and clearance. The pressure endpoint gives the hot pressure from a cold pressure and the temperature change, because pressure tracks absolute temperature (P2/P1 = T2/T1), about +1 psi per 10 °F — so 32 psi set cold at 70 °F reads ~34.6 after warming to 100 °F, and drops on a cold morning, which is what trips the warning light. The speedo-error endpoint gives the speedometer error and true speed from a tyre-size change: a taller tyre makes the speedo read low, so actual speed = indicated × new diameter ÷ old — go up 4 % and 60 on the dial is really 62.5. Everything is computed locally and deterministically, so it is instant and private. Ideal for tyre-shop and fitment apps, fleet and 4x4 build tools, speedo-recalibration calculators, and automotive sites. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 compute endpoints. Estimates — always set pressure cold to the placard.

api.oanor.com/tire-api

Frequently asked questions

Quick answers about pricing, quotas, and integration.

How do I get an API key for Queueing Theory API?
Sign up for free at oanor.com, generate an API key from the developer dashboard, and call Queueing Theory API with the x-oanor-key header. No credit card needed for the free tier.
What's the rate limit for Queueing Theory 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 Queueing Theory API cost?
Queueing Theory API has a free tier with 100 calls / month. Paid plans start at €9.00 / 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 Queueing Theory API GDPR-compliant?
All requests to Queueing Theory 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/queue-api/SOME_PATH \
  -H "x-oanor-key: oanor_test_..."
const res = await fetch("https://api.oanor.com/queue-api/SOME_PATH", {
  headers: { "x-oanor-key": "oanor_test_..." }
});
const data = await res.json();
$ch = curl_init("https://api.oanor.com/queue-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/queue-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 in

New thread

/ 4000

📌 Pinned 🔒 Locked

·

· ·

/ 4000

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

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.