Freddy Coach freddy Personal API
44
AI ReadinessFoundational (D)44/100
Official vendor OpenAPI document · agent-readyHealthcareClinical Databearer4 EndpointsREST
For Agents
Read your own normalized health metrics within your plan's history window, list the distinct metrics and providers available to you, see your connected sources, and read your profile and plan window. Read-only and scoped to your own data.
Use for: Get my normalized health metrics, List the metrics and providers available to me, Show which sources I have connected, Check my profile and plan window
Not supported: Does not write or modify health data, book appointments, or access another user's records. Use for reading your own normalized health metrics, sources, and profile only.
The freddy Personal API exposes read-only access to your own normalized health metrics drawn from your connected sources. It lists your metrics within your plan's history window, returns the distinct metrics and providers available to you, lists the sources you have connected, and returns your profile and plan window. All access is scoped to your own data through a personal API key.
Install Jentic One Beta
Connect the freddy Personal API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the freddy Personal API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Ffreddy.coach%2Ffreddy" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Ffreddy.coach%2Ffreddy" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with freddy Personal API.
List your normalized health metrics within your plan's history window
Return the distinct metrics and providers available to you
List the sources you have connected
Read your profile and plan history window
Use Cases
Patterns agents use freddy Personal API for, with concrete tasks.
★ Agent Health Summary
An AI agent connected through Jentic can pull your normalized health metrics, see which sources feed them, and read your plan window to know how far back the data goes, without a developer wiring the freddy API by hand. Every operation is read-only and scoped to your own data.
List the available metrics, then read the most recent normalized health metrics within the plan window
Connected Source Review
Users want to know which providers feed their health data. freddy lists your connected sources and the distinct metrics and providers available to you, so an app can show coverage and gaps.
List the connected sources and the distinct providers contributing metrics
Metric History Retrieval
Dashboards plot health metrics over the available window. freddy returns your normalized metrics within your plan's history window, so a chart can render the series you are entitled to see.
Retrieve normalized health metrics for the plan window and summarize the latest values
Key Endpoints
4 endpoints — the freddy personal api exposes read-only access to your own normalized health metrics drawn from your connected sources.
METHOD
PATH
DESCRIPTION
GET
/api/v1/metrics
List your normalized health metrics
GET
/api/v1/catalog
List metrics and providers available to you
GET
/api/v1/sources
List your connected sources
GET
/api/v1/profile
Get your profile and plan window
GET
/api/v1/metrics
List your normalized health metrics
GET
/api/v1/catalog
List metrics and providers available to you
GET
/api/v1/sources
List your connected sources
GET
/api/v1/profile
Get your profile and plan window
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
F
freddy Personal API
- Foundational (D)44/100
100
Foundational Compliance63
Developer Experience & Jentic Compatibility19
AI-Readiness & Agent Experience94
Agent Usability60
Security63
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.2
Show dimension breakdown
100
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A+Signals: 4
99%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
100%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
100%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
63
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: B-Signals: 4
0%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
50%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
19
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: FSignals: 4
33%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
0%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
44%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
60
Security
Trust, risk posture, and security compliance.
Grade: B-Signals: 1
60%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
63
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: B-Signals: 1
62%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the freddy Personal API by hand means managing its bearer key, learning your plan's history window, and paging through the available metrics and sources yourself. Through Jentic you install once, import freddy from the API Directory, store the key once, and your agent calls it.
Permission scoping
freddy is a read-only API with four operations, so a rule can allow only the reads your agent needs, such as listing metrics and sources. You choose the operations the agent may call, and because none of them write, your health data cannot be modified.
Credential isolation
Your freddy key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'read my health metrics' or 'list my connected sources', and Jentic returns the matching freddy operation with its output shape so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using freddy Personal API through Jentic.
What authentication does the freddy Personal API use?
The freddy Personal API authenticates with a personal API key sent as a bearer token in the Authorization header, per its OpenAPI spec. The key scopes access to your own data within your plan's history window. Through Jentic the key is stored encrypted by your own Jentic One instance and injected at call time, so it never reaches the agent's context.
Can I read my health metrics with the freddy Personal API?
Yes. The metrics operation returns your normalized health metrics within your plan's history window, and the catalog operation lists the distinct metrics and providers available to you.
Can I limit what my agent is allowed to do with the freddy Personal API?
Yes. freddy is read-only, so write a rule that allows only the metric and source reads your agent needs, letting it summarize your data without any ability to change it. Every call it makes is logged.
Is there a freddy MCP server?
You do not need an MCP server to give your agent the freddy Personal API. Jentic connects it directly from the API Directory: import freddy, store your key once, and the agent calls its read operations by intent without loading another server's tool definitions into its context.
What are the rate limits for the freddy Personal API?
The OpenAPI spec does not specify numeric rate limits for the freddy Personal API. Check the freddy documentation at https://freddy.coach for current limits.
How do I read my health metrics with the freddy Personal API through Jentic?
Search Jentic for an intent like 'read my health metrics', and it returns freddy's metrics operation with its output shape so your agent can pull your normalized data within the plan window. To run it on your own infrastructure, install Jentic One from its GitHub repo.
GET STARTED