Account

Start from a confirmed Cloud account.

Sign up with your work email, confirm the address, then open the Cloud console. Public signup starts a 7-day Cloud trial; paid plans are managed from the authenticated billing console.

Start 7-day trial Sign in Billing console

First run path

Five steps from install to first memory.

1. Run bilinc start

The CLI shows the signup path and the exact next command.

2. Start 7-day Cloud trial

Create a public Bilinc Cloud account and confirm email.

3. Create one Cloud key

Bootstrap a workspace and issue one hosted key for the runtime.

4. Run bilinc login

Save the key locally so commit, recall, status, and quicktest work without repeated env setup.

5. Run bilinc quicktest

Write one durable memory, recall it, and verify Cloud status.

API key

Issue one key per runtime or environment, then let the CLI store it locally.

Create

Open API keys, name the key after the runtime, and copy the value while it is shown once.

Store

Use bilinc login for local development. Use BILINC_API_KEY in server, CI, or hosted agent secrets.

Rotate

Revoke old keys when an agent, CI job, or workspace boundary changes.

Observe

Usage, billing, and audit events are visible in the Cloud console.

CLI smoke

Prefer this path before raw API calls.

pip install -U bilinc
bilinc start
bilinc login --api-key bil_live_...
bilinc quicktest

bilinc commit --key USER_PREF --value '{"theme":"dark"}'
bilinc recall --query "user preference"
bilinc status

Commit

Write one durable memory.

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" }
  }'

Recall

Read the state back through a recall profile.

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
  }'

Agent handoff

Give this prompt to your coding agent.

Paste this into Codex, Claude Code, Cursor, or another trusted agent runtime after you have stored the API key in that runtime's secret manager.

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

Connect an agent to hosted memory.