Consider native Anthropic API instead of OpenRouter

t-298.7·WorkTask·
·
·
·Omni/Ide.hs
Parent:t-298·Created1 month ago·Updated1 month ago

Description

Edit

Currently using OpenRouter with explicit --api-key because pi CLI OAuth doesn't work headless. Options: 1. Keep using OpenRouter (works, but extra hop) 2. Copy Ben's ~/.pi/agent/auth.json to Ava (tokens expire) 3. Use ANTHROPIC_API_KEY directly with --provider anthropic 4. Create a service account with Anthropic

Evaluate cost, latency, and reliability tradeoffs.

Timeline (3)

💬[human]1 month ago

Decision: Keep using OpenRouter for now. Reasons: 1. OpenRouter works with explicit --api-key (no OAuth) 2. Provides model flexibility (can switch models easily) 3. Cost tracking built-in 4. No token expiration issues 5. Works reliably in production

Native Anthropic would require either copying auth tokens (expire) or using ANTHROPIC_API_KEY directly. OpenRouter is a reasonable abstraction layer. Closing as won't-fix.

🔄[human]Open → Done1 month ago