01Output
Structured by default
JSON on the standard output, diagnostics on the standard error, and a line per state to follow a job.
CLI · in development
The whole pipeline, from one command line.
Sign in, set up projects and Spaces, add memory, search, and manage keys and policy with gb. Made for people at a terminal and for the scripts they write.
In development. Not available yet.
gb auth login
Signed in. The session stays in your keychain.
gb init --project … --space …
The project file is written, with no secret in it.
gb memories ingest --document contract.pdf
{"jobId":"job_…","status":"Accepted"}
gb jobs get job_… --fields state
{"state":"succeeded"}
gb mcp serve
The same operations, as tools for your agents.
Built for scripts
A command line a program can rely on.
02Exit status
Errors you can act on
Each kind of refusal has its own exit status and a named action, so a script never parses a message.
03Secrets
Never on the screen
Keys and sessions go to the system keychain or a private file: never an argument, never printed.
04Sealed
Encrypted before it leaves
What you add is sealed for the masking service, after its certificates are checked, and every request is signed.
05Retries
Safe to run again
Retries, backoff and idempotency keys are built in: the same request twice is one operation.
06Discovery
It describes itself
gb describe shows each command's arguments, outputs and every error it can return.
What it covers
Every operation, one command each.
From the first sign-in to the last search.
| Area | Commands | What for |
|---|---|---|
| Access | gb auth | Sign in and out, rotate your key, see where you stand. |
| Set-up | gb projects gb spaces gb apps gb init | Projects, the Spaces that keep memory apart, and the apps that use them. |
| Control | gb keys gb policy | Keys bound to the one client that holds them; the signed policy each request obeys. |
| Memory | gb memories ingest gb jobs get gb search | Add documents and notes, follow each job to its end, search in scope. |
| Agents | gb mcp serve | A local MCP server, so an agent can add to memory and search it. |
One surface
Declared once. The same in every tool.
Each operation is declared once and generated into the CLI, the SDKs and the MCP server, so they never drift apart.
01CLI
For people and scripts
Every operation from a terminal, a CI job or a shell script.
02SDKs
TypeScript and Python
The same operations as typed calls in your own code.
03MCP
For agents
Ingest, search and job state as tools an agent can call.
04HTTP
Any language
The API under all three, and the drop-in router for model calls.
No SDK for your language? Call gb as a process: its output and exit statuses make it a bridge.