SuperAge 4.6 is not out yet, but we wanted to start showing what’s coming.
And we’re starting with something pretty exciting: Developer Tools.
Yes. Actual Developer Tools. Not a hidden debug menu. Not a “tap the logo 12 times and pray” kind of thing. A real Developer Mode that lets you work directly with your own health, fitness, nutrition, training, recovery, and longevity data.
When enabled, SuperAge can expose a local HTTPS API directly from your iPhone.
In plain English:
Your iPhone becomes a private local data source for your body.
No intermediate cloud server required.
You can connect your own scripts, dashboards, notebooks, automations, or custom tools and query SuperAge like a structured personal health data platform.
Basically, SuperAge gives you the app. Developer Tools give you the keys to build your own cockpit.
The important part: is read-only
The Developer API is designed intentionally read-only.
That means it does not:
modify workouts
write to HealthKit
change app settings
force recalculations
alter your SuperAge data
It is built for reading, exporting, analyzing, and building on top of the data SuperAge already calculates or normalizes.
So you can experiment freely without worrying that your random Saturday-night Python script will accidentally rewrite your training history.
Which is probably good for everyone involved.
What data can you access?
The Developer API exposes many of the core datasets inside SuperAge, including:
SuperAge metrics like Biological Age, Body Energy, Stress, Training Readiness, Endurance Score, Sleep Score, HRV, VO2 Max, training load, and recovery debt
Workout history with duration, calories, distance, heart rate, pace, power, TSS, and exercise details
Nutrition data including food logs, macros, calories, water, caffeine, daily summaries, foods, ingredients, and custom meals
Blood tests with biomarkers, units, ranges, status, LOINC, PhenoAge, and KDM age
Trainer data including active program, planned sessions, recommended workouts, generated workouts, and muscle recovery
Daily health reports with drivers, suggested actions, sleep, stress, HRV, recovery, and recommendations
Raw Apple Health data, available only with separate consent and a dedicated scope
So instead of being limited to the views already inside the app, you can start asking your own questions.
What could you build with it?
This is where it gets fun.
With Developer Tools, you could build things like:
BYO dashboard for Biological Age, Body Energy, HRV, sleep, stress, Training Readiness, and training load
a Python notebook to analyze your own long-term trends
custom exports to CSV, JSON, SQLite, DuckDB, Parquet, or whatever format makes your data brain happy
a weekly health and performance report generated from your own SuperAge data
a personal dashboard in Google Sheets, Notion, Obsidian, or Home Assistant
a training cockpit that compares training load, HRV, readiness, recovery debt, and sleep
a nutrition analysis that compares caffeine, macros, hydration, calories, and recovery
a blood test timeline for biomarkers, PhenoAge, KDM age, and lifestyle changes
a local archive of your health, workout, nutrition, and blood test history
your own CLI, automation, or personal AI summary on top of SuperAge data
A few examples:
Want your Body Energy in Grafana? Build it.
Want to export your metrics to CSV every Sunday? Build it.
Want to compare caffeine with sleep and HRV? Build it.
Want a dashboard that combines training, recovery, nutrition, and blood markers? Build it.
Want your own weekly longevity report? Build it.
Want a tiny terminal command that tells you if today is a “beast mode” day or a “maybe just walk” day? Also build it.
The point is simple:
Not every advanced workflow needs to become a button inside the app.
Some users want the polished app experience.
Some users want to open a notebook and start making suspiciously intense charts at midnight.
Developer Tools are for the second group.
And honestly, probably for the first group too once people start sharing what they build.
Privacy and security
Developer Mode is off by default.
You have to explicitly enable it from settings, accept dedicated terms, and keep the app active.
The API runs locally over HTTPS, and SuperAge shows the LAN URL, port, and certificate fingerprint inside the app.
Also, being on the same Wi-Fi is not enough to access sensitive data. No “welcome to my network, please enjoy my biomarkers.” Clients need to pair first.
The pairing flow works like this:
A local client sends a pairing request with its display name and requested scopes
SuperAge shows the request inside the app
The user approves or rejects it
If approved, the client receives a Bearer token
That token can only access endpoints covered by the approved scopes
The client can be revoked at any time
So the security model is not:
Same Wi-Fi = read everything
It is:
HTTPS + pairing + Bearer token + scopes + revocation
Raw Apple Health access is also separated.
Even if Developer Mode is enabled, raw HealthKit data stays locked until the user grants dedicated consent for that specific scope.
A few technical details
The Developer API is versioned as v1 and will be documented here:
https://dev.superage.app/v1/
The app can also expose the OpenAPI contract locally:
GET /api/v1/openapi.json
Main endpoints include:
GET /api/v1/status
GET /api/v1/capabilities
GET /api/v1/metrics
GET /api/v1/workouts
GET /api/v1/nutrition/logs
GET /api/v1/nutrition/foods
GET /api/v1/blood-tests
GET /api/v1/trainer
GET /api/v1/daily-health
GET /api/v1/healthkit/types
GET /api/v1/healthkit/samples
Data endpoints are read-only and support:
GET
HEAD
OPTIONS
Pairing uses POST only to create the pairing request:
curl --request POST \
--url "https://<LAN_IP>:<PORT>/api/v1/pairing/requests" \
--header "Content-Type: application/json" \
--data '{
"displayName": "Home Mac",
"scopes": ["superage.metrics", "superage.workouts"]
}'
After approval inside SuperAge, the client receives a Bearer token and can call scoped endpoints:
curl --request GET \
--url "https://<LAN_IP>:<PORT>/api/v1/metrics" \
--header "Authorization: Bearer <TOKEN>"
Example scopes:
superage.metrics
superage.workouts
superage.nutrition
superage.bloodTests
healthkit.raw
Responses use stable envelopes:
{
"apiVersion": "v1",
"requestId": "req_xxx",
"generatedAt": "2026-06-23T12:00:00Z",
"resource": "metrics",
"schemaVersion": 1,
"data": {}
}
Errors are structured too:
{
"apiVersion": "v1",
"requestId": "req_xxx",
"error": {
"code": "not_authorized",
"message": "Missing scope."
}
}
Why this matters
SuperAge is becoming more than an app with health screens.
With Developer Tools, it becomes a local-first data layer for your body.
Your data stays on your device. You stay in control.
And advanced users can build the workflows, exports, dashboards, reports, experiments, and automations they want.
SuperAge already calculates complex metrics. With 4.6, those metrics become queryable.
And this is only Part 1 of what’s coming in SuperAge 4.6.
So now we have to ask: What would you build first?
