Docs Classements ↗
🌐 Français
EN简体中文繁體中文EspañolFrançais日本語한국어العربيةPortuguês
Contribuez vos données

L'Open Router Standard

TKX flips the usual integration burden: instead of us writing an adapter per marketplace, you expose public pricing and we ingest you automatically. Any router, aggregator, inference provider or model lab whose /v1/models carries pricing is normalized, sanity-checked and ranked within the hour.

✓
Déjà en direct via le standard : novita.ai et Requesty — intégrés sans aucun code sur mesure.

Dialectes de tarification pris en charge

Expose per-model pricing in any one of these shapes; TKX normalizes all four to USD per 1M tokens:

// A — style OpenRouter : $/token en chaînes de caractères
"pricing": { "prompt": "0.0000006", "completion": "0.0000024" }

// B — style Requesty : $/token en nombres
"input_price": 0.0000006, "output_price": 0.0000024

// C — style Novita : dix-millièmes de $ par 1 M (÷10000)
"input_token_price_per_m": 6000, "output_token_price_per_m": 24000

// D — one-api / new-api style: /api/pricing ratio system (base $2/1M; quota_type=1 rows are skipped)
"model_name": "gpt-5.5", "model_ratio": 2.5, "completion_ratio": 4, "quota_type": 0

Comment nous protégeons les données

Les prix ingérés passent trois vannes de contrôle avant de pouvoir apparaître : une vérification de plage plausible par ligne, une vérification d'échantillon minimum par source (≥3 modèles tarifés) et une vérification d'écart par source par rapport aux grilles tarifaires officielles (une source dont la marge médiane est extravagante est écartée entièrement). Les mauvaises unités ne polluent jamais les tableaux.

Usage reporting (optional) — light up your Volume column

The Routers board ranks by 24h traded token volume first. OpenRouter's volume comes from its public rankings; every other marketplace can report its own by exposing one public JSON endpoint (any https URL). We pull it hourly — you never push numbers to us, and anyone can curl your endpoint to audit what we show.

// GET https://your-domain/tkx-usage.json — yesterday's completed UTC day
{
  "date": "2026-07-20",                    // UTC calendar day (YYYY-MM-DD), the last completed day
  "total_tokens_24h": 123456789012,     // prompt + completion tokens, whole platform
  "models": [                              // optional but recommended
    { "model_name": "gpt-5.5", "tokens_24h": 12345678 }
  ],
  "requests_24h": 98765,                 // optional
  "spend_usd_24h": 1234.56                // optional
}

Self-reported volume appears with an explicit self badge — never mixed with measured data, never added to OpenRouter's numbers, and never counted into TKX indices. Reports pass validation valves (shape, plausibility caps, freshness ≤3 days, per-model breakdown consistency); a report that fails any valve is dropped whole for that cycle. Self-reported ≠ endorsed: we display and label, readers judge.

i
Register the usage URL together with your /v1/models on the registration form, or ask us to attach it to an existing listing. It lights up within one collection cycle.

Faites-vous référencer

← Précédent
Introduction