Install

Install the Cloud SDK, then attach Bilinc to your agent.

The product path is simple: start a 7-day Cloud trial, set BILINC_API_KEY, then use the Python SDK, CLI, or MCP adapter from your agent runtime.

Start 7-day Cloud trial Install Cloud SDK MCP setup

Cloud SDKpip install bilinc

Agent bridgeMCP config

Trial7 days

RuntimePython 3.10+

Start a 7-day Cloud trial

Create a Bilinc Cloud account. No card is required for the hosted trial.

https://bilinc.space/signup

Confirm email and open Cloud

Confirm the email link, then open the Cloud dashboard to bootstrap your default workspace.

https://bilinc.space/dashboard

Create a workspace API key

Issue one hosted key per runtime or environment. Copy it once and store it in your server or agent secrets.

BILINC_API_KEY=bil_live_...

Install the Cloud SDK

Use the PyPI package as a thin SDK, CLI, and MCP adapter for Bilinc Cloud.

pip install bilinc

Run the first commit and recall

Set BILINC_API_KEY, then commit and recall one memory from your agent runtime.

import os
from bilinc import CloudClient

client = CloudClient(api_key=os.environ["BILINC_API_KEY"])

client.commit(
    "agent.intent",
    {"goal": "ship reliable memory"},
    memory_type="semantic",
    importance=0.9,
)

results = client.recall("reliable memory", limit=5)

Attach MCP

Add the Cloud MCP adapter to a coding agent when you want recall available during live work.

{
  "mcpServers": {
    "bilinc": {
      "command": "python",
      "args": ["-m", "bilinc.cloud_mcp"],
      "env": { "BILINC_API_KEY": "bil_live_..." }
    }
  }
}

Agent prompt

Give this to the agent after creating a Cloud key.

You are working with Bilinc Cloud as the hosted memory/state plane.

Use the API key only as a bearer token. Never print, log, commit, or expose it.

Base URL: https://bilinc.space

When durable agent memory matters:
1. Commit important state with POST /api/cloud/memory/commit.
2. Recall prior state with POST /api/cloud/memory/recall.
3. Keep keys stable and namespaced, for example agent.goal, user.preference, project.status.
4. Use semantic memory for durable facts, episodic memory for run outcomes, and procedural memory for reusable workflows.
5. If an operation fails, treat the write as not durable until the API returns success.

Required headers:
Authorization: Bearer <BILINC_API_KEY>
Content-Type: application/json

Next steps

Pick the path that matches the work.

SDK quickstart Cloud quickstart Agent recipes DevTools Trust posture

CLI path

export BILINC_API_KEY=bil_live_...
bilinc commit --key USER_PREF --value '{"theme":"dark"}'
bilinc recall --query "user preference"
bilinc status

Raw API path

curl https://bilinc.space/api/cloud/memory/commit \
  -H "Authorization: Bearer $BILINC_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "key": "agent.memory.bootstrap",
    "value": {
      "goal": "keep durable state between runs",
      "owner": "agent-runtime"
    },
    "memoryType": "semantic",
    "importance": 0.8,
    "metadata": { "source": "cloud-quickstart" }
  }'

curl https://bilinc.space/api/cloud/memory/recall \
  -H "Authorization: Bearer $BILINC_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "query": "durable state between runs",
    "profile": "balanced",
    "limit": 5
  }'