Bilinc
Bilinc
Hosted memory infrastructure for coding 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?" — that is the layer Bilinc provides.
Bilinc 2.1.5 on PyPI is the public cloud-only package: a thin Python SDK, CLI, and MCP adapter for Bilinc Cloud. It does not ship the local StatePlane, storage backends, eval, observability, integrations, or server runtime internals.
Use Bilinc when
A long-running coding agent needs to recall prior decisions before a risky edit.
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.
Related MCP server: mem-universe
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 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.
Start in 60 Seconds
pip install -U bilinc
bilinc startbilinc start is the first-run guide. The activation target is simple: reach a
passing bilinc quicktest, which performs one hosted commit, one hosted recall,
and one Cloud status check.
Start the 7-day Bilinc Cloud trial at https://bilinc.space/signup.
Confirm email.
Create one hosted API key in the Cloud dashboard.
Connect the CLI:
bilinc login --api-key bil_live_...
bilinc quicktestIf you prefer a browser guide, open https://bilinc.space/install and follow the same four-step path.
MCP Adapter
Bilinc exposes a standard Model Context Protocol server over stdio, so any MCP-compatible client can connect — Claude Code, Codex, Cursor, Hermes-Agent, opencode, and others.
{
"mcpServers": {
"bilinc": {
"command": "python",
"args": ["-m", "bilinc.cloud_mcp"],
"env": { "BILINC_API_KEY": "bil_live_..." }
}
}
}Three tools, deliberately:
Tool | What it does |
| Write durable agent state. Each write carries provenance — which run, tool, or operator produced it. |
| Retrieve prior context and decisions before acting. |
| Check hosted Cloud health and account state. |
Documented client setups: Claude Code · Codex · Cursor · any MCP client
The adapter exposes hosted commit, recall, and status operations. It does not bundle local runtime internals.
Python SDK
from bilinc import CloudClient
client = CloudClient() # reads BILINC_API_KEY or a key saved by `bilinc login`
client.commit("agent.goal", {"ship": "reliable memory"}, memory_type="semantic")
results = client.recall("agent goal", limit=5)
status = client.status()For server, CI, and hosted agent runtimes, store the key as BILINC_API_KEY.
CLI
bilinc status
bilinc commit --key agent.goal --value '{"ship":"reliable memory"}'
bilinc recall --query "agent goal"
bilinc doctorUseful first-run commands:
bilinc start
bilinc login --api-key bil_live_...
bilinc quicktest
bilinc mcp installHosted Endpoints
Health:
GET https://bilinc.space/api/cloud/healthCommit:
POST https://bilinc.space/api/cloud/memory/commitRecall:
POST https://bilinc.space/api/cloud/memory/recall
Authenticated memory operations require an active Bilinc Cloud entitlement.
Benchmark receipt
Archived research receipt, LongMemEval-s cleaned retrieval fixture, 500 questions: R@5 98.0%, NDCG@5 0.933, with no LLM reranker and no paid API.
This is an archived retrieval-component result — not a current hosted SLA, not an end-to-end agent score, and not a competitor ranking. Published memory-system scores use different metrics, datasets, and levels of LLM assistance, so they are not directly comparable. Present this receipt only with this scope attached.
Compare
Answer guides
Links
Website: https://bilinc.space
Signup: https://bilinc.space/signup
Install guide: https://bilinc.space/install
Quickstart: https://bilinc.space/docs/quickstart
Cloud quickstart: https://bilinc.space/docs/cloud-quickstart
Migration guide: https://bilinc.space/docs/migration-v2
MCP setup: https://bilinc.space/docs/mcp
Machine-readable index: https://bilinc.space/llms.txt · https://bilinc.space/ai-index.json
License
BUSL-1.1. See LICENSE.
Maintenance
Tools
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/atakanelik34/Bilinc'
If you have feedback or need assistance with the MCP directory API, please join our Discord server