Feature

Secure API keys

Hashed keys, per-key limits and model permissions. Revoke any key instantly.

API keys are never stored in plain text — only hashes. Set spending limits per key, choose exactly which models each key can use, and block or delete a key from the dashboard to stop it instantly. Two-factor sign-in protects the account itself, so a leaked password is not a leaked wallet.

Storage
Hashed
Limits
Per key
Account
Two-factor sign-in

What you get

  • Keys shown once at creation, hashed at rest
  • Allow or block individual models per key
  • Per-key spending limits
  • Block, unblock or delete keys anytime
  • Two-factor authentication on the account

Common use cases

Production appsClient projectsCI pipelinesTeam access control

How it works

  1. 1
    Create a key
    Generate a key from the dashboard — it is shown once and stored hashed.
  2. 2
    Scope it
    Set a spending limit and choose which models the key may call.
  3. 3
    Deploy it
    Use the key in your app, agent or CI pipeline.
  4. 4
    Revoke anytime
    Block or delete the key from the dashboard and it stops working immediately.

Frequently asked questions

Can I see my key again later?

No. Keys are shown once at creation and only their hash is stored — create a new key if one is lost.

Can a key be limited to one model?

Yes. Each key can allow or block individual models and carry its own spending limit.

How fast does revocation take effect?

Immediately. A blocked or deleted key stops working right away.

Related features

Transparent billing

Every request shows tokens, cost, latency and model — at market price.

One wallet for every model

Top up via Razorpay — UPI, cards and netbanking. One balance for the whole catalog.

OpenAI-compatible API

Keep the OpenAI SDK. Swap the base URL and key. Ship in minutes.