Skip to main content

brain-db-sdk (Python)

The Python client for the Brain memory database. Speaks Brain's BRN0 wire protocol directly; no dependency on Brain's internal code.

Status: typed-graph verbs (Phase 6). The wire codec (Phase 1) is verified byte-for-byte against the shared conformance corpus (all 86 .bin/.json cases re-encode to identical bytes). On top of it, a synchronous connection layer (a transport over a socket, a Connection running the handshake HELLO → WELCOME → AUTH → AUTH_OK and request/response, a BrainClient holding the negotiated session), the three v1 verbs with ergonomic builders (encode(), recall() streaming to EOS / recall_frames(), forget()), a with_retry helper + RetryPolicy (exponential backoff, server retry_after_ms), and the typed-graph verbs: create_entity(), create_statement(), create_relation(), upload_schema(), and materialize_procedural(); and the space/session registry verbs: create_space() / list_spaces() / delete_space() and create_session() / list_sessions() / delete_session() for managing the per-request isolation unit (space) and conversation groupings (session) that a trusted principal targets via act_as. BrainClient is built on a MuxConnection: a background reader thread demultiplexes responses by stream_id, so every verb is concurrency-safe and many requests run in flight at once over one connection from multiple threads. A Pool opens a fixed set of such connections and hands them out round-robin for socket-level parallelism. Transparent reconnect and an asyncio client are later phases.

The full build plan is in the repo-root ../PLAN.md; the layered architecture is in ../ARCHITECTURE.md.

from brain_db_sdk import (
    BrainClient, EncodeBuilder, RecallBuilder, ForgetBuilder, RetryPolicy, with_retry,
)

with BrainClient.connect("127.0.0.1", 7878) as client:
    stored = client.encode(EncodeBuilder("the user prefers dark mode").build())
    answer = client.recall(RecallBuilder("ui preferences").limit(5).build())
    # answer.answer_kind is Single/Set (fact answer.values) or Episodic
    # (memory answer.results); NoSubject/NoMemory means "don't know".
    # Ride out transient ResourceExhausted/Unavailable; the stable request_id
    # makes the resend idempotent.
    req = ForgetBuilder(stored.memory_id).build()
    with_retry(lambda: client.forget(req), RetryPolicy())

Develop + verify against the corpus:

python3 -m venv .venv && .venv/bin/pip install cbor2 pytest
PYTHONPATH=src .venv/bin/python -m pytest tests/ -q

The integration suites run against a real server when BRAIN_SDK_IT_DATA is set, and skip otherwise; scripts/it-server.sh up boots one and prints the vars. Set BRAIN_SDK_IT_REQUIRED=1 wherever a server is meant to be reachable so a misconfigured one fails instead of reading as green.

Layout (folder-per-concern, mirroring the reference Rust SDK):

src/brain_db_sdk/
  wire/        frame + CBOR codec, opcodes, typed payloads (corpus-verified)
  errors.py    client error taxonomy (BrainError + subclasses)
  transport.py sync read/write of whole frames over a socket
  connection.py handshake + one-at-a-time request/response
  client.py    high-level BrainClient: connect, handshake, encode/recall/forget
  verbs.py     ergonomic EncodeBuilder / RecallBuilder / ForgetBuilder
  retry.py     RetryPolicy + with_retry (exponential backoff, server retry_after)

HTTP tier

For hosted Brain (the Arc cloud gateway) or a self-hosted brain-edge edge, the package also ships BrainHttpClient — a JSON-over-HTTP client with the same verb surface, field names, and error shape as the Rust and TypeScript SDKs (the canonical contract is ../HTTP_CONTRACT.md). Use it when you talk to Brain through an HTTP edge and authenticate with an API key; use the wire BrainClient above for a direct socket, streaming, transactions, and typed-graph management. It has no third-party dependency — pure urllib.

from brain_db_sdk import BrainHttpClient

brain = BrainHttpClient(api_key, base_url="https://api.arc-labs.ai")
stored = brain.encode(text="the kettle whistled")
answer = brain.recall(query="what whistled?", max_results=3)
who = brain.whoami()  # namespace + space_id + permissions

Dependencies: cbor2 (runtime), pytest (dev). CRC32C is pure Python.

The live HTTP edge smoke tests cover identity, capabilities, and a memory encode/recall/list/forget lifecycle across all SDKs. Run them from the repo root with BRAIN_SDK_IT_HTTP=https://edge.example BRAIN_SDK_IT_HTTP_KEY=brain_… scripts/edge-it.sh. License: Apache-2.0.

Metadata

Release files for brain-db-sdk 0.1.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for brain-db-sdk 0.1.0
File Size Uploaded
brain_db_sdk-0.1.0.tar.gz 173.1 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for brain-db-sdk 0.1.0
File Interpreter ABI Platform
brain_db_sdk-0.1.0-py3-none-any.whl Python 3 none any Details

Total release size: 276.5 kB

Release files / brain_db_sdk-0.1.0.tar.gz

Download URL brain_db_sdk-0.1.0.tar.gz
Size 173.1 kB
Tags Source
SHA-256 checksum
How to use checksums
56bcd3ae4748622add258cecaacde5306e939c833b48771849521a7f9834dc0a
BLAKE2b-256 checksum
How to use checksums
9af434b74a322242cdffdc6b89654be0b79e97243f16a0b7b08320d0485bbce7
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 6, 2026.

Transparency log

Release files / brain_db_sdk-0.1.0-py3-none-any.whl

Download URL brain_db_sdk-0.1.0-py3-none-any.whl
Size 103.4 kB
Tags Python 3
SHA-256 checksum
How to use checksums
496a89472e66f92db4d130eb1725bbc18c5d450c95e03d6d99f71b896f6a9d1a
BLAKE2b-256 checksum
How to use checksums
c5f5574bbafc383f33b72e0d2d3ad5ab2c2c501e120db1ca72461bf3d3976fc0
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 6, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

0.1.0 This release

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page