Documentation

Build governed context into your agents.

Northsun is the memory and enrichment layer for AI agents. Use the REST API for the stable caller-memory lifecycle, or connect the hosted MCP server to chat, coding, and workflow agents. Governed context intelligence is the differentiator: context should arrive with the evidence, timing, and boundaries required to use it well.

Start here

The stable public REST API is three endpoints: POST /v1/recall_and_enrich, POST /v1/calls/end, and GET /v1/caller/{phone_number}. Start with the REST quickstart, connect an agent through the MCP guide, or follow the dedicated chat and workflow path. The guides below separate callable behavior from design-stage architecture.

Get started

  • Introduction — The memory and enrichment layer for AI agents: live caller memory and enrichment endpoints, a beta hosted MCP surface, and governed context intelligence.
  • Installation — Get a Northsun API key today and install the CLI, hosted MCP, or raw HTTP surface.
  • Quickstart — Complete one Northsun (formerly Mnemix) caller-memory lifecycle against the frozen public REST contract: recall context before an interaction, submit the c
  • MCP server — The hosted Northsun (formerly Mnemix) MCP server gives authenticated MCP-compatible agents memory, caller, enrichment, and retrieval tools over Streamable
  • What is caller memory? — Caller memory is the application pattern of using an incoming phone number to request the tenant's known caller record, prior-call history, and available e
  • API reference — The full public v1 surface is three endpoints. Base URL for all of them: https://mcp.mnemix.ai. Every request needs a bearer token:
  • Authentication and API keys — Every Northsun (formerly Mnemix) REST and MCP request is authenticated with a tenant-scoped API key. Send it as a bearer token from server-side code; North
  • Errors, rate limits, and retries — Northsun (formerly Mnemix) returns JSON errors with a stable envelope. Production integrations should branch on the HTTP status and error.code, log the tra
  • What recall gives you back — The real, field-for-field response shape of POST /v1/recall_and_enrich — what production serves today, and how to put it in a voice-agent prompt without wr
  • Hangup, and what happens next — POST /v1/calls/end and the read-after-write guarantee — the next recall for that caller sees this call immediately, not eventually.

Core concepts

  • Overview — Understand Northsun caller memory, enrichment, evidence, temporal facts, policy, feedback, and the ship-state boundary between them.
  • Evidence references — Learn how the Northsun repository models tenant-scoped provenance, lineage, source priority, hashes, and temporal metadata.
  • Locked facts — Understand the repository substrate for evidence-backed, versioned facts and the boundary between database procedures and public product behavior.
  • Bi-temporal validity — Separate when a fact was true from when the system recorded it, with the exact Northsun substrate scope and public API boundary.
  • Architecture — How Northsun (formerly Mnemix) is actually built — the worker, the storage tiers, the gate stages, and where the recall path spends its time. Northsun is d
  • Context Spaces — Learn how Mnemix is designed to isolate, share, and govern memory across groups of AI agents.
  • Caller enrichment — Northsun (formerly Mnemix) combines remembered interaction history with real-world caller context in the same pre-interaction response. Enrichment is addit
  • Salience and Beacon — How Northsun frames serving the right context at the right moment, and the exact boundary between the shipped caller read and proactive design work.

Governed design

  • Policy bundles — Explore the governed design for versioned action rules without mistaking a frozen architecture contract for a public product API.
  • Validation gate — Understand the design for server-owned action validation, deterministic rules, isolated qualitative grading, and evidence-based graduation.
  • Feedback loop — Learn how outcome feedback could connect served context to usefulness, staleness, contradiction, and later corrections—with current contract boundaries.

SDKs and tools

  • TypeScript — Use the platform fetch API to call Northsun (formerly Mnemix) over the frozen public caller-memory contract. This keeps your integration pinned to the thre
  • Python over HTTP — Northsun (formerly Mnemix) does not currently publish an official Python SDK from this repository. Python applications should use the frozen REST API direc

Agent clients

  • Codex — Connect Codex to the hosted Northsun MCP endpoint, verify the authenticated tools, and remove or rotate the connection safely.
  • Cursor — Connect Cursor to Northsun over remote MCP, verify the available tools, and handle environment-backed authentication safely.
  • Gemini CLI — Add the hosted Northsun MCP endpoint to Gemini CLI, verify tool discovery, and remove or rotate the connection safely.
  • Hermes Agent — Connect Hermes Agent to Northsun with an environment-backed header, verify prefixed MCP tools, and rotate or remove the connection.
  • Claude Code — Connect Claude Code to the hosted Mnemix MCP server and verify the available tools.
  • Mnemix CLI — Inspect authentication and caller-memory flows from a terminal.

Integration guides

  • Chat and workflow agents — Wire a chat, coding, or workflow agent to the evolving Northsun context loop, and prove the lifecycle before you depend on it.

Operate

  • Troubleshooting — Diagnose a Northsun integration by status code, error code, endpoint, and trace identifier, then collect a safe diagnostic receipt.
  • Production readiness — The launch checklist for a Northsun integration — server-side auth, an observable recall/write-back lifecycle, and claims that match observed behavior.
  • What isn't built yet — One honest page — the validation gate, policy-bundle authoring, self-serve signup, and billing are not shipped today. Read this before you plan around any

Guides

  • Migrating to Northsun — Move an existing agent memory workflow to Northsun without importing stale, unsourced, or unverified context as if it were truth.
  • Voice integration patterns — Map any voice platform onto the Northsun recall, conversation, write-back, and verification lifecycle without making memory a greeting blocker.
  • Vapi — Install the published Vapi integration kit, wire the webhook, and place your key.
  • Bland — Install the published Bland integration kit, wire the pre-call and post-call webhooks, and place your key.
  • Twilio — Install the published Twilio-direct integration kit, wire the Voice webhook and Status Callback, and place your key.
  • ElevenLabs — Install the published ElevenLabs Agents integration kit, wire the conversation-initiation and post-call webhooks, and place your key.
  • Retell — Install the published Retell AI integration kit, wire the call_inbound and call_analyzed webhooks, and place your key.
  • LiveKit — Install the published LiveKit Agents integration kit, resolve the caller's SIP identity, and write session context back at hangup.

Reference

  • Glossary — Canonical definitions for the product, API, governance, and ship-state terms used throughout Northsun documentation.