Skip to main content

Quickstart

This guide gets you from zero to a working nutrition calculation in under 5 minutes.

1. Get your API key

Self-serve (most builders): sign up at saturday.fit/api — $5.39/month, no contract. Your key is revealed once after checkout and emailed to you. An AI agent can do this for you too: POST /v1/signup (no auth) returns a hosted checkout link. Not sure self-serve is your lane? See Getting Access. Platform partners: keys come with your agreement — contact api@saturday.fit. Partner sandbox keys start with sk_test_ and work against test data with no rate limit concerns.
Treat your key like a password — it authenticates every request and spends your daily call allowance.

2. Make your first calculation

The core of Saturday’s API is the nutrition calculation endpoint. It takes activity parameters and returns a fuel prescription.

Install an SDK (optional)

Saturday provides official SDKs for Python and TypeScript:

3. Read the response

A successful response returns a fuel prescription with safety metadata:
Key fields to understand:
Safety data is never gated. Every response includes full safety metadata regardless of subscription status. Bad hydration can cause hyponatremia — a potentially fatal condition. Safety information is always free and complete.

4. Understand teaser vs. full responses

The response above shows full precision numbers because it’s from a sandbox key. In production, responses depend on the athlete’s subscription status: Teaser responses include a subscription_cta field:
See Freemium Model for the full details.

5. Next steps

You’ve just calculated a nutrition prescription with minimal inputs. From here:
1

Create an athlete profile

Athletes — Store athlete settings (weight, sweat level, preferences) for more accurate calculations.
2

Understand safety

Safety — Learn about Saturday’s safety model and why it matters.
3

Track activities

Activities — Create activities, attach prescriptions, and collect feedback.
4

Go to production

Authentication — Swap your sk_test_ key for a sk_live_ key when you’re ready.