oanor
Sign up free
Marketplace Pricing Features Sign in

API · /caniuse-api

Can I Use API

healthy 4,682 Subscribers

Browser-feature compatibility data as an API — the "Can I Use" support tables for over 550 web platform features across 19 browsers (Chrome, Edge, Firefox, Safari, iOS Safari, Samsung Internet, Opera, IE and more). Look up any feature (flexbox, css-grid, webp, fetch, websockets, …) for its full support matrix: per-browser current support, the first version that shipped full support, partial/prefixed/disabled flags and notes, the spec status, categories, keywords, global usage share and reference links. Ask a single feature×browser question, list or filter features by category, search features by keyword, and get the browser/agent list with version histories and the category/status legend. Backed by the public caniuse-db dataset (refreshed every 12 hours); query results are computed live. 7 endpoints. Built for build tooling, polyfill decisions, compatibility dashboards, linters and documentation. No upstream key.

#caniuse #browser-compatibility #web-platform #developer-tools #css #frontend
api.oanor.com/caniuse-api
Get an API key Try in playground → Contact provider

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

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

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

API health

healthy
Uptime
100.00%
Server probes · 24h
Avg latency
154 ms
Server probes · 24h
Subscribers
4,682
active
Total calls
112
last 7 days
status Full status page → · 21 probes/24h

Pricing

Pick a tier — billed monthly, cancel anytime.

Free

Free

  • 2,150 calls / month
  • 2 requests / second
  • Hard cap (429 above quota, no overage)
  • 2,150 calls/month
  • 2 req/sec
  • All 7 endpoints, 550+ features
  • No credit card
Sign in to subscribe

Starter

€8.50 /month

  • 47,000 calls / month
  • 8 requests / second
  • Hard cap (429 above quota, no overage)
  • 47k calls/month
  • 8 req/sec
  • Full support matrices
  • Email support
Sign in to subscribe

Pro

€27.00 /month

  • 238,000 calls / month
  • 20 requests / second
  • Hard cap (429 above quota, no overage)
  • 238k calls/month
  • 20 req/sec
  • Build-tooling / linters
  • Priority support
Sign in to subscribe

Mega

€62.00 /month

  • 1,190,000 calls / month
  • 50 requests / second
  • Hard cap (429 above quota, no overage)
  • 1.19M calls/month
  • 50 req/sec
  • CI / platform scale
  • Dedicated SLA
Sign in to subscribe

Built by

P
PremiumApi

Related APIs

Other APIs with overlapping tags.

Cable Tray Fill API

Cable-tray fill engineering maths as an API, computed locally and deterministically from NEC Article 392 — the allowable-fill, single-layer and tray-width numbers an electrician, estimator or designer runs for a tray run. The fill endpoint applies NEC 392.22(A)(1) Column 1 for multiconductor power and lighting cables no larger than 4/0 in a ladder or ventilated-bottom tray: the total cable cross-sectional area is capped at the tray width × 7/6, so a 12-inch tray allows 14 in² — sum every cable's csa, get the percentage fill and whether it is within code, with the spare area left. The large-cable endpoint covers cables 4/0 and larger, which must lie in a single layer with the sum of their diameters not exceeding the tray width — no stacking — so it returns the spare width and the code check. The min-width endpoint inverts the rule to size the tray: minimum width = cable area × 6/7, rounded up to a standard 6/9/12/18/24/30/36-inch width, leaving room for spare capacity and future cables. Everything is computed locally and deterministically, so it is instant and private. Ideal for electrical-design and estimating tools, industrial and OSP utilities, and code-check calculators. Pure local computation — no key, no third-party service, instant. Ladder/ventilated trays; solid-bottom and mixed fills use the other NEC columns, and ampacity must be derated for fill. 3 compute endpoints. For conduit and box fill use a conduit API.

api.oanor.com/cabletray-api

Off-Grid Solar Sizing API

Off-grid solar system-sizing maths as an API, computed locally and deterministically — the battery-bank, solar-array and charge-controller numbers an RV, cabin, boat or off-grid homeowner sizes a system with. The battery-bank endpoint gives the storage you need = (daily load × days of autonomy) ÷ (depth of discharge × round-trip efficiency), then ÷ the system voltage for amp-hours: the autonomy carries you through cloudy days and the depth-of-discharge limit protects the cells (lead-acid ~50 %, lithium 80–100 %, which is why lithium banks run smaller), so a 2 kWh/day load at 12 V with 2 days autonomy, 50 % DoD and 85 % efficiency needs about 785 Ah. The array endpoint gives the panels = daily energy ÷ (peak sun hours × system efficiency), where peak sun hours is the day's irradiance as equivalent full-sun hours (~3–6 by place and season) and the efficiency rolls up controller, wiring, heat and dust losses — about 670 W for that load at 4 sun hours and 75 %. The charge-controller endpoint sizes the controller = array watts ÷ battery voltage × a 1.25 safety factor, so a 700 W array on a 12 V bank wants roughly an 80 A controller. Everything is computed locally and deterministically, so it is instant and private. Ideal for solar-installer and DIY tools, RV/marine/cabin power planners, and renewable-energy calculators. Pure local computation — no key, no third-party service, instant. Size for the worst month. 3 compute endpoints. For solar irradiance and sun hours use a solar API; for battery runtime under load a battery API.

api.oanor.com/offgrid-api

Aircraft Fuel Planning API

Aircraft fuel-planning maths as an API, computed locally and deterministically — the endurance, range and fuel-required numbers a pilot, dispatcher or flight-sim developer plans a flight with, all honouring a reserve. The endurance endpoint gives how long you can fly = usable fuel ÷ burn rate, holding back a reserve (30 min day / 45 min night VFR, 45 min IFR is typical), so the usable endurance is the time you can actually plan to rather than the tanks-dry figure — 50 gallons at 10 gph is 5:00 total but 4:15 usable on a 45-minute reserve. The range endpoint turns that into distance = usable endurance × ground speed, so it lives or dies on the wind: a headwind cuts the ground speed and the range while burning the same fuel per hour, which is why you plan on the forecast ground speed, not the true airspeed. The fuel-required endpoint sizes the load for a leg = trip time × burn plus the reserve — 300 nm at 120 kt and 10 gph needs 25 gallons of trip fuel plus 7.5 reserve, 32.5 total — to which a real flight adds taxi and climb allowances. Everything is computed locally and deterministically, so it is instant and private. Ideal for flight-planning and EFB apps, dispatch and flight-school tools, flight-simulator utilities, and general-aviation calculators. Pure local computation — no key, no third-party service, instant. Add taxi/climb and a personal margin; confirm against tank capacity and weight-and-balance. 3 compute endpoints. For glide range use a glide-ratio API; for density altitude a density-altitude API.

api.oanor.com/fuelburn-api

Glide Ratio API

Aircraft glide-performance maths as an API, computed locally and deterministically — the glide-distance, glide-ratio and reachability numbers a pilot, flight-instructor or flight-sim developer works an engine-out or soaring problem with. The glide-distance endpoint gives the still-air distance you can cover = height above the ground × the glide ratio (L/D): from 5,000 ft at a 9:1 ratio you reach about 45,000 ft, ~7.4 nm, with the answer in feet, nautical miles and kilometres. The glide-ratio endpoint reads the slope straight off the polar — glide ratio = forward speed ÷ sink rate (1 knot ≈ 101.27 ft/min), so 60 kt at a 600 ft/min sink is about 10:1, a 5.6° glide path — and gliders reach 40–60:1, a light single ~9:1, an airliner ~17:1. The reach endpoint answers the practical question: the height needed to reach a field = distance ÷ glide ratio, the arrival height is what is left, and it only counts as making it if that clears a safety reserve (default 1,000 ft) for the circuit and approach. Everything is computed locally and deterministically, so it is instant and private. Ideal for flight-planning and EFB apps, gliding and soaring tools, flight-simulator and training utilities, and aviation-safety calculators. Pure local computation — no key, no third-party service, instant. Still-air estimates — adjust for wind, configuration and a margin. 3 compute endpoints. For density altitude use a density-altitude API; for runway wind components a crosswind API.

api.oanor.com/glideratio-api

Frequently asked questions

Quick answers about pricing, quotas, and integration.

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