Developers
Durable reminder memory, when the public API ships.
The product is one reminder engine with an HTTP /v1 used by the first-party Flutter app. Third-party keys, OAuth, webhooks, and agent tokens are specified. They are not live.
What you get
- One reminder primitive: due date, offsets, channels, recurrence
- Cloud Functions own scheduling. Clients do not attach live Firestore listeners to reminder lists
- OpenAPI contract in the repo for the first-party subset the app uses today
- Webhook callbacks and scoped API keys are in the design, not in production auth
- Do not build a customer integration against undocumented Functions URLs
Live today: one dashboard, email reminders, push notifications, and recurring items. Coming later: SMS, calendar sync, attachments, teams, and public API keys.
What to do today
Use the app. If you are evaluating the platform, read features and the security page. Do not ship a dependency on public API keys that do not exist.
Questions
- Where is the API reference?
- The implemented contract is openapi/v1.yaml in the GitHub repo. The full public API spec is still draft. There is no hosted docs portal yet.
- Can my agent create reminders now?
- Only if it signs in as a Firebase user the way the app does. That is not a supported partner path. Wait for agent tokens.
Add it once. Never forget it again.
Live today: one dashboard, email reminders, push notifications, and recurring items.