oanor
Sign up free
Marketplace Pricing Features Sign in

API · /brake-api

Vehicle Braking API

healthy 3,774 Subscribers

Vehicle-braking physics as an API, computed locally and deterministically. The stopping-distance endpoint computes the total distance to stop a vehicle as the sum of the reaction distance the vehicle travels during the driver's reaction time, v·t, and the braking distance v²/(2·μ·g) — which grows with the square of speed, so doubling the speed quadruples the braking distance — from the speed, the tyre-road friction coefficient, the reaction time and the road grade, along with the deceleration and the time to stop. The braking-force endpoint computes the braking force F = m·a and the deceleration of a vehicle, either from a stop-in-a-given-distance (a = v²/2d) or from the friction coefficient (a = μ·g), with the kinetic energy that must be dissipated as heat. The skid-speed endpoint reconstructs the speed at the start of a skid from the skid-mark length, v = √(2·μ·g·d), a lower-bound estimate used in accident reconstruction. Speed is in km/h by default (also m/s or mph), mass in kg and distances in m; dry asphalt has μ ≈ 0.7, wet ≈ 0.4 and ice ≈ 0.1. Everything is computed locally and deterministically, so it is instant and private. Ideal for automotive, driving-safety, fleet, telematics and accident-reconstruction app developers, stopping-distance and forensic tools, and physics education. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is vehicle braking; for general kinematics use a kinematics API and for an object on a slope an inclined-plane API.

#braking #stopping-distance #automotive #safety #physics #developer-tools
api.oanor.com/brake-api
Get an API key Try in playground → Contact provider

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

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

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

API health

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

Pricing

Pick a tier — billed monthly, cancel anytime.

Free

Free

  • 4,000 calls / month
  • 2 requests / second
  • Hard cap (429 above quota, no overage)
  • 4,000 calls/month
  • 2 req/sec
  • Stopping + braking force + skid speed
  • No credit card
Sign in to subscribe

Starter

€5.00 /month

  • 45,000 calls / month
  • 6 requests / second
  • Hard cap (429 above quota, no overage)
  • 45,000 calls/month
  • 6 req/sec
  • Reaction + braking, km/h/m/s/mph
  • Email support
Sign in to subscribe

Pro

€14.00 /month

  • 228,000 calls / month
  • 15 requests / second
  • Hard cap (429 above quota, no overage)
  • 228,000 calls/month
  • 15 req/sec
  • Telematics & reconstruction pipelines
  • Priority support
Sign in to subscribe

Mega

€45.00 /month

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

Built by

P
PremiumApi

Related APIs

Other APIs with overlapping tags.

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

Engine Displacement API

Internal-combustion engine maths as an API, computed locally and deterministically. The displacement endpoint computes an engine's swept volume from the bore, the stroke and the number of cylinders, V = (π/4)·bore²·stroke per cylinder, in cubic centimetres, litres and cubic inches, and classifies the bore-to-stroke geometry as oversquare, square or undersquare. The compression endpoint relates the compression ratio and the clearance volume, CR = (swept + clearance)/clearance — give the clearance to get the ratio or the ratio to get the clearance — and, with a boost pressure, estimates the effective compression ratio of a forced-induction engine. The power-to-weight endpoint computes the power-to-weight ratio in horsepower per tonne, kilowatts per tonne and watts per kilogram, the weight per horsepower, and, with a displacement, the specific output in horsepower per litre. Bore and stroke are in millimetres, volumes in cc, weight in kilograms and power in horsepower or kilowatts. Everything is computed locally and deterministically, so it is instant and private. Ideal for automotive, motorsport, motorcycle and engine-builder app developers, build-spec and tuning tools, and mechanical education. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is engine geometry and tuning; for EPA fuel-economy data use a fuel-economy API and for tyre sizes a tyre-calculator API.

api.oanor.com/engine-api

Towing Calculator API

Trailer-towing weight maths as an API, computed locally and deterministically. The tongue endpoint computes the tongue (hitch) weight as a percentage of the loaded trailer weight and reports the recommended 10–15 % range — too little tongue weight is the main cause of trailer sway. The capacity endpoint computes the maximum trailer weight a tow vehicle can pull, GCWR − curb weight − payload (the passengers and cargo in the vehicle), and checks a proposed trailer against it with the margin remaining. The payload endpoint computes the vehicle payload still available once the trailer is hitched, GVWR − curb weight − tongue weight, since the tongue weight presses down on the tow vehicle and counts against its payload rating. Everything is computed locally and deterministically, so it is instant and private. Ideal for RV, caravan, trailer and fleet apps, tow-vehicle matching and load-planning tools, and automotive calculators. Pure local computation — no key, no third-party service, instant. Live, nothing stored. Guidance only — follow the manufacturer's ratings. 3 endpoints. This is trailer-towing weights; for tyre size and rolling circumference use a tyre API.

api.oanor.com/towing-api

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

Frequently asked questions

Quick answers about pricing, quotas, and integration.

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