Provider Integration

For Providers

If you’d like to be a model provider and sell inference on OpenRouter, fill out our form to get started.

To be eligible to provide inference on OpenRouter you must have the following:

1. List Models Endpoint

You must implement an endpoint that returns all models that should be served by OpenRouter. At this endpoint, please return a list of all available models on your platform. Below is an example of the response format:

1
{
2
  "data": [
3
    {
4
      // Required
5
      "id": "anthropic/claude-sonnet-4",
6
      "hugging_face_id": "", // required if the model is on Hugging Face
7
      "name": "Anthropic: Claude Sonnet 4",
8
      "created": 1690502400,
9
      "input_modalities": ["text", "image", "file"],
10
      "output_modalities": ["text", "image", "file"],
11
      "quantization": "fp8",
12
      "context_length": 1000000,
13
      "max_output_length": 128000,
14
      "pricing": {
15
        "prompt": "0.000008", // pricing per 1 token
16
        "completion": "0.000024", // pricing per 1 token
17
        "image": "0", // pricing per 1 image
18
        "request": "0", // pricing per 1 request
19
        "input_cache_read": "0", // pricing per 1 token
20
        "input_cache_write": "0" // pricing per 1 token
21
      },
22
      "supported_sampling_parameters": ["temperature", "stop"],
23
      "supported_features": [
24
        "tools",
25
        "json_mode",
26
        "structured_outputs",
27
        "web_search",
28
        "reasoning"
29
      ],
30
      // Optional
31
      "description": "Anthropic's flagship model...",
32
      "openrouter": {
33
        "slug": "anthropic/claude-sonnet-4"
34
      },
35
      "datacenters": [
36
        {
37
          "country_code": "US" // `Iso3166Alpha2Code`
38
        }
39
      ]
40
    }
41
  ]
42
}

NOTE: pricing fields are in string format to avoid floating point precision issues, and must be in USD.

Valid quantization values are: int4, int8, fp4, fp6, fp8, fp16, bf16, fp32.

Valid sampling parameters are: temperature, top_p, top_k, repetition_penalty, frequency_penalty, presence_penalty, stop, seed.

Valid features are: tools, json_mode, structured_outputs, web_search, reasoning.

Tiered Pricing

For models with different pricing based on context length (e.g., long context pricing), you can provide pricing as an array of tiers instead of a single object:

1
{
2
  "pricing": [
3
    {
4
      "prompt": "0.000002", // base tier pricing per 1 token
5
      "completion": "0.000012", // base tier pricing per 1 token
6
      "image": "0.01", // pricing per 1 image (base tier only)
7
      "request": "0", // pricing per 1 request (base tier only)
8
      "input_cache_read": "0.000001", // base tier pricing per 1 token
9
      "input_cache_write": "0.000006" // base tier pricing per 1 token
10
    },
11
    {
12
      "prompt": "0.000004", // long context tier pricing per 1 token
13
      "completion": "0.000018", // long context tier pricing per 1 token
14
      "input_cache_read": "0.000002", // long context tier pricing per 1 token
15
      "input_cache_write": "0.000009", // long context tier pricing per 1 token
16
      "min_context": 200000 // minimum input tokens for this tier to apply
17
    }
18
  ]
19
}

When using tiered pricing, the first tier (index 0) is the base pricing that applies when input tokens are below the min_context threshold. The second tier applies when input tokens meet or exceed the min_context value.

Limitations:

• Currently, OpenRouter supports up to 2 pricing tiers.
• The image and request fields are only supported in the base tier (index 0) and will be ignored if included in other tiers.

2. Auto Top Up or Invoicing

For OpenRouter to use the provider we must be able to pay for inference automatically. This can be done via auto top up or invoicing.

3. Uptime Monitoring & Traffic Routing

OpenRouter automatically monitors provider reliability and adjusts traffic routing based on uptime metrics. Your endpoint’s uptime is calculated as: successful requests ÷ total requests (excluding user errors).

Errors that affect your uptime:

• Authentication issues (401)
• Payment failures (402)
• Model not found (404)
• All server errors (500+)
• Mid-stream errors
• Successful requests with error finish reasons

Errors that DON’T affect uptime:

• Bad requests (400) - user input errors
• Oversized payloads (413) - user input errors
• Rate limiting (429) - tracked separately
• Geographic restrictions (403) - tracked separately

Traffic routing thresholds:

• Minimum data: 100+ requests required before uptime calculation begins
• Normal routing: 95%+ uptime
• Degraded status: 80-94% uptime → receives lower priority
• Down status: <80% uptime → only used as fallback

This system ensures traffic automatically flows to the most reliable providers while giving temporary issues time to resolve.

4. Performance Metrics

OpenRouter publicly tracks TTFT (time to first token) and throughput (tokens/second) for all providers on each model page.

Throughput is calculated as: output tokens ÷ generation time, where generation time includes fetch latency (time from request to first server response), TTFT, and streaming time. This means any queueing on your end will show up in your throughput metrics.

To keep your metrics competitive:

• Return early 429s if under load, rather than queueing requests
• Stream tokens as soon as they’re available
• If processing takes time (e.g. reasoning models), send SSE comments as keep-alives so we know you’re still working on the request. Otherwise we may cancel with a fetch timeout and fallback to another provider