per-provider model details overview

[harmw]

Working on a quick PR to list models per providers, in addition to the general /v2/providers json blob:

λ curl -s 'localhost:8080/v2/providers/avian?pretty=true&sort=context' | glow --width 150

   Provider: Avian

   Field                                                                  │ Value
  ────────────────────────────────────────────────────────────────────────┼───────────────────────────────────────────────────────────────────────
   ID                                                                     │  avian
   Type                                                                   │  openai-compat
   API Endpoint                                                           │  https://api.avian.io/v1
   Default Large Model ID                                                 │  moonshotai/kimi-k2.5
   Default Small Model ID                                                 │  deepseek/deepseek-v3.2

  ## Models

   Model ID                   │ Name                       │ Context Window             │ Input Cost ($/M)           │ Output Cost ($/M)
  ────────────────────────────┼────────────────────────────┼────────────────────────────┼────────────────────────────┼────────────────────────────
    moonshotai/kimi-k2.5      │ Kimi K2.5                  │ 262144                     │ 0.450000                   │ 2.200000
    z-ai/glm-5                │ GLM-5                      │ 204800                     │ 0.950000                   │ 2.550000
    minimax/minimax-m2.5      │ MiniMax M2.5               │ 196608                     │ 0.270000                   │ 1.080000
    deepseek/deepseek-v3.2    │ DeepSeek V3.2              │ 163840                     │ 0.230000                   │ 0.330000

The /v2/providers endpoint remains, obviously, but the change introduces /v2/providers/foobar to limit returning just json for that provider. And there's a pretty parameter to have it return a markdown table for when you're just interested in available models/context/pricing bits.

Alternative approach is embedding as another CLI part, but I figured that might be just too much. IMHO this is good enough 😅

[andreynering]

Hi @harmw,

An endpoint to see a single providers sounds reasonable, and easy to implement.

Regarding markdown, I'm not so sure. I guess we can add if the code is straightforward enough. I would suggest you to submit separate PRs for each feature (provider endpoint + markdown support).

If we decide to add markdown, I'd vote to check one of these instead of ?pretty=true:

• Accept: text/markdown header
• .md suffix in the URL

[harmw]

hm, that's not bad at all 🤔 having .md to decide on output

meanwhile: #231

markdown: #232