oanor
Sign up free
Marketplace Pricing Features Sign in

API · /tire-api

Tire Calculator API

healthy 3,314 Subscribers

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.

#tire #tyre #automotive #fitment #vehicle #developer-tools
api.oanor.com/tire-api
Get an API key Try in playground → Contact provider

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

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

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

API health

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

Pricing

Pick a tier — billed monthly, cancel anytime.

Free

Free

  • 600 calls / month
  • 2 requests / second
  • Hard cap (429 above quota, no overage)
  • 600 calls/month
  • 2 req/sec
  • Size + pressure + speedo error
  • No credit card
Sign in to subscribe

Starter

€4.85 /month

  • 15,500 calls / month
  • 8 requests / second
  • Hard cap (429 above quota, no overage)
  • 15,500 calls/month
  • 8 req/sec
  • Revs/mile & gas-law pressure
  • Email support
Sign in to subscribe

Pro

€16.20 /month

  • 95,000 calls / month
  • 20 requests / second
  • Hard cap (429 above quota, no overage)
  • 95,000 calls/month
  • 20 req/sec
  • Fitment & fleet pipelines
  • Priority support
Sign in to subscribe

Mega

€48.60 /month

  • 310,000 calls / month
  • 48 requests / second
  • Hard cap (429 above quota, no overage)
  • 310,000 calls/month
  • 48 req/sec
  • Platform scale
  • Dedicated SLA
Sign in to subscribe

Built by

P
PremiumApi

Related APIs

Other APIs with overlapping tags.

Tire & Drivetrain API

Tyre, wheel and drivetrain maths as an API. The tire endpoint parses a metric tyre size such as 205/55R16 into all its real dimensions — section width, aspect ratio, sidewall height, rim and overall diameter in millimetres and inches, rolling circumference, and revolutions per kilometre and per mile. The compare endpoint takes an original and a replacement tyre size and works out the change in overall diameter and the resulting speedometer and odometer error — so you know how much faster you are really going than the dial shows after a tyre change. The gear endpoint computes a gear ratio from ring and pinion tooth counts, or the road speed from engine RPM, total gear ratio and tyre size. Everything is computed locally and deterministically, so it is instant and private. Ideal for automotive and motorsport apps, tyre shops and fitment tools, modding and restomod planning, and vehicle configurators. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is tyre and drivetrain maths; for vehicle specifications by VIN use a vehicle-database API.

api.oanor.com/tirecalc-api

Suspension Tuning API

Vehicle-suspension maths as an API, computed locally and deterministically — the spring and frequency numbers a racer, tuner or chassis engineer sets a car up with. The wheel-rate endpoint converts a spring rate to the rate the wheel actually feels: wheel rate = spring rate × motion ratio², where the motion ratio is the spring's travel per unit of wheel travel — a 200 lb/in spring at a 0.7 motion ratio gives a 98 lb/in wheel rate, because the spring's leverage softens it. The frequency endpoint gives the ride (natural) frequency at a corner, f = (1/2π)·√(wheel rate × g ÷ corner sprung weight), the number that really sets the ride: luxury cars run about 0.5–1.2 Hz, sporty street 1.2–1.7, race cars 2 Hz and up. The spring-rate endpoint inverts it — the spring rate needed to hit a target frequency for a corner weight and motion ratio — so you can pick the frequency for the car's job and get the spring straight out. Everything is computed locally and deterministically, so it is instant and private. Ideal for motorsport and tuning apps, chassis-setup and corner-balancing tools, suspension-design calculators, and engineering study aids. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 compute endpoints. Estimates — real ride also depends on damping and tyres.

api.oanor.com/suspension-api

Window Tint API

Window-tint maths as an API, computed locally and deterministically — the net VLT numbers an installer or car owner picks a film by. The catch with tint is that visible light transmission multiplies through layers: factory automotive glass already passes only about 70–80 % of light, so a film’s rated VLT is not what you end up with. The vlt endpoint multiplies it out — net % = the product of each layer’s VLT ÷ 100 — so a 35 % film on 78 % factory glass nets 27.3 %, a 5 % limo film on the same glass nets 3.9 %, and you can stack several layers in one call; it also describes how dark that looks, from near-clear down to blackout. The required endpoint runs it backwards: to land on a target net VLT through known glass you need a film of target ÷ glass × 100, so hitting a 35 % net on 78 % glass takes a 44.9 % film — and it flags the impossible case where the target is lighter than the bare glass already allows. Everything is computed locally and deterministically, so it is instant and private. Ideal for auto-tint, detailing, glass and automotive app developers, film-selection and compliance tools, and shop software. Pure local computation — no key, no third-party service, instant. Legal limits vary by jurisdiction — check local law. Live, nothing stored. 2 compute endpoints.

api.oanor.com/windowtint-api

Tire Size API

Tyre-size geometry as an API, computed locally and deterministically. The dimensions endpoint parses a metric tyre code such as 205/55R16 — or separate width, aspect ratio and rim values — into its full geometry: the sidewall height (width·aspect/100), the overall diameter (rim·25.4 + 2·sidewall) in millimetres and inches, the rolling circumference, and the revolutions per kilometre and per mile; a 205/55R16 works out to a 112.75 mm sidewall and a 631.9 mm (24.88 in) outside diameter. The compare endpoint takes an original and a replacement size and computes the speedometer error and ground-clearance change of swapping between them: because the speedometer is calibrated to the original rolling diameter, a larger tyre makes it read low, so true speed = indicated · OD_new/OD_old, and a tyre that is 2 % bigger means an indicated 100 is really about 102 km/h. Staying within ±3 % keeps the error and clearance change small. Tyre codes use the metric P-metric/Euro-metric form. Everything is computed locally and deterministically, so it is instant and private. Ideal for automotive, tyre-shop, fitment, car-enthusiast, fleet and vehicle-spec app developers, plus-sizing and speedo-error tools, and garage software. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 2 endpoints. This is metric tyre geometry; for fuel economy use a fuel-economy API.

api.oanor.com/tiresize-api

Frequently asked questions

Quick answers about pricing, quotas, and integration.

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