Understand the environments
| Key or environment | Base URL | What it does |
|---|---|---|
Sandbox key (gw_sandbox_) | https://gateway.accountablehq.com | Simulated sandbox-chat model. Free, no agreement or credits; content never reaches a provider and is not stored. |
Production key (gw_live_) | https://gateway.accountablehq.com | Approved real models, billed from prepaid credits. Requires signed agreements. Currently an invitation-only preview. |
Local demo (gw_test_) | http://127.0.0.1:4317 | Developer machine with simulated models and test credits. |
Sandbox and production keys share one base URL; the key decides which models it can call. Healthcare data is allowed only on production keys and routes that meet every activation requirement.
Separate credentials and balances
Keys, workspace records, and wallets belong to an environment. Test credits cannot fund live requests, and demo databases cannot be reused as live wallets. Keep GATEWAY_BASE_URL and GATEWAY_API_KEY paired in your secret configuration.
Sandbox keys
Use a sandbox key while you build: same endpoints, authentication, errors, streaming, structured outputs and tool calling, with a simulated model. Requests are limited to 10 per minute per key and 1,000 per workspace per UTC day. A sandbox key can never call a real model, and a production key cannot call sandbox-chat. Do not send patient information to the sandbox; it is for integration testing.
A live key is not a blanket approval
Model and healthcare access are evaluated at request time. An agreement expiry or changed provider route can stop dispatch even for a previously usable key. Treat changes in eligibility as actionable failures, not as a reason to route around controls.