Do I need an OpenAI or AWS account?
Not for the intended standard Accountable-managed offering. Your application uses an Accountable Gateway key. Accountable owns the upstream provider connections. In the current local demo, no provider account is needed because the answers are simulated.
Why does the website show a model I cannot call?
The public library also shows planned models. Your key’s authenticated catalog is the discovery source for configured access. Healthcare readiness is a separate check.
Can I send real patient data now?
No. The public preview and private staging use synthetic data only. Provider BAA acceptance does not activate customer PHI on its own.
Why did I receive 409 rather than my old answer?
Duplicate requests are blocked, but the gateway does not store prompt/answer text for response replay. Inspect the original request’s status before deciding whether to create a new logical request.
Why are credits held after an error?
The provider’s outcome may be unknown. The hold prevents potentially incurred usage from being spent again until it is reconciled. See billing outcomes.
Can I enable streaming or tools?
Yes, where the selected route advertises the capability. Streaming and strict JSON outputs are available on configured OpenAI routes. Function tools are enabled for compatible Chat Completions models. See streaming and tool calling.
Where is conversation history?
The gateway does not provide stored conversation history. Send the relevant supported text messages with each request and manage any retained history in your own application.
Does one BAA cover every model on the internet?
No. The intended offering covers only the model routes Accountable has reviewed and made eligible under its actual agreements and controls. A new model or feature must pass that process.