The exercise databaseyour fitness appactually wants.
1,324 exercises. Structured metadata. Sub-50 ms p99 from a global edge. Free tier. Predictable USD pricing. Cancel anytime.
Live demo
A real, live response
from the production API.
- Global infra
- Per-key analytics
- 99.9% on paid tiers
- Cancel anytime
{
"id": "0001",
"name": "3/4 Sit-up",
"bodyPart": "Waist",
"target": "Abs",
"equipment": "Body Weight",
"secondaryMuscles": [
"Hip Flexors",
"Lower Back"
],
"instructions": [
"Lie flat on your back with your knees bent and feet flat on the ground.",
"Place your hands behind your head with your elbows pointing outwards.",
"Engaging your abs, slowly lift your upper body off the ground, curling forward until your torso is at a 45-degree angle.",
"Pause for a moment at the top, then slowly lower your upper body back down to the starting position.",
"Repeat for the desired number of repetitions."
]
}01
Predictable pricing
Flat monthly tiers in USD. No surprise overage like RapidAPI. No quote calls.
02
Built worldwide
Global edge, multi-region read replicas, EU data residency available on request.
03
Honest free tier
100 requests / month — enough to verify the integration. No card to start.
/// SDK
SDK in any language
Plain REST + JSON. Bearer-token auth. Six languages, copy-pasteable.
shell
curl
node
JavaScript
py
Python
go
Go
rb
Ruby
php
PHP
01What does the API return?
Structured exercise metadata: name, body part, target muscle, equipment, instructions, MET, secondary muscles. GIF previews are sold separately through the marketplace.
02Is there a free tier?
Yes — 100 requests per month after free signup. Enough to verify the integration, then upgrade when you ship.
03Can I cancel anytime?
Yes — self-serve cancellation via Stripe Customer Portal. Your plan stays active through the end of the current billing period; no mid-period refunds.
04Where is data hosted?
Frankfurt by default. EU jurisdiction. We can move you to a different region on Pro+ if compliance requires.
05How do you prevent dataset leakage?
Per-key rate limits, sequential-ID scrape detection on free tier, and per-customer canary fields embedded in responses for forensic identification.