Record Observations
Observations
Record Observations
Record what happened. You observe; Nous derives the claims.
POST
Record Observations
The only write verb in the customer graph. Agents never overwrite, they record observations. Nous derives the new facts automatically from the full observation history and tells you which were recomputed.
Request
Body
Entity UUID, email, domain, or LinkedIn URL. Not a bare name — writes need a precise identifier so the entity can be created if it doesn’t exist yet.
One or more observations to append. Each:
Response
claims_recomputed lists the state properties whose claim was re-derived after this batch — your downstream UI can refetch only those.
The observation model
You’re appending to an immutable, append-only customer graph. Two reasons:- The graph self-heals. When a new observation contradicts an old one, the affected facts recompute and the belief shifts. Nothing is ever “lost.”
- Every claim is auditable —
epistemic_class+sourceson every claim let your agent (and your audit log) see exactly which observations support it.
null value on a state observation to assert the fact ended — they left the company, the deal closed-lost, the email bounced.