oanor
Iscriviti gratis
Mercata Prezzi Caratteristiche Accedi

API · /pace-api

Running Pace API

salutare 3,157 Abbonati

A running-pace calculator as an API. Work out pace and speed from a distance and a time (pace per kilometre and per mile, plus km/h, mph and m/s); compute the finish time from a distance and a target pace; predict your time at another distance using Peter Riegel's formula (T2 = T1 × (D2/D1)^1.06) — e.g. estimate a half-marathon from a 10K; and generate a split-time table for even pacing. Times accept seconds, M:SS or H:MM:SS. Perfect for running and fitness apps, race planning, training logs and pace bands. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 5 endpoints. Distinct from general unit conversion and from body-metric (BMI/BMR) health calculators.

#running #pace #fitness #sports #calculator #developer-tools
api.oanor.com/pace-api
Ottieni una chiave API Prova nel parco giochi → Contatta provider

Specifica leggibile dalle macchine, così gli agenti AI possono integrare questa API.

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

Individuazione: GET /api/index.json elenca ogni API.

Running Pace API — live data on the oanor API marketplace

API salute

salutare
Tempo di attività
100.00%
Sondaggi del server · 24 ore su 24
Latenza media
82 ms
Sondaggi del server · 24 ore su 24
Abbonati
3,157
attiva
Chiamate totali
95
ultimi 7 giorni
status Pagina di stato completa → · 15 sonde/24h

Prezzi

Scegli un livello: fatturazione mensile, annullamento in qualsiasi momento.

Free

Gratis

  • 1,035 chiamate/mese
  • 2 richieste/secondo
  • Tetto rigido (429 sopra la quota, nessuna eccedenza)
  • 1,035 calls/month
  • 2 req/sec
  • Pace + time + predict + splits
  • No credit card
Accedi per abbonarti

Starter

€0.75 /mese

  • 8,750 chiamate/mese
  • 8 richieste/secondo
  • Tetto rigido (429 sopra la quota, nessuna eccedenza)
  • 8.75k calls/month
  • 8 req/sec
  • km + mile, Riegel prediction
  • Email support
Accedi per abbonarti

Pro

€20.65 /mese

  • 138,500 chiamate/mese
  • 20 richieste/secondo
  • Tetto rigido (429 sopra la quota, nessuna eccedenza)
  • 138.5k calls/month
  • 20 req/sec
  • Fitness / race-app pipelines
  • Priority support
Accedi per abbonarti

Mega

€58.65 /mese

  • 730,000 chiamate/mese
  • 50 richieste/secondo
  • Tetto rigido (429 sopra la quota, nessuna eccedenza)
  • 730k calls/month
  • 50 req/sec
  • Platform scale
  • Dedicated SLA
Accedi per abbonarti

Costruito da

P
PremiumApi

Correlato APIs

Altro APIs con tag sovrapposti.

Swimming API — oanor API marketplace

Swimming API

Swimming maths as an API, computed locally and deterministically — the SWOLF, threshold-pace and per-100 m numbers a swimmer, coach or training app works a set out with. The swolf endpoint scores stroke efficiency for one length: SWOLF (swim + golf) = the strokes taken plus the seconds taken, and like golf lower is better — gliding further per stroke or swimming faster both cut it, so a 25 m length in 18 strokes and 30 s is a SWOLF of 48. Because it is pool-length and stroke dependent, the score is normalized to 25 m so lengths in different pools compare. The css endpoint computes Critical Swim Speed, the swimmer's threshold pace, from two all-out time trials: CSS = (distance1 − distance2) ÷ (time1 − time2) — the classic 400 m and 200 m test, where 6:00 and 2:50 give about 1.05 m/s, a 1:35 / 100 m threshold; training paces are then set as offsets from CSS, the swimmer's equivalent of a runner's threshold or an erg's 2 k pace. The pace endpoint gives speed and the per-100 m pace swimmers actually quote (time ÷ distance × 100), so 100 m in 1:30 is a 1:30 / 100 m pace at 1.11 m/s. Everything is computed locally and deterministically, so it is instant and private. Ideal for swim-training and coaching tools, lap-tracker and triathlon apps, and fitness calculators. Pure local computation — no key, no third-party service, instant. 3 compute endpoints. For running pace use a pace API; for indoor rowing a rowing API.

api.oanor.com/swimming-api

 Indoor Rowing API — oanor API marketplace

Indoor Rowing API

Indoor-rowing (Concept2 erg) maths as an API, computed locally and deterministically — the watts, split and calorie numbers a rower, coach or fitness app works a piece out with, using the published Concept2 relations. The split-to-watts endpoint turns a 500 m split into power: on an erg the power is fixed by the pace, not the stroke rate, so watts = 2.80 ÷ pace³ where the pace is the seconds per metre (the split ÷ 500) — a 2:00 split is about 202 W. Because power goes as the inverse cube of pace, small split gains cost a lot of watts: pulling 1:50 instead of 2:00 is roughly 270 W, not 220. The watts-to-split endpoint inverts it — pace = (2.80 ÷ watts)^(1/3), split = pace × 500 — so a target wattage maps to the split on the monitor and a rower's power compares directly with a cyclist's or any other watts figure. The calories endpoint applies the Concept2 calorie formula, Cal/hr = (watts × 4 × 0.8604) + 300, where the +300 is a fixed resting-metabolism term that makes the erg's count run higher than pure mechanical work; 200 W is about 988 Cal/hr, roughly 494 calories over 30 minutes. Everything is computed locally and deterministically, so it is instant and private. Ideal for rowing and erg training tools, coaching and leaderboard apps, and fitness calculators. Pure local computation — no key, no third-party service, instant. Concept2 model — a machine estimate, not lab calorimetry. 3 compute endpoints. For running pace use a pace API; for cycling a cycling API.

api.oanor.com/rowing-api

 Powerlifting Score API — oanor API marketplace

Powerlifting Score API

Powerlifting strength-score maths as an API, computed locally and deterministically — the Wilks, DOTS and IPF GL numbers a meet, gym or training app uses to compare lifters across bodyweights and sexes. The wilks endpoint gives the classic Wilks coefficient (1996) and score: total × 500 ÷ a fifth-order polynomial in bodyweight, with separate male and female curves — long the federation standard for "best lifter", a 100 kg man totalling 600 kg scores about 365. The dots endpoint gives the modern DOTS score (2019), the same total × 500 ÷ polynomial idea but fitted to updated data with a fourth-order curve that is fairer across the weight classes and not skewed to the middleweights, now the default in most raw meet software. The ipf-gl endpoint gives the International Powerlifting Federation's current GL Points (2020): 100 × total ÷ (A − B·e^(−C·bodyweight)), with separate constants for sex and for raw (classic) versus equipped lifting, the official metric at IPF championships. Everything is computed locally and deterministically, so it is instant and private. Ideal for meet-management and scoring software, gym leaderboards and training-log apps, and strength-sport tools. Pure local computation — no key, no third-party service, instant. 3 compute endpoints. For one-rep-max estimation and plate loading use a strength-training API.

api.oanor.com/powerlifting-api

 Barbell & Lifting API — oanor API marketplace

Barbell & Lifting API

Barbell- und Gewichtheber-Mathematik als API, lokal und deterministisch berechnet – die Plattenbeladungs- und Prozentzahlen, die ein Lifter, Trainer oder eine Fitness-App an der Hantelbank ausrechnet. Der Platten-Endpunkt löst das alltägliche Rätsel im Fitnessstudio, welche Platten auf jeder Seite für ein Zielgewicht aufgelegt werden müssen: 100 kg auf einer Standard-20-kg-Stange bedeuten 40 kg pro Seite, zuerst die schwersten als 25er und 15er; 102,5 kg fügt die 1,25-Mikroplatte hinzu; und wenn ein Ziel mit den vorhandenen Platten nicht erreichbar ist, lädt es die nächstmögliche Kombination und teilt das Defizit mit, sodass Sie nie raten müssen. Es funktioniert in Kilogramm oder Pfund (225 lb auf einer 45-lb-Stange sind zwei 45er pro Seite), mit einem benutzerdefinierten Stangengewicht und einem benutzerdefinierten Plattensatz. Der Prozent-Endpunkt wandelt ein One-Rep-Max in das tatsächlich zu ladende Arbeitsgewicht um: 80 % eines 100-kg-Maximums sind 80 kg, und die Abfrage eines Fünf-Wiederholungs-Gewichts ergibt etwa 85,7 kg über die Epley-Formel (1RM = Gewicht × (1 + Wiederholungen ÷ 30)) – fünf Wiederholungen liegen nahe 86 % des Maximums, zehn Wiederholungen nahe 75 %. Der Aufwärm-Endpunkt baut eine Rampe von der leeren Stange bis zum Arbeitssatz bei etwa 40, 55, 70 und 85 %, jede auf einen ladbaren Schritt gerundet, wobei die Wiederholungszahl sinkt, wenn die Stange schwerer wird. Alles wird lokal und deterministisch berechnet, also sofort und privat. Ideal für Entwickler von Fitnessstudio-, Krafttrainings-, Powerlifting- und Fitness-Apps, Workout-Logger und Coaching-Tools sowie für Entwickler von intelligenten Hantelbänken und Plattenrechnern. Reine lokale Berechnung – kein Key, kein Drittanbieter-Service, sofort. Exakte Mathematik, keine Simulation. Live, nichts gespeichert. 3 Compute-Endpunkte. Für die Schätzung des One-Rep-Max aus einem Satz verwenden Sie eine Strength-API.

api.oanor.com/barbell-api

Domande frequenti

Risposte rapide su prezzi, quote e integrazione.

Come ottengo una chiave API per Running Pace API?
Registrati gratuitamente su oanor.com, genera una chiave API dalla dashboard sviluppatore e chiama Running Pace API con l'header x-oanor-key. Nessuna carta di credito richiesta per il piano gratuito.
Qual è il limite di velocità di Running Pace 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 Running Pace API?
Running Pace API ha un piano gratuito con 100 chiamate / mese. I piani a pagamento partono da €0.75 / 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.
Running Pace API è conforme al GDPR?
Tutte le richieste a Running Pace 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/pace-api/SOME_PATH \
  -H "x-oanor-key: oanor_test_..."
const res = await fetch("https://api.oanor.com/pace-api/SOME_PATH", {
  headers: { "x-oanor-key": "oanor_test_..." }
});
const data = await res.json();
$ch = curl_init("https://api.oanor.com/pace-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/pace-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.

Accedi

Nuova discussione

/ 4000

📌 Fissato 🔒 Bloccato

·

· ·

/ 4000

🔒 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.

Accedi

Apri nuovo ticket

Descrivi cosa ti serve. Il team del provider riceve un'email e risponde sulla pagina del ticket.

  • Nessun ticket per questa API.

Abbonamento attivo: le chiamate possono iniziare subito.

Invia la tua prima richiesta —

Abbonamento attivo: copia uno snippet e avvia la tua prima chiamata.