API keys

Create a key

Open API Keys in the dashboard, give the key a name (up to 60 characters) and create it. Your account must be verified with Telegram first. Otherwise creation is refused with 403 permission_denied.

What the list shows

Each key shows its name, a masked prefix, its status, when it was created, and when it was last used. Request logs use that same masked prefix next to the name — the secret is never displayed again after you create the key.

Key format

New API keys begin with the sk- prefix followed by 43 cryptographically random characters (≥ 256 bits of entropy). Legacy keys with the fm_ prefix remain fully functional and supported for existing integrations.

Rotate or delete a key

You can rotate an existing key directly from the dashboard: this generates a new sk- secret and lets you optionally revoke the old key immediately or keep it active during a transition grace period. Deleting a key removes it immediately, and requests using it return 401 invalid_api_key. Historical usage records are kept, and each one still shows the key's name and masked prefix captured when that request was metered — deleting a key never rewrites its history.

Usage

Spend is per account, not per key. Review requests, tokens and models in the dashboard under Usage and Request logs, or call GET /v1/usage. Each logged request also records the latency the gateway measured (and, for streams, the time to the first byte) next to the key that issued it, shown as name plus masked prefix.