openrouter-debug-bundle

# OpenRouter Debug Bundle ## Current State !`node --version 2>/dev/null || echo 'N/A'` !`python3 --version 2>/dev/null || echo 'N/A'` ## Overview When an OpenRouter request fails or returns unexpected results, you need a structured debug bundle: the exact request, response, headers, generation metadata, and environment info. The generation ID (`gen-*` prefix in `response.id`) is the key correlator -- it lets you look up exact cost, provider used, and latency via `GET /api/v1/generation?id=`. ## Quick Debug: curl ```bash # Send a request and capture full response with headers curl -v https://openrouter.ai/api/v1/chat/completions \ -H "Authorization: Bearer $OPENROUTER_API_KEY" \ -H "Content-Type: application/json" \ -H "HTTP-Referer: https://my-app.com" \ -H "X-Title: debug-test" \ -d '{ "model": "openai/gpt-4o-mini", "messages": [{"role": "user", "content": "Say hello"}], "max_tokens": 50 }' 2>&1 | tee /tmp/openrouter-debug.txt # Extract generation ID from response GEN_ID=$(jq -r '.id' /tmp/openrouter-debug.txt 2>/dev/null) echo "Generation ID: $GEN_ID" # Look up generation metadata (exact cost, provider, latency) curl -s "https://openrouter.ai/api/v1/generation?id=$GEN_ID" \ -H "Authorization: Bearer $OPENROUTER_API_KEY" | jq '.data | { model: .model, total_cost: .total_cost, tokens_prompt: .tokens_prompt, tokens_completion: .tokens_completion, generation_time: .generation_time, provider: .provider_name }' ``` ## Py...