venice-api-keys
Installation
SKILL.md
Venice API Keys
Admin endpoints for managing Bearer API keys. Management routes need an ADMIN key. For wallet-only auth, use venice-auth / venice-x402 instead.
| Endpoint | Key type | Purpose |
|---|---|---|
GET /api_keys |
ADMIN | List your active keys (masked). |
POST /api_keys |
ADMIN | Create a key. Response contains the only copy of the secret. |
PATCH /api_keys |
ADMIN | Update description, expiresAt, consumptionLimit, limitPeriod, modelPrivacy. |
DELETE /api_keys?id=... |
ADMIN | Revoke a key. |
GET /api_keys/{id} |
ADMIN | Full details for one key (usage, limits, expiration). |
GET /api_keys/rate_limits |
any | Balances + per-model rate limits for the calling key. |
GET /api_keys/rate_limits/log |
ADMIN | Last 50 rate-limit breaches on the account. |
GET /api_keys/generate_web3_key |
none | Get a short-lived token to sign with a wallet. |
POST /api_keys/generate_web3_key |
none | Prove a wallet holds staked VVV and mint an API key. |
Limits: key creation (POST /api_keys) is capped at 20 requests/minute per user and 500 active keys per user (expired keys don't count).
A request with no Authorization header gets a 402 x402 auth challenge rather than 401; a bad key gets 401.