Api Usage Examine

If you're subscribed

Once you’ve subscribed, you can easily monitor your account’s overall token usage directly from the dashboard.

You can also view detailed analytics for each individual API key — including usage statistics, quota management, and expiration settings — all in one place.

Custom model mappings

In Dashboard → API Keys, create or edit a key and add a Model mapping row. The client model is the name your application sends; the upstream model is the actual model to call. For example, map cloud-opus-5-5 to claude-opus-5-5, then send "model": "cloud-opus-5-5" with that key.

Mappings belong to that key, are case-sensitive exact matches, and apply only once (no chains). The target still follows the key's channel restrictions and normal pricing. JSON and streaming responses restore the requested alias in the protocol's model fields, including Gemini's modelVersion; message text, tool arguments and billing records keep their original values. Native Gemini requests use the alias in models/<alias>:generateContent or :streamGenerateContent.

Each key supports up to 64 mappings, with model names up to 200 characters and no whitespace. Remove a row to delete a mapping; remove all rows and save to disable mappings. Requests that do not match a configured alias retain the existing behavior. Activity keys remain read-only.

If you get shared api-key from other people

If you’re using an API key shared by someone else, you can still track its usage in the Usage section, accessible from the top navigation bar.