Model ID

A RouteAPI model ID is the name your application sends in the model field. It is the public contract between your business system and RouteAPI.

Why stable model IDs matter

• When the platform adjusts model availability, application code does not need frequent changes.
• Teams can use a unified set of approved model names.
• Logs, billing, and alerts are easier to read.
• Client configuration across SDKs and tools becomes simpler.

Example

{
  "model": "gpt-4o",
  "messages": [
    { "role": "user", "content": "Summarize this document." }
  ]
}

The value of model should match a model ID currently available to the account in the RouteAPI console.

Best practices

• Use model IDs from the console, and do not hardcode temporary names in production.
• Reserve different model IDs for different quality, latency, or cost expectations.
• Validate model behavior before using it in production flows.
• After changing the model ID for a high-traffic application, review usage logs to confirm the result.