Agent skill · data analytics · jeremylongshore

openrouter-model-availability

Monitor OpenRouter model availability and implement health checks. Use

Why this skill is useful

Adds executable health check scripts and monitoring procedures for OpenRouter model availability that are not publicly documented.

What it needs

Requires curl, jq, python3 installed locally. Requires openrouter account access. About 4k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.

What this skill does

OpenRouter Model Availability Overview OpenRouter's /api/v1/models endpoint is the source of truth for model availability. Models can be temporarily unavailable, have degraded performance, or be permanently removed. This skill covers querying model status, building health probes, tracking availability over time, and automating failover. Prerequisites An OpenRouter API key exported as OPENROUTERAPIKEY for live probes (the catalog query itself needs no auth) — see the openrouter-install-auth skill for setup curl and jq for the catalog status queries and the cron monitoring script Python 3.8+ with the OpenAI SDK and requests (pip install openai requests) for the health-check service A small credit balance — each maxtokens: 1 probe costs roughly $0.0001 Instructions 1. Confirm your models exist in the catalog with curl -s https://openrouter.ai/api/v1/models jq ... per Query Model Status — pull contextlength and per-million pricing without spending any tokens. 2. For a zero-cost existence check inside code, use checkmodelexists() from Catalog-Based Availability Check; on a miss it calls findsimilar() to suggest same-provider replacements. 3. Probe live health with probemodel() from Health Check Service — a maxtokens: 1 request that returns a HealthStatus with available, latencyms, and checkedat. 4. Sweep your critical set with checkcriticalmodels(), which logs OK/FAIL plus latency per model. 5. Automate via the Availability Monitoring Script as a /5 cron job appending timestamped status lines to /var/log/openrouter-health.log. 6. Tune alerting per Error Handling — require 2-3 consecutive failures before marking a model down to avoid false positives. …

How to use it

Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:

@skills jeremylongshore/openrouter-model-availability--462870

View the source on GitHub

Browse the @skills marketplace