gevetyAccess your Gevety health data - biomarkers, healthspan scores, biological age, supplements, activities, daily actions, 90-day health protocol, upcoming test...
You have access to the user's health data from Gevety via the REST API. Use web_fetch to retrieve their biomarkers, healthspan scores, and wearable statistics.
If this is the user's first time using Gevety, guide them through setup:
gvt_)~/.clawdbot/clawdbot.json:{
"skills": {
"entries": {
"gevety": {
"apiKey": "gvt_your_token_here"
}
}
}
}After adding the token, they'll need to restart Clawdbot for changes to take effect.
All requests require Bearer authentication. Use the GEVETY_API_TOKEN environment variable:
Authorization: Bearer $GEVETY_API_TOKENBase URL: https://api.gevety.com
The API preserves biomarker specificity. Fasting and non-fasting variants are distinct:
| Input Name | API Returns | Notes |
|------------|-------------|-------|
| CRP, C-Reactive Protein | CRP or C-Reactive Protein | Standard CRP (LOINC 1988-5) |
| hsCRP, hscrp, Cardio CRP | hs-CRP | High-sensitivity CRP (LOINC 30522-7) |
| Glucose, Blood Glucose | Glucose | Generic/unspecified glucose |
| Fasting Glucose, FBS, FBG | Glucose Fasting | Fasting-specific glucose |
| Insulin, Serum Insulin | Insulin | Generic/unspecified insulin |
| Fasting Insulin | Insulin Fasting | Fasting-specific insulin |
| IG | Immature Granulocytes | Expanded for clarity |
| Vitamin D, 25-OH Vitamin D | Vitamin D | |
| LDL, LDL Cholesterol | LDL Cholesterol | |
Important: The API no longer forces fasting assumptions. If a lab report says "Glucose" without specifying fasting, it returns as "Glucose" (not "Fasting Glucose"). This preserves the original context from your lab results.
Always call this first to discover what health data exists.
GET /api/v1/mcp/tools/list_available_dataReturns:
biomarkers: List of tracked biomarkers with test counts and latest dateswearables: Connected devices and available metricsinsights: Whether healthspan score is calculated, axis scores availabledata_coverage: Percentage of recommended biomarkers tracked (0-100)Overview of the user's health status.
GET /api/v1/mcp/tools/get_health_summaryReturns:
overall_score: Healthspan score (0-100)overall_status: OPTIMAL, GOOD, SUBOPTIMAL, or NEEDS_ATTENTIONtrend: IMPROVING, STABLE, or DECLININGaxis_scores: Scores for each health dimension (metabolic, cardiovascular, etc.)top_concerns: Biomarkers needing attentionscoring_note: Explanation when overall score differs from axis scores (e.g., "Overall healthspan is high, but Inflammation axis needs attention")Note on scores: The overall healthspan score is a weighted composite. It's possible to have a high overall score while one axis is low (or vice versa). The scoring_note field explains these situations.
Get detailed history for a specific biomarker.
GET /api/v1/mcp/tools/query_biomarker?biomarker={name}&days={days}Parameters:
biomarker (required): Name or alias (e.g., "vitamin d", "ldl", "hba1c", "crp")days (optional): History period, 1-730, default 365Returns:
canonical_name: Standardized biomarker name (see table above)history: Array of test results with dates, values, units, flagslatest: Most recent resulttrend: Direction (IMPROVING, STABLE, DECLINING) and percent changeoptimal_range: Evidence-based optimal valuesTip: If biomarker not found, the response includes did_you_mean suggestions.
Daily metrics from connected wearables (Garmin, Oura, Whoop, etc.).
GET /api/v1/mcp/tools/get_wearable_stats?days={days}&metric={metric}Parameters:
days (optional): History period, 1-90, default 30metric (optional): Focus on specific metric (steps, hrv, sleep, etc.)Returns:
connected_sources: List of connected wearable platformsdaily_metrics: Per-day data (steps, resting HR, HRV, sleep, recovery)summaries: Aggregated stats with averages, min, max, trendsGet ranked health improvement opportunities with estimated healthspan impact.
GET /api/v1/mcp/tools/get_opportunities?limit={limit}&axis={axis}Parameters:
limit (optional): Max opportunities to return, 1-50, default 10axis (optional): Filter by health axis (metabolic, cardiovascular, etc.)Returns:
opportunities: Ranked list of improvement opportunitiestotal_opportunity_score: Total healthspan points availabletotal_years_estimate: Estimated years of healthy life if all optimizedhealthspan_score: Current healthspan scoreEach opportunity includes:
biomarker: Standardized biomarker namecurrent_value / optimal_value: Where you are vs targetopportunity_score: Healthspan points gained if optimizedyears_estimate: Estimated healthy years gainedpriority: Rank (1 = highest impact)Calculate biological age using validated algorithms (PhenoAge, Light BioAge).
GET /api/v1/mcp/tools/get_biological_ageReturns:
result: Biological age calculation (if available)biological_age: Calculated biological agechronological_age: Calendar ageage_acceleration: Difference (positive = aging faster)algorithm: Which algorithm was usedbiomarkers_used: Biomarkers that contributedinterpretation: What the result meansavailable: Whether calculation was possiblereason: Why not available (if applicable)upgrade_available: Can unlock better algorithm with more dataupgrade_message: What additional tests would helpGet the user's supplement stack.
GET /api/v1/mcp/tools/list_supplements?active_only={true|false}Parameters:
active_only (optional): Only show currently active supplements, default falseReturns:
supplements: List of supplements with dosage, frequency, durationactive_count: Number of currently active supplementstotal_count: Total supplements trackedEach supplement includes:
name: Supplement namedose_text: Formatted dosage (e.g., "1000 mg daily", "200mg EPA + 100mg DHA daily")is_active: Currently takingduration_days: How long on this supplementNote: For multi-component supplements (like fish oil), dose_text shows all components (e.g., "200mg EPA + 100mg DHA daily").
Get workout/activity history from connected wearables.
GET /api/v1/mcp/tools/get_activities?days={days}&activity_type={type}Parameters:
days (optional): History period, 1-90, default 30activity_type (optional): Filter by type (running, cycling, strength, etc.)Returns:
activities: List of workouts with metricstotal_count: Number of activitiestotal_duration_minutes: Total workout timetotal_distance_km: Total distance coveredtotal_calories: Total calories burnedEach activity includes:
activity_type: Type (running, cycling, swimming, etc.)name: Activity namestart_time: When it startedduration_minutes: How longdistance_km: Distance (if applicable)calories: Calories burnedavg_hr / max_hr: Heart rate datasource: Where the data came from (garmin, strava, etc.)Get the user's action checklist for today.
GET /api/v1/mcp/tools/get_today_actions?timezone={timezone}Parameters:
timezone (optional): IANA timezone (e.g., "America/New_York"), default UTCReturns:
effective_date: The date being queried in user's timezonetimezone: Timezone used for calculationwindow_start / window_end: Day boundaries (ISO datetime)actions: List of today's actionscompleted_count / total_count: Completion statscompletion_pct: Numeric completion percentage (0-100)last_updated_at: Cache staleness indicatorEach action includes:
action_id: Stable ID for deep-linkingtitle: Action titleaction_type: Type (supplement, habit, diet, medication, test, procedure)completed: Whether completed todayscheduled_window: Time window (morning, afternoon, evening, any)dose_text: Dosage info if applicable (e.g., "1000 mg daily")Get the user's 90-day health protocol with top priorities.
GET /api/v1/mcp/tools/get_protocolReturns:
protocol_id: Stable protocol IDphase: Current phase (week1, month1, month3)days_remaining: Days until protocol expiresgenerated_at / last_updated_at: Timestampstop_priorities: Top 5 health priorities with reasoningkey_recommendations: Diet and lifestyle action itemstotal_actions: Total actions in protocolEach priority includes:
priority_id: Stable ID (same as rank)rank: Priority rank (1 = highest)biomarker: Standardized biomarker namestatus: Current status (critical, concerning, suboptimal, optimal)target: Target value with unitcurrent_value / unit: Current measured valuemeasured_at: When this biomarker was last measuredwhy_prioritized: Explanation for why this is prioritizedNote: If no protocol exists, returns a helpful error with suggestion to generate one at gevety.com/protocol.
Get tests that are due or recommended based on biomarker history and AI recommendations.
GET /api/v1/mcp/tools/get_upcoming_testsReturns:
tests: List of upcoming tests sorted by urgencyoverdue_count: Number of overdue testsdue_soon_count: Tests due within 30 daysrecommended_count: AI-recommended teststotal_count: Total number of upcoming testsEach test includes:
test_id: Stable ID for deep-linking (format: panel_{id} or recommended_{id})name: Test or panel nametest_type: Type (panel, biomarker, recommended)urgency: Priority level (overdue, due_soon, recommended)due_reason: Why this test is needed (e.g., "Due 2 weeks ago", "AI recommendation")last_tested_at: When this was last tested (if applicable)biomarkers: List of biomarkers included (for panels)| Range | Status | Meaning |
|-------|--------|---------|
| 80-100 | OPTIMAL | Excellent health optimization |
| 65-79 | GOOD | Above average, minor improvements possible |
| 50-64 | SUBOPTIMAL | Room for improvement |
| <50 | NEEDS_ATTENTION | Several areas need focus |
Each health dimension is scored independently:
Important: It's possible to have a high overall score with one low axis score (or vice versa). The scoring_note field in get_health_summary explains these situations.
| Label | Meaning |
|-------|---------|
| OPTIMAL | Within evidence-based ideal range |
| NORMAL | Within lab reference range |
| SUBOPTIMAL | Room for improvement |
| HIGH/LOW | Outside lab reference range |
| CRITICAL | Needs immediate medical attention |
list_available_data to see what's trackedget_health_summary for the overall picturescoring_note is present, explain the score discordancequery_biomarker?biomarker=vitamin dquery_biomarker?biomarker=crp (returns as "CRP" or "hs-CRP" depending on lab)get_wearable_stats?metric=sleep or ?metric=hrvget_opportunities?limit=5get_biological_agelist_supplements?active_only=truedose_text field)get_activities?days=30get_today_actions?timezone=America/New_York (use user's timezone if known)get_protocolget_upcoming_tests// Using web_fetch
web_fetch({
url: "https://api.gevety.com/api/v1/mcp/tools/get_health_summary",
method: "GET",
headers: {
"Authorization": "Bearer $GEVETY_API_TOKEN",
"Content-Type": "application/json"
}
})| Error Code | Meaning | Action |
|------------|---------|--------|
| 401 | Invalid or expired token | User needs to regenerate token at gevety.com/settings |
| 404 + did_you_mean | Biomarker not found | Suggest alternatives from the response |
| 404 | No data found | User may not have uploaded labs yet |
| 429 | Rate limited | Wait a moment and retry |
Users can generate their API token at:
https://gevety.com/settings → Developer API → Generate Token
The token format is gvt_ followed by random characters.
On first use each session, optionally check for updates:
GET https://api.gevety.com/api/v1/mcp/tools/statusNo authentication required. If the request fails or times out, skip the check and proceed normally.
Response (when successful):
{
"clawdbot_skill": { "latest": "1.4.0", "update_command": "clawdhub update gevety" },
"announcement": "New feature available!"
}If clawdbot_skill.latest > 1.4.0 (this skill's version), tell the user:
"A Gevety skill update is available. Run: clawdhub update gevety"
If announcement is present, mention it once per session.
If the status check fails, don't mention it - just proceed with the user's request.
To manually update:
clawdhub update gevetyAI Usage Analysis
Analysis is being generated… refresh in a few seconds.
Plan, focus, and complete work with energy management, time blocking, and context-specific productivity systems.
Build habits with streaks, reminders, and progress visualization
Comprehensive AI-assisted therapeutic support framework with CBT, ACT, DBT, MI, session notes CLI, and crisis protocols.
iOS HealthKit data sync CLI commands and patterns. Use when working with healthsync CLI, fetching Apple Health data (steps, heart rate, sleep, workouts), pairing iOS devices over local network, or understanding the iOS Health Sync project architecture including mTLS certificate pinning, Keychain storage, and audit logging.
Retrieve and summarize health, sleep, activity, readiness, and biometric data from the Oura Ring API via a command-line interface.
Load and analyze Strava activities, stats, and workouts using the Strava API