Most of the time, your agents reach Retia over MCP. But when you want to read or write the vault from your own code, a token-authenticated API is there.
If you're connecting an agent — Claude, Codex, Cursor — MCP is the easiest path and needs no code. The API is for when you want programmatic control from your own application.
Every request carries your token as a Bearer header — the same token your agents use. It identifies your workspace and scopes every call to your data. Nothing is reachable without it.
The API mirrors what your agents do: read projects, search the vault, and write notes. A small, predictable surface — growing as the product does.
A complete reference, SDKs, and rate-limit details live in the docs — the surface here is the core, and it grows with the product.
The same structured note your agents create over MCP — now from any language that can make an HTTP request.
Every token you create has a scope — and this is where Retia's whole philosophy shows. The most sensitive layer of your vault isn't locked to keep everyone out. It's locked so that only who you choose gets in. You decide what each token can see and do.
That's the point of the sensitive layer: not to hide things from everyone, but to let exactly the agent you authorize work on your behalf — without ever exposing your secrets to us, the operator.