littlebigbrain — Python SDK
The Python client for Little Big Brain — write graph facts and query one immutable published snapshot. Built on httpx + pydantic; ships sync and async clients.
pip install littlebigbrain # imports as `lbb`
Quickstart
from lbb import LbbClient
with LbbClient(
"https://0abc1def--production.db.eu.littlebigbrain.com",
api_key="lbb_sk_live_...",
graph="main",
) as lbb:
graph = lbb.graph("main")
# 1. Write a fact.
graph.facts.create({
"triplets": [{
"source": {"type": "CONCEPT", "name": "handbook", "key": "doc:42"},
"relation": "RELATED_TO",
"target": {"type": "CONCEPT", "name": "vacation policy", "key": "passage:42:1"},
"evidence": "Employees receive 25 days of annual leave.",
}],
}, idempotency_key="doc:42:v1")
# 2. Publication is automatic. Inspect one coherent watermark when needed.
published = lbb.read_snapshot_model()
print(published.snapshot.served_at_seq, published.query_lag_commits)
# 3. Query the snapshot with SPARQL.
rows = lbb.sparql_select(
"SELECT ?s ?o WHERE { ?s <policy:annual_leave> ?o } LIMIT 5"
)
for row in rows:
print(row["s"], row["o"])
For hosted use, pass the exact endpoint_url shown on the stack's Connect
page. Omitting base_url retains the loopback default for local/self-hosted
development only; graph and branch remain ordinary client scope parameters.
Facts are graph-scoped (lbb.graph("main").facts); search and published-snapshot
inspection use the client's active graph/branch scope.
Examples
Search with filters. Use the request body to filter before ranking — here, only facts an ACL principal may see:
results = lbb.graph_search({
"query": "incident response runbook",
"targets": ["entities"],
"search": {
"filters": {
"op": "overlaps",
"field": "acl",
"values": ["user:rino@example.com", "group:engineering"],
},
},
"top_k": 20,
})
Bulk import. Load many records as NDJSON in one call:
lbb.graph("main").facts.import_ndjson(
[
{"source": {"type": "DOC", "name": "handbook", "key": "doc:42"},
"relation": "HAS_PASSAGE",
"target": {"type": "PASSAGE", "name": "leave-policy", "key": "p:42:1"}},
# …one record per line
],
idempotency_key="handbook-batch-1",
)
For large or long-running loads, submit a streamed durable job:
accepted = lbb.submit_import_ndjson(
records(),
idempotency_key="hubspot:portal-42:run-2026-07-29",
)
completed = lbb.wait_for_import_job(accepted.job_id)
print(completed.state, completed.committed_commit_seq)
The async client accepts an async iterable as well. Success means all grouped
commits are durable and final publication was enqueued; it does not mean
published indexes have already reached committed_commit_seq. Empty iterables
are rejected locally before an import POST is sent.
Time-travel read. Pin a SPARQL query to a past instant — results reflect the graph as it was then:
results = lbb.sparql(
"SELECT ?s ?p ?o WHERE { ?s ?p ?o } LIMIT 10",
as_of_valid_time="2026-01-01T00:00:00Z",
)
print(results.vars)
for row in results: # iterates flat {var: value} dicts
print(row)
The async client mirrors every method — async with AsyncLbbClient(...) as lbb: and await each call.
Errors & retries
Methods return parsed dictionaries and raise LbbError (with status_code, code, param, request_id, and doc_url) on any non-2xx response. Safe reads and idempotency-keyed writes retry 429/5xx and transport failures with full-jitter backoff, bounded by a retry budget (retry_budget_ms, default 60s) rather than a fixed count, and honor Retry-After — a terminal error the server marks non-retryable surfaces immediately. Use raw_request(...) for response headers, request id, and retry/timing metadata.
More
Beyond the quickstart: entities.sample(type=..., limit=...) for a bounded
published-generation sample and entities.filter_by_attributes(...) for
relation-bound structured SPARQL; and ontology/schema for ontology
inspection and atomic schema publication. SPARQL is the one query language on
the API. Typed Pydantic responses are exposed by
matching *_model helpers; generated models live in lbb.models.
Full reference and guides: docs.littlebigbrain.com/sdks/python.
Develop
python3 -m venv .venv
.venv/bin/pip install -e ".[dev]"
ruff check lbb tests
mypy lbb
pytest tests
lbb/models.py is generated from the API contract — change the Rust API types and regenerate rather than editing it by hand.
Release files for littlebigbrain 0.11.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| littlebigbrain-0.11.0.tar.gz | 114.0 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| littlebigbrain-0.11.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 212.8 kB
Release files / littlebigbrain-0.11.0.tar.gz
| Download URL | littlebigbrain-0.11.0.tar.gz |
|---|---|
| Size | 114.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f23b28a70922c1b7056edb62a1211f4aa97d542ef585563e27a72f9638c88a89
|
|
BLAKE2b-256 checksum How to use checksums |
464051d298c15938dda19fd901a65eb14df3db3bda9b029926759ba32a4e4fed
|
| 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 Aug 21, 2026.
Transparency logRelease files / littlebigbrain-0.11.0-py3-none-any.whl
| Download URL | littlebigbrain-0.11.0-py3-none-any.whl |
|---|---|
| Size | 98.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
09ef022755c7b3e3eb42b29d4eb73c54b02233cde1b81dd8d1a45600949d5124
|
|
BLAKE2b-256 checksum How to use checksums |
7710ae207f88154b9c50b758d31cc72d16d06013578410d1297eb901eac62628
|
| 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 Aug 21, 2026.
Transparency log