# Henia

> Henia is a private nutrition and training diary. Signed-in users can grant AI assistants revocable, account-scoped access.

## Restricted structured channel for Instinct and Muse

1. Start with https://app.heniahealth.com/assistant-guide.md (public; no Authorization header).
2. API base: https://app.heniahealth.com/api/assistants/v1. Use only a dedicated approved provider/account credential.
3. At connection, read authenticated GET /contract, its public guidelines_path and authenticated specification_path before operating.
4. This channel accepts typed JSON for confirmed food and completed training, and returns today's remaining budget. It does not run Henia AI or export private history.
5. Use only enabled contract scopes. Photos, calendar, reminders and general provider onboarding are not enabled. Muse needs its own verified adapter and credential.
6. The following legacy MCP workflow is a separate integration; never use it as a fallback for this restricted channel.

## Legacy MCP integration

- MCP endpoint: https://app.heniahealth.com/mcp
- Machine-readable server manifest: https://app.heniahealth.com/.well-known/mcp/server.json
- Transport: Streamable HTTP
- Authentication discovery: https://app.heniahealth.com/.well-known/oauth-protected-resource/mcp
- Recommended authorization: OAuth device authorization with a one-time user code.
- Device authorization endpoint: https://app.heniahealth.com/oauth/device_authorization
- Token endpoint: https://app.heniahealth.com/oauth/token
- Scopes: `nutrition.read nutrition.write`
- The one-time code expires after 10 minutes. Access tokens last one hour; refresh credentials rotate and expire after 30 days without use or 90 days maximum.
- Manual 90-day bearer tokens remain available as a fallback under Settings → AI assistants.
- Credentials identify the Henia user. Never request an email password, website cookie, or email address for MCP authorization.

## Legacy MCP assistant workflow

1. Call `estimate_meal` for natural-language meal descriptions.
2. Ask any clarification questions returned by the estimator.
3. Show the estimated foods, portions, calories, and macros to the user.
4. Call `log_meal` only after the user explicitly confirms.
5. Read the current entry before an update, and require explicit confirmation before deleting anything.

## Legacy MCP capabilities

- Read one nutrition day or an inclusive range of up to 31 days.
- Search the Henia food catalog.
- Estimate a meal without saving it.
- Log a confirmed meal or drink.
- Update or delete entries belonging to the connected user.

The endpoint is self-describing through MCP `initialize`, `server/discover`, and `tools/list`.