Usage and logs

Use aggregate usage for trends and request logs for individual API request investigation.

Usage and Logs answer different operational questions. Both respect project access and the effective data policy shown in Data Controls.

Usage

Usage aggregates requests and estimated cost by time bucket. Group results by the authorized project, key, model, or operation. Filter them by project, key, model, operation, environment, or status. Test-environment traffic can appear in Usage but is not counted as spend.

Estimated usage cost is not an invoice. When policy withholds request metadata, the visible aggregate may be incomplete; billing records remain the record of spend.

Logs

When Logs is available for your organization, it provides request-level metadata for recent API traffic. Use the request id, status, error code, project, key, endpoint, environment, or model to investigate failures and confirm which integration sent a request.

Log availability and detail depend on your organization’s effective data policy and retention window. Request and response payloads, prompts, uploads, and generated artifacts are not captured alongside request metadata. A request-detail window describes supported access, not proof that data was physically deleted at its boundary.

Review Data controls to understand what can appear in these surfaces, and Billing and limits when a request is capacity-constrained.