// CLOUD MEMORY · QUICKTEST READY · MCP

BIL.INC

DURABLE MEMORY FOR CODING AGENTS

Commit, recall, audit, and rollback agent state through one hosted Cloud key. Start with the SDK, run quicktest, then attach Codex, Claude Code, Cursor, or MCP.

pip install -U bilinc
bilinc start
bilinc login --api-key bil_live_...
bilinc quicktest
7-day trial · no card · Python 3.10+
GET STARTED FREEVIEW DOCSADD MCPVIEW PRICING
8,000+ downloads/users worldwidePyPI v2.1.4Cloud SDKMCP adapter
[ v2.1.4 STABLE ]█
8,000+
downloads/users worldwide
20
MCP tools
98.0%
LongMemEval-s R@5
0.933
NDCG@5
7 days
Cloud trial

what.is.bilinc

Durable memory for coding agents — with commit, recall, audit, and rollback.

Bilinc lets agents save important facts, recall prior decisions, inspect state, and recover from bad memory. Start with the Python package, create a hosted Cloud API key, then use the SDK, CLI, or MCP adapter from your agent runtime.

Install BilincAdd MCPView use cases

Verified writes

Run checks before agent state becomes durable memory.

Conflict-aware memory

Revise or contract beliefs when new state contradicts old state.

Snapshots and rollback

Checkpoint, diff, and restore agent memory after a bad run.

MCP for coding agents

Attach Bilinc to Codex, Claude Code, Cursor, and local agent workflows.

Cloud API keys

Use the PyPI SDK with hosted API keys instead of shipping local storage internals.

Cloud for teams

Use hosted API keys, shared workspaces, and billing-backed entitlements.

60.second.path

First successful run

bilinc quicktest proves that your local CLI can reach Bilinc Cloud, authenticate with a hosted API key, commit one memory, recall it, and read Cloud status. After that, the same key can be moved into Codex, Claude Code, Cursor, or your own agent runtime.

architecture

Agent runtime → Bilinc Cloud

  1. Agent runtime calls SDK, CLI, HTTP, or MCP.
  2. Bilinc Cloud checks API key, entitlement, and workspace scope.
  3. Hosted memory/state plane stores commit and recall events.
  4. Audit, rollback, retention, and billing posture stay inspectable.

operator routes

Pick the path that matches your deployment reality.

Bilinc 2.1.4 starts with a cloud-only public package and a CLI-led first run. Paid Cloud exists for teams that need shared state, retention, and production accountability without running local storage internals.

start here

Connect your agent

Install Bilinc 2.1.4, run bilinc start, connect Cloud once, then verify hosted commit and recall with quicktest.

Start in 60 sec

hosted path

Evaluate Bilinc Cloud

Start a 7-day hosted trial, test managed state and API-key workflows, then move to Pro or Team from the billing console when the workload is real.

Start trial

operational trust

Check the control surface

Read how writes, rollback, observability, audit trail, and runtime entitlements behave before you put persistent agents on top.

Review trust

billing posture

Understand billing status

Cloud billing is live for owner/admin operators. Internal entitlements remain the runtime authority; Stripe syncs subscription state.

Read billing

// BOOT_SEQUENCE.SH

HOW IT WORKS

Five commands to a trustworthy agent state layer.

BILINC_TERMINAL — bash
BILINC SDK v2.0 • BUSL-1.1 • source access by request

// BENCHMARK_RESULTS.LOG

BENCHMARK RESULTS

Reproducible benchmark receipts. No LLM in the loop; not hosted-SLA claims.

LongMemEval-s R@5: 98.0%NDCG@5: 0.933AMB L1: 94/100AMB L2: 100/100
01. LONGMEMEVAL-S
_
□
×
98.0%

Fresh cleaned fixture reproduction: 98.0% R@5 and 0.933 NDCG@5 without a paid API.

FULL 500 · NO LLM RERANKER
LONGMEMEVAL_CATEGORY_TRACE — 2026-07-05
_
□
×
KNOWLEDGE-UPDATE
100.0%
MULTI-SESSION
99.2%
SINGLE-ASSISTANT
96.4%
PREFERENCE
93.3%
SINGLE-USER
100.0%
TEMPORAL
96.2%

AMB (Agent Memory Benchmark) is the open benchmark by vectorize.io. ConvoMem 98.0% and LoCoMo 90.35% remain internal ReARC regression checks, not official dataset claims.

faq

Practical answers before you wire memory into an agent.

Is Bilinc a vector database?

No. Bilinc can use retrieval signals, but its product boundary is agent state: typed memory, verification, revision, audit history, snapshots, and rollback.

Is the PyPI package self-hosted?

No. Bilinc 2.1.4 on PyPI is a cloud-only SDK, CLI, and MCP adapter. Local storage/runtime internals are not shipped in the public wheel.

Do I need a Cloud key?

Yes for hosted memory operations. The public package installs freely, but commit and recall use BILINC_API_KEY and active Cloud entitlements.

What happens when memory contradicts older state?

Bilinc exposes conflict-aware revision paths so a new write does not silently overwrite useful state. Operators can inspect the resulting history.

Does Bilinc make every answer true?

No. Verification improves inspectability and failure handling. It does not turn every generated answer into automatic truth.

Which agents can use it?

Any agent that can call Python, HTTP, or MCP can use Bilinc. The docs include Codex, Claude Code, Cursor, and general agent prompts.