Usage

Open Usage in the signed-in GM dashboard to inspect account activity and spend.

Make usage attributable

Create a separate API key for each application and environment. Give every key a descriptive name such as production-api, staging-worker, or local-dev. This makes unexpected activity easier to isolate and lets you revoke one workload without interrupting the others.

Investigate unexpected spend

1. Identify the affected key and time window in the dashboard.
2. Check recent deployments, background jobs, retries, and streaming reconnects.
3. Revoke the key immediately if compromise is possible.
4. Replace it only in the intended workload.
5. Contact hi@saygm.com with timestamps and request IDs, but never include the API key or prompt content.

Application-side telemetry

Record model ID, status, latency, and your own correlation ID. Avoid logging GM keys, authorization headers, or sensitive request content. When retrying, record the attempt number so duplicated work can be distinguished from separate user requests.