Choosing an SDK
Every client below speaks the same HTTP API and authenticates with the same
stack API key. They are interchangeable — write with
one, read with another, all against one graph. The first-party SDKs
(@lbb/client, lbb) are generated from one API contract, so the shapes match
across languages — see Types & generated models.
At a glance
Section titled “At a glance”| SDK / surface | Package | Runtime | Reach for it when… |
|---|---|---|---|
| TypeScript client | @lbb/client |
Node 18+, browsers, edge workers | You’re building a JS/TS app, API route, or edge function |
| Python client | lbb-sdk (imports as lbb) |
Python 3.9+ (httpx + pydantic) |
Scripts, notebooks, data/ML pipelines |
| MCP server | @lbb/mcp |
Node (stdio) or hosted HTTP | You want an AI agent (Claude, Cursor, Codex) to read/write the graph |
| HTTP API | — | Any language | No SDK for your language, or you want the native SPARQL Protocol |
| CLI | — | Self-hosted deployments | Operating a self-hosted deployment (coming with self-hosting) |
Same three verbs everywhere
Section titled “Same three verbs everywhere”Whatever you pick, the shape is the same: write facts → build indexes → query. The Quickstart shows all three verbs side by side in TypeScript, Python, and cURL.
Pick one
Section titled “Pick one”TypeScript — @lbb/clientDependency-free fetch wrapper; typed request/response shapes.
Python — lbbSync + async, dict or typed Pydantic models.
MCP server — @lbb/mcpSix task-shaped tools for agents; local stdio or hosted OAuth.
HTTP API & SPARQLREST + the native SPARQL 1.1 Protocol endpoint.
CLI (self-hosted)Local control plane for self-hosted deployments (coming soon).