Openrouter Prod Checklist
Overview
This skill provides a comprehensive production readiness checklist covering security, reliability, observability, and cost management for OpenRouter deployments.
Prerequisites
- Working OpenRouter integration in staging/development
- Production infrastructure ready
Instructions
- Security review: Verify API keys are in a secrets manager (not env files on disk), HTTPS is enforced, and no sensitive data leaks into logs
- Reliability setup: Configure fallback models, retry logic with exponential backoff, circuit breakers, and request timeouts for every API call
- Observability: Set up structured logging for every API call (request ID, model, latency, tokens, cost), alerting on error rate spikes, and a monitoring dashboard
- Cost controls: Set account spending limits in the OpenRouter dashboard, implement per-request
max_tokens, and deploy budget enforcement middleware
- Load testing: Run load tests at 2x expected peak traffic to verify rate limits, latency under load, and fallback behavior; document capacity limits
Output
- Production readiness checklist with pass/fail for each category
- Monitoring dashboard with key metrics (latency, error rate, cost, token usage)
- Documented runbooks for common failure scenarios (rate limiting, provider outages, credit exhaustion)
Error Handling
| Error |
Cause |
Fix |
| Production key exposed |
Key logged or committed to source |
Rotate immediately; deploy from secrets manager; add secret scanning |
| No fallback configured |
Primary model goes down in production |
Add at least one fallback model before launch; test failover |
| Missing monitoring |
Errors go undetected |
Set up alerting on 4xx/5xx rates and latency P95 before launch |
See ${CLAUDE_SKILL_DIR}/references/errors.md for full error reference.
Examples
See ${CLAUDE_SKILL_DIR}/references/examples.md for runnable code samples.
Resources
1---2name: openrouter-prod-checklist3description: |4 Validate production readiness of your OpenRouter integration. Use before deploying to production. Trigger with phrases like 'openrouter production', 'openrouter launch checklist', 'production ready', 'openrouter deploy'.5allowed-tools: Read, Write, Edit, Grep6version: 1.0.07license: MIT8author: Jeremy Longshore <jeremy@intentsolutions.io>9compatible-with: claude-code, codex, openclaw10---1112# Openrouter Prod Checklist1314## Overview1516This skill provides a comprehensive production readiness checklist covering security, reliability, observability, and cost management for OpenRouter deployments.1718## Prerequisites1920- Working OpenRouter integration in staging/development21- Production infrastructure ready2223## Instructions24251. **Security review**: Verify API keys are in a secrets manager (not env files on disk), HTTPS is enforced, and no sensitive data leaks into logs262. **Reliability setup**: Configure fallback models, retry logic with exponential backoff, circuit breakers, and request timeouts for every API call273. **Observability**: Set up structured logging for every API call (request ID, model, latency, tokens, cost), alerting on error rate spikes, and a monitoring dashboard284. **Cost controls**: Set account spending limits in the OpenRouter dashboard, implement per-request `max_tokens`, and deploy budget enforcement middleware295. **Load testing**: Run load tests at 2x expected peak traffic to verify rate limits, latency under load, and fallback behavior; document capacity limits3031## Output3233- Production readiness checklist with pass/fail for each category34- Monitoring dashboard with key metrics (latency, error rate, cost, token usage)35- Documented runbooks for common failure scenarios (rate limiting, provider outages, credit exhaustion)3637## Error Handling3839| Error | Cause | Fix |40|-------|-------|-----|41| Production key exposed | Key logged or committed to source | Rotate immediately; deploy from secrets manager; add secret scanning |42| No fallback configured | Primary model goes down in production | Add at least one fallback model before launch; test failover |43| Missing monitoring | Errors go undetected | Set up alerting on 4xx/5xx rates and latency P95 before launch |4445See `${CLAUDE_SKILL_DIR}/references/errors.md` for full error reference.4647## Examples4849See `${CLAUDE_SKILL_DIR}/references/examples.md` for runnable code samples.5051## Resources5253- [OpenRouter Documentation](https://openrouter.ai/docs)54- [OpenRouter Models](https://openrouter.ai/models)55- [OpenRouter API Reference](https://openrouter.ai/docs/api-reference)56- [OpenRouter Status](https://status.openrouter.ai)
micsapp