Developers
There isn’t an API yet.
No public API, no keys, no endpoints, no SDK. Here’s the direction it might take, and what you can do today.
Nothing is deprecated or coming out of beta — it has never existed. If you need one, say so: right now, demand is the entire roadmap.
The nuance
Sort of, but not for you.
Sarabellum is a browser app talking to a Postgres database through a generated REST layer, so in the narrow technical sense an HTTP API is what makes it work at all.
But it isn’t a product. It’s an internal contract that changes whenever a feature changes, with no versioning, no stability promise and no documentation. Building against it would mean building on something that breaks without warning and owes you nothing. That’s not an API; it’s a trap with a URL.
A real one means committing to stability, and committing to stability at this size means never being able to change anything. That trade isn’t worth making until someone actually needs it.
The direction, if it happens
Read before write. Pull your tasks, focus sessions and check-ins out for your own dashboards or analysis. Lower risk, and probably most of the value.
Capture before everything. If writes come, the first one is “create a task from somewhere else” — that’s the thing people actually want.
Tokens, not OAuth. A personal access token you generate for yourself, scoped to your own data. Nobody needs a third-party app ecosystem here.
The more interesting question
Honestly, MCP is probably more useful than REST for an app like this — letting your own AI assistant read and act on your Sarabellum directly, the way Sara already does. That’s the version worth building, and it’s a thought rather than a plan.
Meanwhile
What you can actually do today.
Discord slash commands
The closest thing to an integration that exists. /add captures a task,
/brief reports your day, /sara and /s talk to
her. It’s currently wired to one specific setup — ask if you
want in.
Get your data out
No API needed. Ask and you’ll get an export — it’s your data and there’s no lock-in strategy here. Just ask.
Tell us what you’d build
The most useful thing on this page. A concrete “I want to do X” beats any amount of speculation about what an API should look like — and it’s how this would get prioritised at all.
Under the hood
Not documentation — just an honest description, since you’re on the developer page and probably curious. Sarabellum is a React 19 + TypeScript app built with Vite, on Supabase (Postgres with row-level security on every table) with Google OAuth, deployed on Vercel. Sara runs in serverless functions calling Anthropic’s Claude, so the API key never reaches the browser. The marketing site you’re reading is static HTML generated at build time, which is why it loaded instantly and shipped no JavaScript frameworks at you.
The repository is private. Questions about the architecture are welcome anyway: aolsendev@gmail.com.
Security researchers
If you’re here looking for an attack surface: the Security page has the disclosure policy, an honest list of what’s not been done, and a real thank-you for anyone who reports something properly.
Tell us what you’d build.
Right now, demand is the entire roadmap. The app is free in the meantime.