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.