Gearing metrics + speed
API · /bikegear-api
Bicycle Gear API
salutare
4,493 Abbonati
Bicycle gearing maths as an API, computed locally and deterministically. The gear endpoint takes a chainring and cog tooth count and a wheel size and returns every common gearing metric: the gear ratio, gear inches (the classic measure — ratio times wheel diameter in inches), the gain ratio (Sheldon Brown's crank-length-aware measure), the development or rollout (metres travelled per crank revolution), and the road speed at a chosen cadence in km/h and mph. The speed endpoint converts between a gear-and-cadence and road speed in either direction — the speed at a cadence, or the cadence needed for a target speed. The table endpoint builds a gear chart: give one or more chainrings and a cassette of cogs and it returns a matrix of gear inches, development, gain ratio or ratio for every combination — ideal for visualising a drivetrain. Wheel size can be a preset (700x25c, 26-inch, 29er and more) or an exact rolling circumference in millimetres, and crank length is configurable for the gain ratio. Everything is computed locally and deterministically, so it is instant and private. Ideal for cycling apps and bike-fit tools, drivetrain and gear-ratio planners, and bike-shop and component sites. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is bicycle gearing; for cycling power, FTP and training zones use a cycling API.
api.oanor.com/bikegear-api
API salute
salutare- Tempo di attività
- 100.00%
- Sondaggi del server · 24 ore su 24
- Latenza media
- 90 ms
- Sondaggi del server · 24 ore su 24
- Abbonati
- 4,493
- attiva
- Chiamate totali
- 40
- ultimi 7 giorni
Prezzi
Scegli un livello: fatturazione mensile, annullamento in qualsiasi momento.
Free
Gratis
- 10,935 chiamate/mese
- 2 richieste/secondo
- Tetto rigido (429 sopra la quota, nessuna eccedenza)
- 10,935 calls/month
- 2 req/sec
- Gear + speed + table
- No credit card
Starter
€12.45 /mese
- 20,550 chiamate/mese
- 8 richieste/secondo
- Tetto rigido (429 sopra la quota, nessuna eccedenza)
- 20.55k calls/month
- 8 req/sec
- Gain ratio + gear charts
- Email support
Pro
€32.35 /mese
- 255,500 chiamate/mese
- 20 richieste/secondo
- Tetto rigido (429 sopra la quota, nessuna eccedenza)
- 255.5k llamadas/mes
- 20 req/seg
- Tuberías de transmisión / bicicleta
- Soporte prioritario
Mega
€70.35 /mese
- 1,320,000 chiamate/mese
- 50 richieste/secondo
- Tetto rigido (429 sopra la quota, nessuna eccedenza)
- 1.32M llamadas/mes
- 50 req/seg
- Escala de plataforma
- SLA dedicado
Costruito da
Correlato APIs
Altro APIs con tag sovrapposti.
Bike-Share API
Every public bike-share and e-scooter system in the world as an API — 1,500+ systems across 48 countries from the MobilityData GBFS catalog, plus LIVE station availability. Browse and search the systems catalog by country or name (Citi Bike, Vélib', Divvy, Blue Bikes, Capital Bikeshare, …), look up a system with its GBFS feed URLs, and fetch real-time station data — each station's name, location, capacity and how many bikes and docks are free right now — or find the nearest stations to any coordinate by great-circle distance. Ideal for trip-planning, mobility, maps and smart-city apps. Catalog data from MobilityData; live availability from each operator's official GBFS feed.
api.oanor.com/bikeshare-api
Spoke Length & Wheel API
Bicycle wheel-building maths as an API, computed locally and deterministically — the spoke-length and tension numbers a wheelbuilder laces a wheel by. The spoke endpoint runs the classic spoke-length formula from the hub and rim geometry: L = √(R² + r² + f² − 2·R·r·cos θ) − hole ÷ 2, where R is half the effective rim diameter (ERD), r is half the hub flange diameter, f is the centre-to-flange offset and θ = crosses × 720° ÷ spokes — so a 602 mm ERD rim on a 45 mm flange at 35 mm offset, 32 spokes laced 3-cross (a 67.5° crossing angle), needs a 293.9 mm spoke. It handles radial (0-cross) builds and computes the drive and non-drive sides separately from their own offsets, since a dished wheel’s two sides differ. The bracing endpoint gives each side’s bracing angle = atan(offset ÷ (ERD/2)) — the lever that resists side loads — and the resulting tension ratio, because the side with the smaller offset must carry higher tension, which is why a rear wheel’s non-drive spokes (often only about half the drive-side tension) go slack first. Everything is computed locally and deterministically, so it is instant and private. Ideal for bike-shop, wheelbuilding, cycling and bike-fit app developers, spoke-calculator and build-sheet tools, and component-database software. Pure local computation — no key, no third-party service, instant. Millimetres. Live, nothing stored. 2 compute endpoints. For gear inches or gearing use a bicycle-gear API.
api.oanor.com/spokelength-api
API de rendimiento ciclista
Matemáticas de rendimiento ciclista como API. El endpoint de potencia estima la potencia en vatios necesaria para pedalear a una velocidad dada en una pendiente determinada, a partir de un modelo físico — resistencia a la rodadura, gravedad en la subida y arrastre aerodinámico — con valores predeterminados sensatos que puedes anular (coeficiente de resistencia a la rodadura, área de arrastre CdA, densidad del aire, eficiencia de la transmisión y viento en contra), y desglosa la potencia en sus componentes de rodadura, gravedad y aerodinámica, además de vatios por kilogramo. El endpoint ftp-zones convierte una Potencia Funcional Umbral en las siete zonas de entrenamiento de Coggan, desde recuperación activa hasta potencia neuromuscular, como rangos de vatios. El endpoint vam calcula el VAM — metros de ascenso vertical por hora, la métrica de velocidad de escalada — ya sea a partir de la elevación ganada y el tiempo, o de la velocidad y la pendiente. Todo se calcula local y determinísticamente, por lo que es instantáneo y privado. Ideal para aplicaciones de ciclismo y entrenamiento, ordenadores de bicicleta y herramientas de medidores de potencia, entrenamiento, y análisis de rutas y subidas. Cálculo local puro — sin clave, sin servicio de terceros, instantáneo. En vivo, nada almacenado. 4 endpoints. Esto son matemáticas de ciclismo; para ritmo de carrera usa una API de ritmo y para zonas de frecuencia cardíaca de entrenamiento usa una API de frecuencia cardíaca.
api.oanor.com/cycling-api
Gear Ratio API
Gear-train ratio, speed and torque maths as an API, computed locally and deterministically. The ratio endpoint computes the gear ratio of a single pair from the driver and driven tooth counts (or pitch diameters), ratio = N_driven/N_driver, classifies it as a reduction (more torque, less speed) or an overdrive, and — given an input speed and torque — returns the output speed (input/ratio) and the output torque (input·ratio·efficiency). The train endpoint computes a compound gear train: the overall ratio is the product of the individual stage ratios, and it returns each stage ratio, the output speed and torque, noting that idler gears change only the direction of rotation, not the ratio. The solve endpoint finds the missing one of the input speed, the output speed and the ratio from the other two — for example, the ratio needed to drop a 1500 rpm motor to a 500 rpm output. Everything is computed locally and deterministically, so it is instant and private. Ideal for drivetrain, robotics and machine-design tools, gearbox and transmission selection, bicycle and vehicle gearing, and mechanical-engineering education. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is gear-train ratio and torque; for spur-gear tooth geometry use a spur-gear API.
api.oanor.com/gearratio-api
Domande frequenti
Risposte rapide su prezzi, quote e integrazione.
Come ottengo una chiave API per Bicycle Gear API?
Registrati gratuitamente su oanor.com, genera una chiave API dalla dashboard sviluppatore e chiama Bicycle Gear API con l'header x-oanor-key. Nessuna carta di credito richiesta per il piano gratuito.
Qual è il limite di velocità di Bicycle Gear API?
Il piano gratuito consente 1 richiesta al secondo. I piani a pagamento arrivano fino a 50 richieste al secondo nel piano Mega. I limiti rigorosi restituiscono HTTP 429 oltre la quota — nessuna spesa imprevista.
Quanto costa Bicycle Gear API?
Bicycle Gear API ha un piano gratuito con 100 chiamate / mese. I piani a pagamento partono da €12.45 / mese con quote più alte e limiti di velocità più rapidi.
Posso cancellare l'abbonamento in qualsiasi momento?
Sì. I piani sono fatturati mensilmente e puoi cancellare in qualsiasi momento dalla dashboard di fatturazione. Nessun contratto a lungo termine e nessuna penale di cancellazione.
Bicycle Gear API è conforme al GDPR?
Tutte le richieste a Bicycle Gear API passano attraverso il nostro gateway in UE. La tua chiave upstream non lascia mai il nostro server e nessun dato personale viene condiviso con il fornitore upstream oltre alla richiesta inviata.
Scegli un endpoint dall'elenco a sinistra per visualizzarne i dettagli e provarlo.
Frammenti di codice
Iscriviti per ottenere una chiave API, quindi chiama qualsiasi percorso sotto il tuo slug.
curl https://api.oanor.com/bikegear-api/SOME_PATH \
-H "x-oanor-key: oanor_test_..."const res = await fetch("https://api.oanor.com/bikegear-api/SOME_PATH", {
headers: { "x-oanor-key": "oanor_test_..." }
});
const data = await res.json();$ch = curl_init("https://api.oanor.com/bikegear-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/bikegear-api/SOME_PATH",
headers={"x-oanor-key": "oanor_test_..."},
)
print(r.json())Valutazioni
Accedi per votare.
Nessuna recensione ancora.
Discussione
Fai domande, condividi consigli, ricevi risposte dal provider e dagli altri sviluppatori. Pubblico — chiunque può leggere.
Accedi per scrivere o rispondere.
AccediNuova discussione
📌 Fissato
🔒 Bloccato
·
·
·
-
Risposta del provider
🔒 Discussione bloccata — non si può più rispondere.
-
·
- Nessuna discussione — inizia tu.
Supporto
Supporto privato 1:1 con il provider — fatturazione, integrazione, account. Solo tu e il team del provider vedete questi thread.
Accedi per aprire un ticket di supporto.
AccediApri nuovo ticket
Descrivi cosa ti serve. Il team del provider riceve un'email e risponde sulla pagina del ticket.
-
·
Urgente - Nessun ticket per questa API.