Models

List Available Models

curl https://gateway.vibecc.dev/v1/models \
  -H "Authorization: Bearer vcc_your_key_here"

Response:

{
  "object": "list",
  "data": [
    { "id": "gpt-4o", "object": "model", "owned_by": "vibecc" },
    { "id": "gpt-4o-mini", "object": "model", "owned_by": "vibecc" }
  ]
}

Model Aliases

VibeCC uses model aliases that map to one or more backend providers. When you request gpt-4o, VibeCC routes to the best available provider for that capability — no code changes needed if a provider has an outage.

Get Model Details

curl https://gateway.vibecc.dev/v1/models/gpt-4o \
  -H "Authorization: Bearer vcc_your_key_here"

Response:

{
  "id": "gpt-4o",
  "object": "model",
  "owned_by": "vibecc"
}

Service Classes

Behind each alias is a service class — a routing policy that selects the best available binding based on health score, latency, cost, and tenant affinity. You interact only with the alias.