Schedule a reminder notification on your paired phone
Schedules a reminder — the remind_me MCP tool’s backing endpoint. The phone (not the server) owns the schedule: the server encrypts the message once, delivers it to the paired phone immediately over FCM, and retains nothing (spec D3) — the phone arms a local alarm and fires the reminder notification at at.
at is an absolute Unix epoch in seconds, and must be between 60 seconds and 365 days in the future (400 fire_at_too_soon / 400 fire_at_too_far). The delivery to the phone is best-effort like any other push — a phone that never receives the setup message never arms the alarm.
Requires a paired phone device on the account behind the bearer token (409 no_phone_device).
Phone-capability gate. If the paired phone’s reported app build is too old to schedule reminders, the request is refused outright (426 phone_app_outdated) rather than accepted and silently dropped on arrival — a later app update can’t rescue a message that already arrived and was ignored. A phone that has never reported its version is allowed through instead, with a warnings entry naming the uncertainty.
Authorizations
Opaque bearer token created on your paired Android phone. The format is rfk_live_ followed by 32 URL-safe alphanumeric characters (≥160 bits of entropy). Test tokens use the rfk_test_ prefix.
Body
Response
Created — the reminder setup message was dispatched to the phone.
Reminder id (rmd_ prefix). Pass it to DELETE /v1/reminders/{id} to cancel.
"rmd_3f6e2a7c9b1d4f8e8a5b6c1d2e3f4a5b"
Unix epoch seconds the reminder is scheduled for (echoes the requested at).
1786387000
Present when the phone hasn't reported an app version yet, so the server can't confirm it supports reminders — the setup message may be silently dropped if the installed build predates support. Omitted entirely once the phone's reported version is known to support it.