The assistant looks up and cites passages from this project’s guide. These are original English recordings, not live answers. Retrieval success does not establish answer correctness.Der Assistent sucht und zitiert Abschnitte im Projektleitfaden. Dies sind englische Originalaufzeichnungen, keine Live-Antworten. Erfolgreiche Suche belegt nicht die Richtigkeit der Antwort.
Where should I keep my provider API key, and how do I point the project configuration at it without pasting the secret anywhere?
Recorded answer byAufgezeichnete Antwort von GPT 6 Luna
Keep the provider API key in the repository-root .env file, which is gitignored. In config/providers.toml, reference it with an env:NAME pointer (for example, env:OPENAI_API_KEY) rather than pasting the key. The project resolves that named environment variable when needed.
Cited passages (original English)Zitierte Abschnitte (englisches Original)
connect-provider · passage 0Connect a provider with BYOK and wam doctor Every model call in this project goes through a Connection: a small record that says where to call, which wire protocol to speak, and which environment variable holds the key. You bring your own key (BYOK). Keys live only in the gitignored .env file at the repository root and are referenced from configuration as env:NAME pointers, never pasted into code, logs, traces, or recordings.
connect-provider · passage 2Presets and the credential rule The gateway preset used for the benchmark is exposed as four connections sharing one key, one per API format, beside the standard openai, anthropic, gemini, openrouter, local-openai-compatible, and custom presets. resolve_credential reads the named variable at call time and returns the key value, or None for keyless connections. Only the credentials module and the live benchmark runner may touch the environment for a secret;
What are the four connection protocols in this project, and which provider-side API does each one speak?
Recorded answer byAufgezeichnete Antwort von GPT 6 Luna
The four connection protocols and the provider-side APIs they speak are: OPENAI_COMPATIBLE — Chat Completions endpoints; OPENAI_RESPONSES — the Responses API; ANTHROPIC — the Messages API; and GEMINI — the Google Generative Language API.
Cited passages (original English)Zitierte Abschnitte (englisches Original)
connect-provider · passage 1How a connection is described A connection has an id, a provider label, a protocol, a base URL, and a credential reference. The protocol is one of four fixed values: OPENAI_COMPATIBLE for Chat Completions endpoints, OPENAI_RESPONSES for the Responses API, ANTHROPIC for the Messages API, and GEMINI for the Google Generative Language API. The base URL never carries credentials; a URL with an @ before its first path slash is rejected by the contracts.
What information does the doctor command show for every connection, and which result values can it report?
Recorded answer byAufgezeichnete Antwort von GPT 6 Luna
For each configured connection, wam doctor shows its id, protocol, outcome, and latency in milliseconds. It can report these outcome values: OK, CONFIG_INVALID, CREDENTIAL_MISSING, CREDENTIAL_REJECTED, ENDPOINT_UNREACHABLE, RATE_LIMITED, PROTOCOL_UNSUPPORTED, or UNKNOWN.
Cited passages (original English)Zitierte Abschnitte (englisches Original)
connect-provider · passage 3Checking what works with wam doctor Run wam doctor before spending anything. It probes every configured connection and prints one row per connection with its id, protocol, outcome, and latency in milliseconds. The outcome vocabulary is fixed: OK, CONFIG_INVALID, CREDENTIAL_MISSING, CREDENTIAL_REJECTED, ENDPOINT_UNREACHABLE, RATE_LIMITED, PROTOCOL_UNSUPPORTED, or UNKNOWN. Scripts and the runner switch on these values without guessing, and the detail field is scrubbed of headers and key material first.