openrouter-account

Verify, rotate, and diagnose OpenRouter API credentials across environments.

3|1|Updated Feb 21, 2026
One-click install
npx skills add https://github.com/kitaekatt/plugins-kit --skill openrouter-account
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openrouter-account
Source: https://github.com/kitaekatt/plugins-kit/tree/main/plugins/llm-scripting-kit/skills/openrouter-account
Command: npx skills add https://github.com/kitaekatt/plugins-kit --skill openrouter-account

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill resolves authentication friction by providing a centralized, secure way to manage OpenRouter API credentials, ensuring that plugins and scripts have valid access without manual configuration errors.

Core Features & Use Cases

  • Credential Lifecycle Management: Easily set, rotate, or verify your OpenRouter API key across different project environments.
  • Automated Diagnostics: Automatically identify and resolve HTTP 401 (unauthorized) or 402 (insufficient balance) errors during API calls.
  • Use Case: When a plugin fails to connect to an LLM, use this skill to check if your key is valid or if your account simply needs a balance top-up.

Quick Start

Run the openrouter-account status command to verify your current API key configuration and account status.

Frequently Asked Questions about openrouter-account

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify my OpenRouter API key is valid before running scripts?

To verify your OpenRouter API key, run the openrouter-account status command. This performs a preflight credential check against the OpenRouter auth endpoints to confirm your key is active and properly configured.

Why does my OpenRouter API call return a 401 or 402 error?

OpenRouter API 401 errors mean your API key is unauthorized, while 402 errors indicate insufficient account balance. This skill diagnoses these HTTP errors automatically to determine if you need key rotation or a billing top-up.

Can I manage OpenRouter credentials across different project environments?

Yes, you can manage OpenRouter credentials across different project environments. The skill provides environment-specific key resolution by reading user-scoped .env files to apply the correct API key for each context.

What's the best way to rotate OpenRouter API keys for dependent plugins?

Rotating OpenRouter API keys for dependent plugins is managed centrally through this skill. It handles credential lifecycle management by updating the shared key in your .env file, ensuring all dependent scripts maintain valid access.

Do I need a specific framework to resolve OpenRouter authentication issues?

No framework is needed to resolve OpenRouter authentication issues. The skill requires only standard library access to read user-scoped .env files and perform network validation directly against OpenRouter auth endpoints.

When should I use centralized OpenRouter credential management instead of manual configuration?

Use centralized OpenRouter credential management when multiple scripts or plugins require API access. It resolves authentication friction by preventing manual configuration errors and ensuring automated diagnostics for billing or key failures.