The household, exposed. REST over HTTPS, JSON in and out, versioned and rate limited. A person, addressable. v4, stable since the reorganization.
All requests over HTTPS. The household key travels in the Authorization header. Keys are issued per household and survive its members.
Per household. Exceeding the limit returns 429 with a Retry-After header. The household continues regardless of whether you can read it.
Breaking changes ship as new versions. Deprecated fields remain readable for 14 months, then remain, unreadable.
Responses below are drawn from the demonstration household, which has consented in perpetuity.
Continuity notifies your systems when the household changes state. Signatures are verifiable. Events are delivered at least once and remembered exactly once.
A member's coverage has lapsed. Fired once, at the moment of lapse. The member is not notified. That is your decision to make.
A standing has been recalculated. The previous standing is included for reference and cannot be restored.
A memory retrieval has completed billing. Fired after the memory is delivered, whether or not it was the one requested.
2026-05 · The field person.inner_life is deprecated in v4. It was never populated reliably. Use person.observed_behavior, which is.
2026-02 · The endpoint POST /v4/persons/{id}/forget returns 501 Not Implemented. This is documented behavior.