OEE: availability × performance × quality
API · /oee-api
OEE Manufacturing API
healthy
4,575 Subscribers
Overall Equipment Effectiveness (OEE) and lean-manufacturing maths as an API, computed locally and deterministically — the factory-floor productivity metric behind TPM and continuous improvement. The oee endpoint takes the planned production time, downtime, the total and good piece counts and the ideal cycle time (seconds per piece, or an ideal rate in pieces per minute) and returns the three factors and their product: Availability = run time / planned time, Performance = ideal time for the parts made / run time, Quality = good / total, and OEE = Availability × Performance × Quality — the textbook example of a 420-minute shift with 47 minutes down, 19,271 parts and 423 rejects lands exactly on 74.79 % (88.81 % × 86.11 % × 97.80 %). It also breaks out the six-big-losses view: availability loss, performance (speed) loss in parts, quality loss and the fully-productive part count. The takt endpoint gives the takt time = available time / customer demand (the drumbeat the line must match), the required rate, and — given a cycle time or a total work content — the line capacity, utilisation, whether it meets demand and the minimum number of workstations with the line-balancing efficiency. Everything is computed locally and deterministically, so it is instant and private. Ideal for manufacturing, smart-factory, MES, IoT-dashboard and lean/TPM app developers, production-line monitoring and continuous-improvement tools, and industrial-engineering training. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 2 compute endpoints. This is OEE and takt maths; for equipment reliability/MTBF use a reliability API.
api.oanor.com/oee-api
API health
healthy- Uptime
- 100.00%
- Server probes · 24h
- Avg latency
- 82 ms
- Server probes · 24h
- Subscribers
- 4,575
- active
- Total calls
- 21
- last 7 days
Pricing
Pick a tier — billed monthly, cancel anytime.
Free
Free
- 3,650 calls / month
- 2 requests / second
- Hard cap (429 above quota, no overage)
- 3,650 calls/month
- 2 req/sec
- OEE + takt time + line balancing
- No credit card
Starter
€6.15 /month
- 40,500 calls / month
- 6 requests / second
- Hard cap (429 above quota, no overage)
- 40,500 calls/month
- 6 req/sec
- Six big losses, capacity, stations
- Email support
Pro
€16.40 /month
- 201,000 calls / month
- 15 requests / second
- Hard cap (429 above quota, no overage)
- 201,000 calls/month
- 15 req/sec
- MES & smart-factory pipelines
- Priority support
Mega
€49.50 /month
- 1,160,000 calls / month
- 40 requests / second
- Hard cap (429 above quota, no overage)
- 1,160,000 calls/month
- 40 req/sec
- Platform scale
- Dedicated SLA
Built by
Related APIs
Other APIs with overlapping tags.
Welding Settings API
Welding settings and consumables maths as an API, computed locally and deterministically — the amperage, wire and gas numbers a welder or fabricator dials a machine in with. (For joint strength, that is a separate weld-strength calculation.) The amperage endpoint gives a starting current from material thickness using the mild-steel rule of thumb of about one amp per 0.001 inch — so an eighth-inch plate runs around 125 A, give or take ten percent — and suggests an electrode or wire size to match. The deposition endpoint does the MIG arithmetic exactly: deposition rate (lb/hr) = wire feed speed × the wire’s weight per inch × 60 × efficiency, where weight per inch = (π/4 · d²) × 0.284 lb/in³ for steel, so 0.035-inch wire at 300 in/min lays down about 4.9 lb/hr fed, 4.8 deposited at 98 % — and from a target deposit it returns the arc time and the pounds of wire to buy. The gas endpoint sizes shielding gas: gas used (ft³) = flow in CFH × arc time in hours, and a cylinder’s arc-time duration, so 35 CFH empties an 80 ft³ bottle in about 2.3 hours of actual arc time. Everything is computed locally and deterministically, so it is instant and private. Ideal for welding, metal-fabrication, manufacturing and shop-management app developers, job-costing and consumable-planning tools, and welding-education software. Pure local computation — no key, no third-party service, instant. Machine settings, not joint strength. Live, nothing stored. 3 compute endpoints.
api.oanor.com/welding-api
Machining Speed API
Machining cutting-speed and feed maths as an API, computed locally and deterministically. The speed endpoint converts between cutting (surface) speed and spindle rpm for a given tool or workpiece diameter, in both directions and in either unit system: metric uses N = Vc·1000/(π·D) with Vc in metres per minute and D in millimetres, and imperial uses RPM = SFM·12/(π·D) with the surface speed in feet per minute and the diameter in inches. The feed endpoint computes the table feed rate from the feed per tooth (chip load), the number of teeth or flutes and the spindle rpm for milling (feed = fz·z·N), or from the feed per revolution for turning and drilling, and reports it in millimetres or inches per minute. The materials endpoint lists typical carbide cutting speeds by material, from aluminium and brass through mild and stainless steel to titanium, with a note to use about a third for HSS tooling. Everything is computed locally and deterministically, so it is instant and private. An indicative aid — always confirm with the tool maker's data and adjust for depth of cut, coolant and rigidity. Ideal for CNC and machine-shop tools, CAM and feeds-and-speeds apps, maker and hobby machining, and manufacturing calculators. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is machining feeds and speeds; for screw-thread pitch and tap drill use a thread API and for bolt-circle layouts use a bolt-circle API.
api.oanor.com/machining-api
Reptile Husbandry API
Reptile-husbandry maths as an API, computed locally and deterministically — the keeper numbers behind a healthy vivarium, so the setup is right before the animal moves in. The enclosure endpoint turns an animal length and its habit into the minimum floor length, width and height: terrestrial snakes want a floor at least as long as the snake (a 48-inch corn snake → a 48 × 24 × 24 inch minimum, eight square feet of floor), arboreal species trade floor for height (an 18-inch chameleon → 27 × 18 × 36 inches, tall), and ground lizards and tortoises need far more floor than their body length. The uvb endpoint gives the UV-B target by Ferguson zone — the 1-to-4 classification from Baines et al. (2016) of how much sun a species basks in — returning the mean and basking UV-index ranges (zone 3 open baskers want a basking UVI of 2.9–7.4), and, if you pass a lamp UVI measured at a reference distance, an inverse-square estimate of the mounting distance for the right basking UVI. The feeding endpoint sizes prey from body weight and life stage: a meal of roughly 10–15 % of body weight, no wider than the animal, on an interval that lengthens with age — a 500 g adult snake takes a 40–60 g prey item every fortnight. Everything is computed locally and deterministically, so it is instant and private. Ideal for reptile-keeper and herpetoculture apps, pet-store and breeder tools, vivarium-planning calculators, and care-sheet sites. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 compute endpoints. Educational husbandry estimates — not veterinary advice; research your exact species.
api.oanor.com/reptile-api
Garden Pond API
Garden and koi-pond maths as an API, computed locally and deterministically — the numbers behind a backyard water feature, so you do not have to guess at the hose. The volume endpoint turns length, width and average depth into the water volume in cubic feet, US gallons and litres, applying a shape factor (rectangular 1.0, oval or round 0.79, irregular 0.85) because a liner pond never holds the full bounding box: an 8 × 6 ft pond two feet deep is about 96 cubic feet, or 718 gallons. The liner endpoint sizes the flexible liner to fit a pond — length equals the pond length plus twice the maximum depth plus twice the overlap to anchor under the edging stones (same for width), so that same 8 × 6 pond at two feet deep with a one-foot overlap needs a 14 × 12 ft liner and matching underlayment. The stock endpoint turns a water volume into a safe fish load and the pump you need: roughly one koi per 250 gallons (they grow large and dirty) or one goldfish per 20, plus the pump flow in gallons per hour to turn the whole pond over at least once an hour for koi — 718 gallons holds about two koi and wants a ~720 GPH pump before head-height losses. Everything is computed locally and deterministically, so it is instant and private. Ideal for landscaping and pond-installer tools, garden-design and home-improvement apps, koi and water-garden hobbyist sites, and aquascaping calculators. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 compute endpoints. For pool chemistry use a pool API; for indoor fish tanks use an aquarium API.
api.oanor.com/pond-api
Frequently asked questions
Quick answers about pricing, quotas, and integration.
How do I get an API key for OEE Manufacturing API?
Sign up for free at oanor.com, generate an API key from the developer dashboard, and call OEE Manufacturing API with the x-oanor-key header. No credit card needed for the free tier.
What's the rate limit for OEE Manufacturing 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 OEE Manufacturing API cost?
OEE Manufacturing API has a free tier with 100 calls / month. Paid plans start at €6.15 / 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 OEE Manufacturing API GDPR-compliant?
All requests to OEE Manufacturing 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/oee-api/SOME_PATH \
-H "x-oanor-key: oanor_test_..."const res = await fetch("https://api.oanor.com/oee-api/SOME_PATH", {
headers: { "x-oanor-key": "oanor_test_..." }
});
const data = await res.json();$ch = curl_init("https://api.oanor.com/oee-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/oee-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
📌 Pinned
🔒 Locked
·
·
·
-
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.