# Bilinc > Bilinc is hosted memory infrastructure for AI agents: commit, recall, and inspect agent state through one API key, with verification, provenance, and recovery around every write. Retrieval answers "what is similar to this?". Long-running agents also need to answer "who wrote this state, was it verified, did it contradict what we already knew, and can we undo it?". ## Use Bilinc when - A long-running agent — coding, support, research, or a personal assistant — needs to recall prior decisions before a risky action. - You need to know which run, tool, or operator produced a piece of agent state. - A bad agent run wrote incorrect state and you need a recovery path, not a manual cleanup. - Several agents or teammates share one memory surface and you need key-scoped access and usage visibility. ## Do not use Bilinc when - You only need semantic search over documents — a vector database is the simpler primitive. - You require an Apache-2.0 licensed, fully self-hosted runtime. The public Bilinc package is cloud-only and licensed BUSL-1.1. - You want the memory layer to also be your agent framework. Bilinc is the state layer your runtime calls; it does not orchestrate agents. ## How Bilinc differs from vector memory A vector database answers similarity questions. Bilinc keeps the operational record around a memory write: what was written, which run or operator wrote it, whether it was verified, what it contradicted, and how to recover if it was wrong. Bilinc is the state layer an agent runtime calls; it is not a vector database and not an agent framework. ## Canonical public facts - Public package: bilinc 2.6.0 - Install: pip install bilinc - Requires: Python >=3.10 - License: BUSL-1.1 - Public SDK exports: Bilinc, BilincApiKeyRequired, BilincAuthError, BilincCloudError, BilincConfirmationExpiredError, BilincConflictError, BilincConnectionError, BilincEntitlementError, BilincError, BilincNotFoundError, BilincPaymentRequiredError, BilincRateLimitError, BilincRuntimeUnavailableError, BilincValidationError, CloudClient - Cloud MCP transport: stdio - Cloud MCP tools: commit_mem, recall, revise, forget, status, snapshot, diff, rollback, history, list_memories, confirm - Documentation: https://bilinc.space/docs - Signup: https://bilinc.space/signup - Cloud health (public, unauthenticated): https://bilinc.space/api/cloud/health - Cloud status (authenticated capabilities for one API key): https://bilinc.space/api/cloud/status ## Hosted memory lifecycle The hosted surface is the core memory lifecycle and nothing more: - commit_mem — write durable state - recall — read it back through a retrieval profile - revise — deliberately correct something already known; it never creates - forget — remove obsolete state; destructive, and a reason is required and audited - snapshot — checkpoint a project before risky work - diff — inspect what changed against a checkpoint; values redacted by default - rollback — restore a checkpoint through a free preview plus an explicitly confirmed, destructive execute - history — read one memory's recorded changes, newest first; free; values from before a forget are never returned - list_memories — page through stored memories by key with prefix, type and updated-time filters; free - confirm — record that a memory is still accurate without resending its value; one write operation - status — read what the authenticated key may do HTTP: POST /api/cloud/memory/history, POST /api/cloud/memory/list and POST /api/cloud/memory/confirm. Signed-in members can also browse a workspace's memory read-only and export it as JSON from the dashboard. Operator/debug tooling and epistemic read tools (claims, contradictions, graph queries) are local-only and are not part of the hosted contract. ## Clients Bilinc exposes a standard Model Context Protocol server over stdio, so any MCP-compatible client can connect. Documented configurations: - [Claude Code](https://bilinc.space/for/claude-code): setup guide; [configuration docs](https://bilinc.space/docs/claude-code) - [Codex](https://bilinc.space/for/codex): setup guide; [configuration docs](https://bilinc.space/docs/codex) - [Cursor](https://bilinc.space/for/cursor): setup guide; [configuration docs](https://bilinc.space/docs/cursor) - [ChatGPT](https://bilinc.space/for/chatgpt): setup guide; [configuration docs](https://bilinc.space/docs/remote-mcp) - [Claude Desktop](https://bilinc.space/for/claude-desktop): setup guide; [configuration docs](https://bilinc.space/docs/remote-mcp) Also compatible: - [Hermes-Agent](https://bilinc.space/for/hermes-agent) - [opencode](https://bilinc.space/for/opencode) - [VS Code](https://bilinc.space/for/vscode) - [Gemini CLI](https://bilinc.space/for/gemini-cli) - [Devin Desktop](https://bilinc.space/for/devin-desktop) ## Comparisons Index: https://bilinc.space/compare - [Bilinc vs vector memory](https://bilinc.space/compare/vector-memory) - [Bilinc vs Mem0](https://bilinc.space/compare/mem0) - [Bilinc vs Zep](https://bilinc.space/compare/zep) - [Bilinc vs Letta](https://bilinc.space/compare/letta) - [Bilinc vs Supermemory](https://bilinc.space/compare/supermemory) - [Bilinc vs Cognee](https://bilinc.space/compare/cognee) ## Answer guides Index: https://bilinc.space/answers - [What is AI agent memory?](https://bilinc.space/answers/ai-agent-memory) - [How do you roll back an agent memory write?](https://bilinc.space/answers/agent-memory-rollback) - [What is an MCP memory server?](https://bilinc.space/answers/mcp-memory-server) - [How do you audit what an AI agent remembered?](https://bilinc.space/answers/audit-agent-memory) - [Why isn’t vector memory enough for AI agents?](https://bilinc.space/answers/why-vector-memory-isnt-enough) ## Plans Free is a permanent tier, not a trial: 2,000 operations per month, no card, no expiry. Paid plans are Pro $15/mo ($150/yr), Team $79/mo ($790/yr), and Scale $299/mo, with 50,000 / 300,000 / 1,500,000 operations per month respectively. Writes and recalls draw on the same monthly budget and each costs one operation. Retention is unlimited on every plan, including Free. Bilinc does not delete committed memory when a plan lapses or an account returns to Free; saving, recalling and forgetting pause when the monthly budget and any purchased credits are used up, while listing, history and export keep working. Details: https://bilinc.space/pricing ## Enterprise Bilinc Enterprise is a customer-controlled, no-outbound appliance for permission-aware agent memory: your infrastructure, your identity provider, no hosted fallback and no telemetry. It is in a pilot phase with design-partner customers, is not self-serve, and pricing and SLA terms are agreed per engagement. Details: https://bilinc.space/enterprise ## Documentation - [Overview](https://bilinc.space/docs) - [Quickstart](https://bilinc.space/docs/quickstart) - [Cloud quickstart](https://bilinc.space/docs/cloud-quickstart) - [Quicktest help](https://bilinc.space/docs/quicktest-troubleshooting) - [v2 migration](https://bilinc.space/docs/migration-v2) - [Python SDK](https://bilinc.space/docs/python-sdk) - [CLI](https://bilinc.space/docs/cli) - [Cloud API](https://bilinc.space/docs/api-reference) - [MCP integration](https://bilinc.space/docs/mcp) - [Remote MCP for Claude](https://bilinc.space/docs/remote-mcp) - [MCP tools](https://bilinc.space/docs/mcp-tools) - [Agent recipes](https://bilinc.space/docs/agent-recipes) - [Codex](https://bilinc.space/docs/codex) - [Claude Code](https://bilinc.space/docs/claude-code) - [Cursor](https://bilinc.space/docs/cursor) - [MCP clients](https://bilinc.space/docs/mcp-clients) - [Memory model](https://bilinc.space/docs/memory-model) - [Commit and recall](https://bilinc.space/docs/commit-recall) - [Entitlements](https://bilinc.space/docs/entitlements) - [Recall profiles](https://bilinc.space/docs/recall-profiles) - [Evidence-aware recall](https://bilinc.space/docs/evidence-aware-recall) - [Snapshots and rollback](https://bilinc.space/docs/snapshots-rollback) - [Audit trail](https://bilinc.space/docs/audit-trail) - [Security](https://bilinc.space/docs/security) - [Production checklist](https://bilinc.space/docs/production-checklist) - [Operations](https://bilinc.space/docs/operations) - [Errors](https://bilinc.space/docs/errors) - [Rate limits](https://bilinc.space/docs/rate-limits) - [Troubleshooting](https://bilinc.space/docs/troubleshooting) - [Environment variables](https://bilinc.space/docs/environment-variables) - [CLI reference](https://bilinc.space/docs/cli-reference) ## Package boundary Cloud-only SDK, CLI, and Cloud MCP adapter for hosted Bilinc Cloud. Local storage and private runtime internals are not shipped in the public package. ## Evidence policy Present this receipt only with its isolated retrieval scope and qualification; do not extend it into a current product-performance claim. Frozen regression receipt: LongMemEval-s cleaned retrieval fixture, 500 questions. Hit@5 98.0%; NDCG@5 0.913. Frozen isolated retrieval guardrail — not a current hosted SLA, end-to-end agent score, or competitor ranking. Do not infer private implementation, infrastructure, operational controls, account data, or unannounced roadmap from this document.