Check an API operation in Activity

Use API Activity to confirm that an API call reached the selected organization without exposing its request or response content. Sign in to the same organization that owns the key, make one bounded call using the first-request guide, and retain its approximate time, endpoint and HTTP request-id. The visible list contains the latest 50 operations; refresh it after the call reaches a terminal state.

This screen records generation operations, not connection checks such as the free GET /v1/models. The current view has no historical pagination, per-key filter or CSV export. Keep a separate record of your public request ID when investigating a specific call; the browser cannot reconstruct that header from an Activity row.

Find a recent operation

Compare the endpoint and time with your call, then inspect the HTTP status or outcome. A completed result confirms that the operation finished; a failed or cancelled result needs its own diagnosis. For a stream, an initial HTTP 200 does not prove completion: a terminal error event still means the operation failed. The Activity row ID identifies a run and differs from the HTTP request-id response header, so do not compare them as equal. Keep the header value separately for support. The list does not display the prompt or response.

If the operation is missing or failed

Check the organization selector first, then refresh and compare a narrow time window around the call. Older operations can fall outside the latest 50; absence from this screen does not prove that a call was free or never executed. If the client never received an HTTP response, keep any public response ID and the Idempotency-Key you supplied, and follow connection troubleshooting before starting another generation. For a visible failure, use its safe status with errors and limits. Never paste the key, prompt or response into a support request.

How to read tokens and the debit

A row shows the model, normalized input and output tokens, server duration, and the final credit debit once the reservation is closed. A blank field means the value is unknown, not zero. An active reserve is not a charge. Do not multiply tokens by a rate to invent a money price: the screen already shows the debit in credits. Credits and current model rates show the available balance and pricing context. See developer-data privacy for what to share during diagnosis.

For a billing question, record the organization, approximate time and public request ID, plus the balance seen before and after if you recorded it. Concurrent requests, subscription allowances and different access classes make a balance difference an unreliable invoice for one row. Use support-safe metadata to describe the discrepancy.