Skip to main content
GET
Get Account
The raw projection. Returns every known fact about an entity, each with its source, freshness, and confidence, plus the recent activity timeline. Use this when you want the complete picture; prefer /v2/context for task-shaped, ranked output.

Request

Path params

string
required
URL-encoded identifier — entity UUID, email, domain, LinkedIn URL, or name. Names may return candidates.

Response

recent_observations is truncated to the most recent 50 events. Treat counts derived from it (number of replies, messages, etc.) as lower bounds, not totals. For accurate counts across a longer window or many entities, use POST /v2/query.

Claim shapes worth knowing

Most claims hold a simple scalar value ("VP Sales", "evaluating", 0.78). A few hold structured objects — read these as nested rather than flat. The big one is channels, which carries per-channel state for LinkedIn, email, and anything else Nous tracks per-contact:
So adapters reading “is this person connected on LinkedIn?” should look at claims.channels.value.linkedin.state === 'connected', not a flat linkedin.state claim. New channels get added under the same value object as integrations land.

Ambiguous focus

Same shape as /v2/context:

When to call it

  • “What do we know about X?” type questions
  • Building an audit / debug view of a contact
  • Inspecting epistemic_class and sources to understand WHY a claim is held
For action-oriented context (drafting outreach, prepping a meeting), prefer /v2/context — it returns less, but ranked for the task.