Account & AI credits
Register, buy credits, mint a bur_ key, and link the daemon for metered AI — or stay on your own Anthropic key.
Bureau's browser is free and local. You only need an account if you want the
daemon's AI actions (the llm.ask / intel.judge reasoning seam,
research_run, vision) without holding your own Anthropic key.
Two ways to power AI actions
The daemon resolves the model in a fixed order (see lib/anthropic-model.ts):
- BYOK — your own key wins. If
ANTHROPIC_API_KEYis set in the daemon's environment, calls go straight to Anthropic. Free to Bureau, works offline, no account needed. This always takes precedence. - Proxied — Bureau Cloud. Otherwise, if you've run
bureau linkand stored abur_token, calls route through Bureau's metered proxy atPOST <server>/bureau/v1/ai/messages(the token rides thex-api-keyheader). Credits are debited per real token usage. - Neither. No key and no link → no model. The reasoning steps degrade to a no-op instead of erroring, so browser/scrape/social tools keep working.
The link flow
-
Register on bureau.sh and start with your welcome credits.
-
Buy credits from Pricing when you need more (one-time packs).
-
Mint an API key on your account page. A
bur_…key is shown once at creation with the ready-made command:bureau link --server https://api.bureau.sh --token bur_xxxxxxxx -
Link the daemon by running that command. The
bur_token is stored in the macOS Keychain (servicebureau-cloud); the server URL goes to~/.agentproto/bureau/cloud.json. The token is never printed again, never written to the JSON.
For local development the server is http://localhost:3055:
bureau link --server http://localhost:3055 --token bur_xxxxxxxxManaging the link
bureau link --status # show the stored server (no secret)
bureau link --logout # forget the connection + delete the Keychain tokenThe token must be a Bureau API key with the ai:proxy scope (it starts with
bur_; bureau link refuses anything else).
Not to be confused with bureau login
bureau link (Bureau Cloud, the metered AI proxy) is a separate concern
from bureau login (which stores a Guilde connection for
bureau connect-token). They use different config and different token prefixes.
See Pricing & credits for what a call costs.