// COGNITIVE RUNTIME · EVENT RECEIPTS · MCP READY

BIL.INC

THE VERIFIABLE AGENT BRAIN RUNTIME

Bilinc 2.1.3 starts with one CLI path: install, connect Cloud, run quicktest, then give your agent hosted commit and recall through SDK or MCP.

pip install -U bilinc && bilinc start

Python 3.10+ · BUSL-1.1

START 7-DAY CLOUD TRIAL INSTALL CLOUD SDK ADD MCP SOURCE ACCESS

7.5K+ PyPI downloadsPyPI v2.1.3Cloud SDKMCP adapter

[ v2.1.3 STABLE ]█

7.5K+

PyPI downloads

MCP tools

98.0%

LongMemEval-s R@5

0.933

NDCG@5

7 days

Cloud trial

Live

Cloud billing

what.is.bilinc

Bilinc is a memory and state layer for AI agents.

It 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 Bilinc Add MCP View 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.

why.not.just.vector.memory

Vector databases retrieve similar text. Bilinc manages agent state.

Long-running agents do not only forget. They also remember the wrong things, overwrite useful context, and lose the trail behind important decisions. Bilinc wraps memory with the controls needed for durable state.

Compare memory models Review boundaries

# production memory questions

Was this memory verified before it was written?
Did it contradict prior agent state?
Which run, tool, or operator created it?
Can the team audit why state changed?
Can the agent roll back after a bad write?

Vector memory

Retrieves similar text and helps with semantic search.

Bilinc state plane

Adds verification, revision, provenance, snapshots, rollback, and audit around memory.

operator routes

Pick the path that matches your deployment reality.

Bilinc 2.1.3 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.3, 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

// MODULE_LIST.EXE

CORE CAPABILITIES

Everything a production state layer for autonomous agents should have.

01. VERIFIABLE

□

VERIFIABLE STATE

Z3-backed verification before every commit. State passes validation logic — never blindly stored. Full audit trail for replayable history.

PRODUCTION-CAPABLE

02. BELIEF

□

BELIEF REVISION

AGM-style belief revision machinery for changing or conflicting agent state. Controlled updates under contradiction — no silent data loss.

SUPPORTED

03. DURABLE

□

DURABLE PERSISTENCE

Hosted storage and entitlement gates. Snapshot, recall, and audit primitives for production durable state workflows.

PRODUCTION-CAPABLE

04. OBSERVABILITY

□

OBSERVABILITY

Real operator surface. /health (liveness + readiness) and /metrics (Prometheus-compatible) over authenticated HTTP. bilinc_ prefix metrics.

PRODUCTION-CAPABLE

05. KNOWLEDGE

□

KNOWLEDGE GRAPH

Semantic memory projected into a traversable graph. Contradiction analysis, structural queries, and graph-based belief coherence checks.

SUPPORTED

06. MCP

□

MCP + AUTH

20 MCP tools over stdio (trusted local) and HTTP (bearer auth + rate limiting). Production-hardened transport with 401/429 enforcement.

PRODUCTION-CAPABLE

// 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

use.with.your.agent

Start with one hosted memory contract, then wire it into your agent.

Bilinc should be easy to test from a single terminal and still make sense when the same agent workflow becomes a team-owned production surface.

Codex / Claude / Cursor

Paste the MCP config and give your agent a memory contract before risky work.

Agent recipes

Python agents

Use CloudClient directly for verifiable hosted commit, recall, status checks, and durable memory operations.

Python SDK

Hosted Cloud API

Issue workspace-scoped API keys and call commit/recall over authenticated HTTP.

Cloud quickstart

Team operations

Use shared workspaces, billing entitlements, and audit history when agent state becomes operational.

Billing posture

Recommended first run:pip install -U bilinc->bilinc start->bilinc quicktest

// 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.933

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-06-02

□

KNOWLEDGE-UPDATE

100.0%

MULTI-SESSION

99.2%

SINGLE-ASSISTANT

96.4%

PREFERENCE

93.3%

SINGLE-USER

100.0%

TEMPORAL

96.2%

ConvoMem 98.0% and LoCoMo 90.35% remain internal ReARC regression checks, not official dataset claims.

// ARCH_MAP.SYS

SEVEN-LAYER ARCHITECTURE

One coherent state plane. Every layer with a clear responsibility.

CLOUD SDK LAYER

CloudClient + MCP adapter — hosted commit, recall, status

PRODUCTION

HOSTED PERSISTENCE

Bilinc Cloud — durable storage, retention, entitlement gates

PRODUCTION

VERIFICATION & AUDIT

Z3-backed verification — replayable state history

SUPPORTED

BELIEF MANAGEMENT

AGM revision — controlled updates under contradiction

SUPPORTED

KNOWLEDGE GRAPH

Semantic memory — traversal + contradiction analysis

SUPPORTED

TRANSPORT LAYER

MCP stdio (local) + HTTP (bearer auth + rate limiting)

PRODUCTION

OPERATIONS LAYER

/health + /metrics — Prometheus-compatible monitoring

PRODUCTION

// SYSTEM_ROADMAP.DAT

DEVELOPMENT ROADMAP

Where we are. Where we're going.

PHASE 01 — CORE STATE ENGINE

□

v1.0.4 — SHIPPED

✓CloudClient API (commit, recall, status)
✓Hosted persistence + entitlement gates
✓Snapshot, diff, rollback primitives
✓Z3-backed verification layer
✓AGM belief revision engine
✓Knowledge graph module

PHASE 02 — PRODUCTION TRANSPORT

□

v1.0.4 — SHIPPED

✓MCP stdio transport (trusted local)
✓MCP HTTP (bearer auth + rate limit)
✓20 MCP tools surface
✓/health + /metrics (Prometheus)
✓Cloud runtime and billing guardrails

PHASE 03 — EVIDENCE-AWARE RECALL

□

MAIN — LANDED

✓Recall capture and replay metrics
✓Attributed claim projection
✓Read-only contradiction probes
✓Recall profiles: fast / balanced / verified / deep
✓Entity and backlink projection

PHASE 04 — INTEGRATIONS

□

IN PROGRESS

►LangGraph official adapter
►CrewAI plugin
►AutoGen bridge
►OpenAI Agents SDK hook
►Claude / Anthropic SDK integration

PHASE 05 — HOSTED CLOUD

□

LIVE CLOUD

►Public pricing published
►Entitlements remain runtime authority
►Pro and Team checkout live
►Managed retention and team operations
►Scale and enterprise rollout review

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.3 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.