Connect through narrow, typed boundaries.

Build against Eventium APIs, MCP tools, connectors and event streams without exposing Atlas credentials, physical banks or long-lived internal service secrets.

Review integration paths Request technical access

Eventium API

Identity and authorization stay at the platform boundary.

The API owns the user session, entitlements, CSRF boundary, scoped service assertions and exact resource confirmation.

User and workspace scope on every request
Idempotent writes and replayable operation records
Readiness and entitlement enforced separately

POST /v1/context/recall
Authorization: session
X-CSRF-Token: <token>

{
  "workspace_id": "wrk_northstar",
  "project_id": "prj_incident_483",
  "question": "What supports the revised window?",
  "required_evidence": true
}

200 OK
{
  "answer": "...",
  "evidence": ["source:01", "source:02"],
  "unsupported_fallback": false
}

Model Context Protocol

A small, secure path to Atlas-backed tools.

Trusted clients authenticate through Eventium, receive short-lived scoped assertions and invoke a narrow hosted tool surface. Physical Atlas banks and private service credentials never reach the client.

memory_recall

Retrieve authorized evidence-backed context.

memory_store

Store scoped memory with provenance and rules.

memory_recent

Review recent authorized memory events.

rules_list / rule_add

Read or add approved rules within scope.

Connectors and data

Bring authorized systems into the same context.

Connect files, external applications, live feeds and batch data without collapsing source provenance or bypassing enterprise access controls.

Enterprise connectors

Pre-built adapters for collaboration, service, data and content systems.

Files & media

Capability-aware upload, extraction, private storage, progress and deletion.

Streams & events

Real-time SSE status plus durable event and outbox records.

Integration checklist

What a production client must preserve.

Identity

Use the Eventium API-owned session and never send private service credentials to the browser.

Signed assertions + JWKS

Scope

Bind user, workspace, project and requested capability on every call.

Authorization decision

Memory

Use Atlas retrieval rows as the factual evidence boundary.

Source identifiers

Execution

Apply policy and approval before side effects, then retain the outcome.

Plan + approval + event

Deployment

Verify the exact production commit and dependency readiness.

Health SHA + checks