Prompts and completions are not stored
A call leaves behind a request record, and that record holds metadata only:
Writing a prompt, a completion, or an API key in plaintext to a log is prohibited in
this codebase and enforced by a linter, not left to reviewer attention. That is the
mechanism behind the right-hand column.
The consequence worth planning around: we cannot show you the text of an old call,
because we do not have it. If you need prompt-level history, keep it on your side. What
we can reconstruct from a request id is the route, the timing, the tokens and the
outcome.
API keys
Created in the console, shown once, stored as a hash plus the first eight characters for display. There is no screen and no support process that can recover one — losing a key means revoking it and creating another. Revocation takes effect for new requests within seconds. Requests already accepted are not cancelled by it, so treat anything already in flight as served.Media you send
An image is fetched and normalised so the model can read it. Where a model cannot accept it, the request is rejected before the fetch — a mistaken request does not cause a transfer or a write.What this page does not claim
Being useful here means being clear about the edges:- It says nothing about upstream retention. Your request is served by compute we route to, and what any given provider retains is governed by our agreement with them, not by this page. If your use has a retention requirement, raise it with us and we will answer for your account and your models specifically rather than in general.
- It states no retention period for the request records above.
- It is not a compliance statement. Contractual data-protection terms are handled
through your organization’s agreement — which is also what
AGREEMENT_REQUIREDis asking for when it appears.
Next
Authentication
How keys are issued, scoped and revoked.
Routing and providers
What the response says about who served the call.