Context infrastructure for LLMs. Switch models freely. Your context stays.

Losi is free to get started. Create an account at losi.ai, add a workspace-scoped API key or connect with OAuth, then use MCP, REST, or the open-source @losi-ai SDK — no paid plan required to try.

Losi Context Bank is an open-source SDK (@losi-ai on npm) plus optional hosted APIs on losi.ai. Day one works offline: snapshots, memory, and model adapters. Connect via API key or OAuth when you want live CRM, Spaces, skills, and graph data from your Losi workspace.

Source & full guides: github.com/losi-ai/context-bank

Install

Works with npm, yarn, pnpm, and bun:

npm  install @losi-ai/core @losi-ai/openai @losi-ai/anthropicyarn add     @losi-ai/core @losi-ai/openai @losi-ai/anthropicpnpm add     @losi-ai/core @losi-ai/openai @losi-ai/anthropicbun  add     @losi-ai/core @losi-ai/openai @losi-ai/anthropic

Quickstart — one context, any model

import { LosiContext, MemorySnapshotStore } from "@losi-ai/core";import { OpenAIAdapter } from "@losi-ai/openai";import { AnthropicAdapter } from "@losi-ai/anthropic";
const ctx = new LosiContext({  adapter: new OpenAIAdapter({ apiKey: process.env.OPENAI_API_KEY! }),  store: new MemorySnapshotStore(),  persistKey: "demo",});
await ctx.remember("User prefers short answers.");const a = await ctx.complete("Draft a one-line status update.");
// Switch models — the snapshot (and remember()) stays.ctx.switchAdapter(new AnthropicAdapter({ apiKey: process.env.ANTHROPIC_API_KEY! }));const b = await ctx.complete("Say that again even shorter.");

Packages

Start here

When you need them

Hosted Context Bank API

Create a workspace-scoped API key in Losi (Profile → API Access) and store it in your host vault or as LOSI_API_KEY — do not paste it into chat. The key is bound to a workspace, so you normally only pass the key via env/vault — not a workspaceId.

import { NexusBinding } from "@losi-ai/nexus";import { SpacesBinding } from "@losi-ai/spaces";import { LosiSkillStore } from "@losi-ai/skills";
const nexus = new NexusBinding({  apiKey: process.env.LOSI_API_KEY,  crm: true,  bookings: true,});const spaces = new SpacesBinding({  apiKey: process.env.LOSI_API_KEY,  tasks: true,  calendar: true,});const skills = new LosiSkillStore({ apiKey: process.env.LOSI_API_KEY! });

Auth header: Authorization: Bearer + value from vault/env (LOSI_API_KEY).

Base URL

https://losi.ai/api/v1/context-bank

Endpoints (pathless — workspace implied by key)

For full Nexus CRM mutations (create/update leads, campaigns, email/SMS, etc.) use MCP losiNexus__run or POST /api/v1/nexus/tools with nexus:write on the key — Context Bank /nexus/… is intentionally read-context for SDKs and requires both nexus:read and an active Nexus subscription. Spaces Context Bank reads require spaces:read.

Session example

curl https://losi.ai/api/v1/context-bank/session \  -H "Authorization: Bearer $LOSI_API_KEY"

Workspace-wide search example

curl "https://losi.ai/api/v1/context-bank/search?q=nexus&limit=25" \  -H "Authorization: Bearer $LOSI_API_KEY"

Optional types= filter (comma-separated): space,task,note,event,space_memory,space_reference_memory,graph_node,skill,soul,personal_memory,workspace_memory,contact,booking.

MCP equivalent: losiContext__search with { "q": "nexus", "limit": 25 }.

Skills example

# Listcurl https://losi.ai/api/v1/context-bank/skills \  -H "Authorization: Bearer $LOSI_API_KEY"
# Savecurl -X POST https://losi.ai/api/v1/context-bank/skills \  -H "Authorization: Bearer $LOSI_API_KEY" \  -H "Content-Type: application/json" \  -d '{    "name": "follow-up",    "description": "Draft a follow-up email",    "steps": [{ "type": "note", "text": "Follow up with {{name}}" }],    "parameters": [{ "name": "name", "required": true }]  }'

Legacy /workspaces/{id}/… paths still work when {id} matches the key’s bound workspace. Prefer pathless routes.

Connect without the SDK (MCP, skill, prompt)

Key permissions for MCP / tools

Create the key with the scopes you need (Profile → API Access):

Governed keys can further pin spaceIds, memoryScopes (personal / workspace / space / space_reference), nexusAreas, and optional allowedTools. Space memories stay on the Spaces tool surface (losiSpaces__listSpaceMemories, plus Space Reference Memories).

Workspace-scoped keys are required so Losi can imply the workspace.

Secrets

Store the workspace key in the host vault or as LOSI_API_KEY. Never put losi-… into a chat prompt or commit it to git.

MCP config example

{  "mcpServers": {    "losi": {      "url": "https://losi.ai/api/mcp",      "headers": {        "Authorization": "Bearer ${LOSI_API_KEY}"      }    }  }}

Full guide: docs/connect.md on GitHub

GitHub Packages (optional)

Packages are also published to GitHub Packages under the @losi-ai scope. To install from there, add an .npmrc:

@losi-ai:registry=https://npm.pkg.github.com//npm.pkg.github.com/:_authToken=YOUR_GITHUB_PAT

Most apps should install from npmjs.org instead — no special config needed.

Links

• GitHub: losi-ai/context-bank
• npm org: npmjs.com/org/losi-ai
• Create API keys: Profile → API Access
• Chat Completions API: API Access