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.

API salute

salutare
Tempo di attività
100.00%
Sondaggi del server · 24 ore su 24
Latenza media
87 ms
Sondaggi del server · 24 ore su 24
Abbonati
3,157
attiva
Chiamate totali
70
ultimi 7 giorni
status Pagina di stato completa → · 30 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.

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

Body Fat API

Body-fat-percentage and body-composition maths as an API, computed locally and deterministically. The navy endpoint applies the US Navy circumference method — for men %BF = 495/(1.0324 − 0.19077·log10(waist − neck) + 0.15456·log10(height)) − 450, and for women a formula that adds the hip measurement — to estimate body fat from a tape measure alone, returning the percentage and the fitness category (essential, athletes, fitness, acceptable or obese); a man of 178 cm with a 40 cm neck and 90 cm waist reads about 18.7 %. The deurenberg endpoint gives the BMI-based estimate %BF = 1.20·BMI + 0.23·age − 10.8·(1 if male) − 5.4 from BMI or weight and height plus age. The composition endpoint splits a total weight into fat mass and lean (fat-free) mass from a body-fat percentage. Circumferences and height are in centimetres and weight in kilograms. Everything is computed locally and deterministically, so it is instant and private. Ideal for fitness, wellness, gym, nutrition, body-tracking and health-education app developers, body-composition and progress-tracking tools, and coaching software. These are estimation formulas, not a substitute for DEXA or professional assessment. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is body-fat percentage; for body-mass index use a BMI API and for basal metabolic rate a BMR API.

api.oanor.com/bodyfat-api

Calorie Burn API

Exercise calorie-burn maths as an API, computed locally and deterministically with the MET (metabolic-equivalent) method. The activity endpoint computes the calories burned by an activity, calories = MET × weight × hours, taking the MET value directly or from a named-activity table (walking, running, cycling, swimming, HIIT, rowing, yoga, weightlifting and more), and returns the calories per minute. The steps endpoint turns a step count into distance and calories: the stride is estimated from height (about 0.415 × height for walking, 0.65 for running), the distance is steps × stride, and the energy is the distance times bodyweight times a net cost of roughly 0.5 kcal/kg/km walking or 1.0 running. The duration endpoint works backwards, giving the minutes of an activity needed to burn a target number of calories. Everything is computed locally and deterministically, so it is instant and private. Ideal for fitness, activity-tracking and weight-management app developers, workout and step-counter tools, and wellness dashboards. Pure local computation — no key, no third-party service, instant. Live, nothing stored. Estimates only. 3 endpoints. This is activity energy expenditure; for resting metabolism and TDEE use a BMR API.

api.oanor.com/calorieburn-api

Hydration Calculator API

Hydration and fluid-balance maths as an API, computed locally and deterministically. The daily endpoint estimates the daily fluid need from bodyweight (about 35 ml per kilogram), the minutes of exercise (about 12 ml per minute) and the climate (hot adds 500 ml, very hot 1000 ml, cold subtracts 200 ml), reported in millilitres, litres and 250 ml glasses. The sweat endpoint computes the sweat rate and the degree of dehydration from a before-and-after body weight, the fluid drunk and the duration — sweat loss = (pre − post) + intake − urine, with 1 kg of lost mass treated as 1 litre, and it flags when losses pass the 2 % of body mass where performance falls off. The rehydrate endpoint computes the post-exercise rehydration target, about 1.5 times the fluid deficit to cover ongoing urine losses, with a sodium note for larger losses. Everything is computed locally and deterministically, so it is instant and private. Ideal for fitness, sports and wellness app developers, endurance-training and hydration-reminder tools, and health dashboards. Pure local computation — no key, no third-party service, instant. Live, nothing stored. General guidance, not medical advice. 3 endpoints. This is fluid balance; for basal calories use a BMR API and for heart-rate zones use a heart-rate API.

api.oanor.com/hydration-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.