flu·ere
Sign inStart free

Documents

Model mapping and pricing

Separate client model IDs, platform models, native models, and price versions.

Fluere separates client-facing model IDs, platform model catalog entries, and provider-native model IDs. This keeps API contracts stable while source evaluation, pricing, and routing remain source-specific.

Three model names

  1. Client Model ID: the model string sent by API consumers and tools.
  2. Platform Model: Fluere's canonical catalog entry for pricing, routing, and display.
  3. Provider Native Model: the actual upstream model name found through discovery and mapping.

Pricing rules

  1. Staff maintains platform benchmark prices in CRD per one million tokens.
  2. Acquisition and sell prices are derived from benchmark price, discounts, and source-level pricing policy.
  3. A signed model without benchmark price is unavailable and does not route.
  4. OpenRouter is one model intelligence source; Fluere can sync it daily, then Staff decides whether to promote entries into Platform Models.