# Brocoding Base URL: https://brocod.ing/v1 Key environment variable in examples: BROCODING_API_KEY Default authentication: Authorization: Bearer BROCODING_API_KEY ## Safe operating rules 1. Keep API keys out of source, screenshots, chat logs, browser code, and Git. 2. Use the Default key issued with your account. Do not add extra client-specific keys unless a Brocoding operator asks you to. 3. Verify the exact endpoint used by the client. A green chat ping does not prove Responses or Anthropic Messages. 4. Configure clients through an isolated home/profile or child-process environment. 5. Prove before, Bro, after, and rollback behavior before calling a client setup Verified. ## First request ~~~bash curl -X POST "https://brocod.ing/v1/responses" \ -H "Authorization: Bearer $BROCODING_API_KEY" \ -H "Content-Type: application/json" \ -d '{"model":"deepseek-v4.1","input":"Say hello in one sentence."}' ~~~ Anthropic Messages accepts x-api-key or the same Bearer header. Gemini-native routes accept x-goog-api-key or ?key=. Raw keys without the Bearer prefix remain accepted on OpenAI-compatible routes. ## Public verified operations - GET /v1/models - POST /v1/responses - POST /v1/chat/completions - POST /v1/messages Embeddings, speech recognition, speech translation, text to speech, rerank and moderation have no models on sale yet and are not part of this catalog. Additional operations are documented as Experimental until their model-specific contract checks pass. The full experimental catalog: /v1/responses/compact, /v1/completions, and /v1beta/models/{model}:generateContent. ## Codex CLI isolation Create a separate CODEX_HOME such as ~/.codex-bro. Its config.toml should contain: ~~~toml model = "gpt-6-astra" model_provider = "bro" [model_providers.bro] name = "Brocoding" base_url = "https://brocod.ing/v1" env_key = "BROCODING_API_KEY" wire_api = "responses" ~~~ Read BROCODING_API_KEY without echoing it, export it only in the current terminal, then run CODEX_HOME="$HOME/.codex-bro" codex. Unset both variables to return to the ordinary official Codex path. ## Claude Code isolation For one terminal session, set ANTHROPIC_BASE_URL=https://brocod.ing and ANTHROPIC_AUTH_TOKEN to the Bro key, then start claude from that terminal. Run /status to confirm the base URL and credential source. Unset both variables to return to the saved claude.ai login. ## Grok Build isolation Use a separate GROK_HOME and define a custom model with base_url=https://brocod.ing/v1, env_key=BROCODING_API_KEY, and api_backend=responses. Run grok inspect before grok -m bro. Unset GROK_HOME and BROCODING_API_KEY to return to the default account. ## T3 Code profile Use https://brocod.ing/docs/t3-code for a public, no-secret profile. It enables one provider, Bro Pi, with every Bro model, so there is no provider to choose; Bro Claude, Bro Grok, and Bro OpenCode are configured but off, and Bro Codex is not set up. T3's official providers are not changed. It creates ~/t3_code, adds Bro GPT 6.1 Sol to Favorites, defaults effort to Medium, and limits Bro Claude to Opus 5.5, Sonnet 5.5 and Fable 5.1. The Bro model order is GPT 6 Astra; Grok 4.7; GPT 5.6 Sol, GPT 6.1 Sol, GPT 6 Luna; Opus 5.5, Sonnet 5.5, Fable 5.1; DeepSeek V4.1 Flash; GLM 5.3, GLM 5.3 Flash, GLM 5.3 FlashX; Gemini 4 Argon, Gemini 3.8 Flash; MiMo 2.6 Pro (OpenCode), MiMo 2.6 Flash. Do not put an API key in the public profile. T3 Code stores sensitive provider values locally, so enter the Default Brocoding key after import in Bro Pi BRO_API_KEY (and, only if you turn them on, in Bro Claude ANTHROPIC_AUTH_TOKEN and Bro Grok BRO_API_KEY). Bro Grok must use the isolated GROK_HOME=~/.grok-bro. Before importing, verify grok --version and the resolved Grok executable path; use the managed binary or a symlink rather than a stale copy. Run grok inspect and grok models with the isolated GROK_HOME. T3 starts grok agent stdio, so the provider must reach ready instead of ACP startup timed out after 15000ms. Restart T3 after profile changes, create a fresh thread, and require the exact no-tools response T3_GROK_OK. All three client integrations remain Experimental until a clean before/Bro/after/rollback E2E is recorded with a real account key. ## Links Guides and help: - https://brocod.ing/docs/quickstart - https://brocod.ing/docs/authentication - https://brocod.ing/docs/t3-code - https://brocod.ing/docs/compatibility - https://brocod.ing/docs/troubleshooting - https://brocod.ing/docs/changelog API reference: - https://brocod.ing/docs/models - https://brocod.ing/docs/responses - https://brocod.ing/docs/response-compaction - https://brocod.ing/docs/chat-completions - https://brocod.ing/docs/anthropic-messages - https://brocod.ing/docs/legacy-completions - https://brocod.ing/docs/gemini-generate-content