canonical: https://jentic.com/apis/getmyluna.app/getmyluna

# Getmyluna App Luna API

The Luna API is the shared baby-care tracker behind the Luna app, recording feeds, sleep, nappies, solids, and routines for one family across parents and invited caregivers. It logs, edits, reacts to, and undoes care events, lists today's and any day's events, and returns growth measurements and weekly pattern reviews. It manages the family account, caregiver invites, child profile, and bearer tokens, and every request is scoped to a single family resolved from the credential so no caller can reach another family's data. It also answers questions over the family's own history through its Ask Luna feature. It is aimed at parents and tools that want programmatic access to a shared care log.

## For AI agents

Track baby care across a shared family account: log feeds, sleep, and nappies, review today's events and growth patterns, manage caregiver invites, and read the family's history.

## Scope

Does not provide medical advice, clinical records, or appointment booking. Use for shared baby-care activity tracking across a family only.

## Capabilities

- Log, edit, react to, and undo baby-care events such as feeds, sleep, and nappies
- List today's events and the events for any chosen day
- Return growth measurements and weekly pattern reviews for a child
- Invite and revoke caregiver access to a shared family account
- Create and revoke bearer tokens for connecting an assistant
- Answer questions over the family's own logged history

## Use cases

### Agent-logged care events

An AI assistant a parent talks to can call the Luna API through Jentic to log a feed or nap as it happens and read back today's events to confirm. Jentic returns the log-event operation from a natural-language query, so the assistant records care without the parent opening the app or the assistant reading the Luna reference.

Example prompt: Log a feed event with the current time for the family, then list today's events and confirm the feed was recorded.

### Weekly pattern review

Return growth measurements and the weekly pattern review to show how a child's sleep and feeding are trending across a shared family account. Parents and caregivers use this to spot changes in routine without scrolling the raw event log.

Example prompt: Read the child's growth measurements and the weekly pattern review, then summarize how sleep and feeding changed this week.

### Caregiver access management

Invite a caregiver to the family account, list open invites and members, and revoke access when it is no longer needed, all scoped to one family resolved from the credential. Families use this to share the same care log with a nanny or grandparent without exposing another family's data.

Example prompt: Create a caregiver invite link for the family, list the current members and open invites, and confirm the new invite appears.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/api/vega/onboard` | Create a family account |
| POST | `/api/vega/log` | Log a care event |
| GET | `/api/vega/today` | List today's events |
| GET | `/api/vega/events` | List events for a day |
| GET | `/api/vega/measurements` | Retrieve growth measurements |
| GET | `/api/vega/patterns` | Retrieve patterns and weekly review |
| POST | `/api/vega/invite` | Create a caregiver invite link |
| POST | `/api/vega/token` | Create a bearer token |

## Key resources

- **Tracker** — Log, edit, react to, and undo care events and list events by day
- **Insights** — Return growth measurements, today's events, and weekly pattern reviews
- **Account** — Manage the family account, caregiver invites, and members
- **Tokens** — Create, list, and revoke bearer tokens for connecting an assistant
- **Ask Luna** — Answer questions over the family's own logged history and manage remembered notes

## 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:** 65 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 99 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 45 / 100
  - Agent Usability: 94 / 100
  - Security: 55 / 100
  - AI Discoverability: 79 / 100
- **View full report:** https://jentic.com/apis/getmyluna.app/getmyluna/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 Luna API by hand means creating a bearer token in the app or from a signed-in session, handling the one-family scoping, and coding each logging and review call yourself. Through Jentic you install once, import the API from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** The Luna endpoints resolve the family from the credential rather than from an id in the URL path, so bound your agent to the operations it needs, such as logging events and reading the day. You choose which operations it may call, so the delete-family operation is not included unless you add it.
- **Credential handling:** Your Luna token 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 'log a feed' or 'review this week's patterns', and Jentic returns the matching Luna operation with its input schema so the agent calls the right endpoint without reading the reference docs.

## Related APIs

- **Notion API** — Shared workspace for notes, databases, and collaboration
- **Basecamp API** — Team collaboration with messages, to-dos, and shared spaces
- **Asana API** — Task and activity tracking shared across a group

## FAQ

### Is there a Luna API MCP server?

You do not need an MCP server to give your agent the Luna API. Jentic connects it directly from the API Directory: import the API, store your token once, and your agent calls the logging, review, and account operations. Operations are discovered on demand, so no extra server definitions load into the agent's context.

### What authentication does the Luna API use?

Most endpoints require a bearer token per the OpenAPI spec, with a session cookie named luna_session accepted for the web app, while public endpoints such as the health check and connector manifest need no credential. Through Jentic the token is stored encrypted in your own Jentic One instance and supplied only when an authenticated call runs, so it never reaches the agent's context.

### Is Luna API data scoped to one family?

Yes. Every request is scoped to a single family resolved from the bearer token or session cookie, and there is no way to address another family's data. That means a connected assistant only ever sees and writes to the family whose token it holds.

### What are the rate limits for the Luna API?

The OpenAPI spec does not specify rate limits. A health endpoint lets you check service status, and you can confirm the current request limits in the Luna documentation at https://getmyluna.app.

### Can I limit what my agent is allowed to do with the Luna API?

Yes. Write a rule that permits only the logging and read operations, such as logging a feed and listing today's events, so the agent can track care but cannot run the delete-family operation, and every call it makes is logged.

### How do I log a care event with the Luna API through Jentic?

Search Jentic for 'log a baby feeding event' to surface the log-event operation, load its input schema, pass the event type and time, and execute, then list today's events to confirm. To run it on your own infrastructure, install Jentic One from its GitHub repo.
