BBramaDocs
Browse documentation

Provider-neutral LLM access

One authenticated gateway for every model route.

Brama owns client identity, provider capabilities, subscription entitlements, bounded dispatch, and normalized results. Start here to integrate, operate, and recover the gateway without distributing provider credentials.

Quick startDownloadHow Brama works

Featured documentation

Read topic

Quick start

How do you go from no Brama state to one answered request? This page is the one happy path: install an exact release, run the safe first command, provision the installation's trust material,…

Read topic

HTTP API

Brama serves one HTTP listener, loopback by default (127.0.0.1:8080, port from brama serve --port, address from BRAMABINDADDRESS). Every route — including /health — sits behind the transport…

Read topic

Architecture

What Brama owns, what it deliberately does not, and how one request flows through it. Brama is one Rust process (axum) serving one HTTP listener; its entire job is to turn an authenticated,…

Read topic

Runbook

Something at the gateway looks wrong — which command do you run first, and what does its answer mean? Each entry starts from the symptom, quotes the exact sentence the product uses (every st…

Read topic

Brama examples

This directory is the canonical catalog of supported Brama user outcomes. Each example states version/status, risk, environment, preconditions, inputs, side effects, ordered public-interface…

Read topic

Entitlement

Which account pays for which request. An entitlement is the decision — made per request, from the caller's proven identity and the request's shape — about the one pool that may fund it. Ther…

Complete documentation

All topics

Start here

API & operations

Concepts

Providers

Product contracts

Task guides

Agent integration