Catalog
BerriAI/update-key

BerriAI

update-key

Update an existing API key on a live LiteLLM proxy. Ask for the key and what to change (budget, models, expiry), then call POST /key/update.

v1.0LATEST
NewUpdated Oct 12, 2026

Update Key

Update an existing API key on a live LiteLLM proxy.

Setup

LITELLM_BASE_URL  — e.g. https://my-proxy.example.com
LITELLM_API_KEY   — proxy admin key

API reference: https://litellm.vercel.app/docs/proxy/virtual_keys

Ask the user

  1. Key (required) — the sk-... value. If they don't have it, list keys:
    curl -s "$BASE/key/list?size=25&return_full_object=true" -H "Authorization: Bearer $KEY"
    
  2. What to change — any combination of:
    • max_budget (float)
    • models (list)
    • key_alias (string)
    • tpm_limit / rpm_limit (int)
    • duration (e.g. 30d — extends expiry from now)
    • team_id / user_id (reassign ownership)

Run

curl -s -X POST "$BASE/key/update" \
  -H "Authorization: Bearer $KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "key": "<sk-...>",
    "max_budget": <value>,
    "models": [<models>],
    "duration": "<duration>"
  }'

Only include the fields being changed.

Output

Show the updated key_alias, max_budget, models, expires.

Files1
1 files · 1.0 KB

Select a file to preview

Overall Score

68/100

Grade

C

Adequate

Grades are signals, not a certification. Always review a skill yourself before use.

Safety

72

Quality

62

Clarity

74

Completeness

58

Summary

Updates an existing API key on a live LiteLLM proxy by accepting user-specified changes (budget, models, expiry, TPM/RPM limits) and submitting them via a POST request to the proxy's /key/update endpoint. The skill requires a proxy base URL and admin key for authentication.

Detected Capabilities

curl executionhttp request (POST)environment variable readbearer token authenticationjson payload construction

Trigger Keywords

Phrases that agents use to match this skill to user intent.

update api keychange key budgetextend key expirymanage proxy keyslitellm key updateapi key rate limitrotate api key

Risk Signals

WARNING

Environment variable read for LITELLM_API_KEY (proxy admin credential)

Setup section, curl commands
WARNING

No input validation documented for user-provided parameters (budget, models, duration)

Ask the user section
INFO

No error handling guidance for failed API requests

Run section
WARNING

Bearer token transmitted in HTTP header without explicit HTTPS requirement

curl command

Referenced Domains

External domains referenced in skill content, detected by static analysis.

litellm.vercel.appmy-proxy.example.com

Use Cases

  • Adjust API key spending limits in production
  • Rotate or extend API key expiration
  • Reassign API keys between teams or users
  • Restrict API key model access
  • Update API key rate limits (TPM/RPM)

Quality Notes

  • Strength: Clear setup requirements with specific environment variable names
  • Strength: API reference link provided for additional context
  • Strength: Well-structured optional parameter list with examples
  • Weakness: No guidance on validating key format or parameter ranges before submission
  • Weakness: Missing error handling patterns (e.g., 401 auth failure, 404 key not found, malformed JSON)
  • Weakness: No warning about production impact — updating live keys affects running API clients
  • Weakness: Duration format (e.g., '30d') lacks explanation of valid syntax and behavior
  • Weakness: Output section only describes fields to show, not how to interpret the response or confirm success
  • Weakness: No mention of required HTTPS or cert verification for production proxy
Model: claude-haiku-4-5-20251001Analyzed: Oct 12, 2026

Reviews

Add this skill to your library to leave a review.

No reviews yet

Be the first to share your experience.

Use BerriAI/update-key in your dev environment

Command Palette

Search for a command to run...