Models and availability

Models, providers, routes, endpoint capabilities, and pricing can change over time. Aikey365 documentation intentionally avoids a permanent static model catalog.

Fetch current models

Use the console and pricing page, or:

curl https://aikey365.com/v1/models \
  -H "Authorization: Bearer $AIKEY365_API_KEY"

Why an existing model may fail on one endpoint

Availability depends on multiple layers:

• model capabilities
• upstream channel capabilities
• API key restrictions
• group and routing candidates
• current upstream health

A model name existing does not imply support for every endpoint.

Keep model IDs configurable

export AIKEY365_MODEL="YOUR_MODEL_ID"

Production evaluation

Choose models by workload: latency, context, reasoning, coding, vision, media generation, embeddings, or reranking.

Validate quality, latency, cost, and endpoint compatibility with representative workloads before production.

Pricing

The pricing experience can expose filters such as provider, group, and endpoint type. Final billing can still vary with model, input/output type, caching, route, and current platform configuration.