canonical: https://jentic.com/apis/freddy.coach/freddy

# Freddy Coach freddy Personal API

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.

## For AI 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.

## Scope

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.

## Capabilities

- 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

### 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.

Example prompt: 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.

Example prompt: 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.

Example prompt: Retrieve normalized health metrics for the plan window and summarize the latest values

## Key endpoints

| 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 |

## Key resources

- **Metrics** — List your normalized health metrics within your plan's history window
- **Catalog** — Return the distinct metrics and providers available to you
- **Sources** — List the sources you have connected
- **Profile** — Read your profile and plan history window

## AI readiness

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.

- **Score:** 44 / 100
- **Maturity:** Foundational
- **Dimensions:**
  - Foundational Compliance: 100 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 19 / 100
  - Agent Usability: 94 / 100
  - Security: 60 / 100
  - AI Discoverability: 63 / 100
- **View full report:** https://jentic.com/apis/freddy.coach/freddy/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **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 handling:** 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.
- **Discovery method:** 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

- **Fitbit** — Wearable platform exposing activity, sleep, and health metrics.
- **OpenWearables** — Wearable data source feeding health and activity signals.
- **Google Fitness** — Google's store of fitness and health data from connected apps.

## FAQ

### 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.