Provider Console | OpenModels Documentation

Use the Provider Console to manage an approved provider workspace in OpenModels: review status, connect a models list API, publish routes, update pricing, submit snapshots, monitor usage, review payouts, and maintain provider settings.

Open the Provider Console:

https://openmodels.market/provider-console

Console checklist

Use the left navigation to move through the provider workflow.

Review workspace status in Overview.
Configure and test the Models API endpoint.
Publish and maintain model routes in Routes.
Monitor requests and revenue in Usage.
Review balances and payout history in Payouts.
Keep provider profile and API connection details current in Settings.

Overview

Open Overview to check the selected provider application, status, live route count, request volume, token volume, estimated earnings, and setup guide.

Provider Console overview with routes, live routes, request volume, tokens served, earnings, and setup guide

Key areas:

Area	Purpose
Provider status	Shows whether the selected provider workspace is pending, live, suspended, or needs attention.
Routes / live routes	Shows total route count and the number currently available to users.
Requests 24h	Shows recent request volume.
Tokens served	Shows input and output token volume.
Estimated earnings	Shows current-month estimated earnings.
Setup guide	Tracks profile, API endpoint, route publishing, and monitoring readiness.

Use Review, Open routes, or View health from the setup guide when a step needs attention.

Models API

Open Models API to connect the endpoint that returns your provider model list. This page is the source for syncing model metadata and pricing into OpenModels.

Provider Console Models API page with models URL, test connection, fetch models, and sync status

Workflow:

Enter the Models URL.
Click Test connection to confirm OpenModels can reach and parse the endpoint.
Click Fetch models after the connection is verified.
Check Sync status, Last sync, and Models found.

The endpoint should return JSON with a data array.

{
  "data": [
    {
      "id": "provider/model-name",
      "name": "Model Name",
      "input_modalities": ["text"],
      "output_modalities": ["text"],
      "context_length": 128000,
      "max_output_length": 8192,
      "currency": "USD",
      "pricing": [
        {
          "label": "standard",
          "prompt": "0.000001",
          "completion": "0.000003"
        }
      ],
      "supported_features": ["chat", "streaming"],
      "is_ready": true
    }
  ]
}

Important fields:

Field	Description
`data`	Model array returned by the endpoint.
`id`	Stable model ID used by routes.
`name`	Readable model name.
`input_modalities`, `output_modalities`	Supported modalities such as text, image, audio, or video.
`currency`	Optional; `USD` or `CNY`. Empty values default to `CNY`.
`pricing`	Price rows. Multiple rows are supported.
`label`, `inputMode`	Optional labels for modes such as text-to-image or image-to-image.
`resolution`	Optional image or video resolution constraint.
`prompt`, `completion`	Token prices in decimal units.
`image`, `request`, `duration`	Unit prices for non-token models.
`range_start`, `range_end`	Optional tier range. Use `null` for an open-ended range.
`is_ready`	`true` means the route can be routable after sync.

Routes

Open Routes to review published model routes, route status, pricing, context, supply type, and snapshot state.

Provider Console routes table with model IDs, pricing, route status, and actions

The routes table shows:

Column	Description
Model ID	Public model identifier.
Input	Input token or unit price.
Output	Output token price, when applicable.
Cache	Cache read/write pricing, when applicable.
Context	Context window, when available.
Supply	Supply type shown for the route.
Status	`Live` or `Draft`.
Action	Publish, pause, or edit route actions.

Use Add model to create a new route manually. Select an existing model row to open the route editor.

Route editor

The route editor is a step-by-step drawer used to edit model metadata and submit a new snapshot.

Provider route editor model basics step with model ID, display name, description, and provider logo URL

Editor steps:

Step	Purpose
Model basics	Set model ID, display name, description, and provider logo URL. Existing model IDs are locked to protect live route identity.
Capabilities	Set input/output modalities, supported features, context length, and max output.
Pricing	Add token, request, image, or duration pricing rows.
Preview	Review the route payload before submitting.

Click Submit snapshot after the route payload is ready. A valid snapshot updates the model and pricing data used by the Provider Console and marketplace routes.

Pricing

Use the Pricing step in the route editor to configure price rows.

Provider route editor pricing step with pricing rows and submit snapshot action

Supported pricing types:

Pricing type	Fields
Token pricing	`prompt`, `completion`, `input_cache_read`, `input_cache_write`
Request pricing	`request`
Image pricing	`image`, optional `resolution` and `inputMode`
Duration pricing	`duration`
Tiered pricing	Optional `range_start` and `range_end`

Review the rendered route table after submitting a snapshot so the displayed prices match the intended billing unit.

Publish or pause routes

Use the action button in Routes to change route availability.

Action	Effect
Publish	Marks a draft route as available when the route is ready.
Pause	Temporarily removes a live route from serving traffic.
Submit snapshot	Saves route metadata and pricing updates.

Keep a route live only when the upstream provider can serve traffic reliably. Pause a route before planned downtime, pricing corrections, capacity issues, or upstream degradation.

Usage

Open Usage to review request and revenue summaries for the selected provider application.

Provider Console Usage page with request count, token volume, revenue, and provider usage table

Usage data includes:

Field	Description
Requests	Number of routed requests in the selected window.
Tokens	Input and output token volume.
Revenue	Revenue for the selected window.
Period	Reporting period, such as 30 days.
Provider	Provider workspace for the usage row.
Errors	Error signal for the reporting period.

Use this page to confirm whether OpenModels is routing traffic to the expected provider application and whether revenue is being recorded.

Payouts

Open Payouts to review confirmed provider balance, payout method, current-month estimates, and payout history.

Key areas:

Area	Description
Available balance	Confirmed balance available for payout.
Paid out	Historical payout total.
Estimated earnings this month	Live estimate based on current-month usage.
Requests this month	Request count used for the current estimate.
Payout method	Configured payout channel, if available.
Contact	Contact channels such as Telegram or WeChat.
Payout history	Ledger entries for balance changes and payouts.

Confirmed monthly bills and settlements update the available balance. Live estimates do not directly change the confirmed payout balance.

Settings

Open Settings to maintain the provider profile and API connection details tied to the signed-in account.

Settings include:

Section	Fields
Basic info	Provider name, legal name, website, provider logo URL, provider type, status.
Contact	Contact email, Telegram, WhatsApp.
Infrastructure	Inference region and related provider metadata.
API connection	API base URL, auth type, provider API key, upstream key activation.
Review notes	Provider description and authorization details.

Use Save changes after editing profile details. If a provider API key is already active, leave the key field blank unless you intentionally want to rotate it.

Provider Console FAQ

What should I configure first?

Start with Settings if the provider profile or API connection is incomplete. Then use Models API to test and sync the model list, and Routes to review and publish routes.

When should I use Models API instead of Add model?

Use Models API when your provider can generate a structured model list automatically. Use Add model when you need to create or edit a small number of routes manually.

What does Submit snapshot do?

It saves the current model route payload, including metadata, capabilities, pricing, and readiness. The latest valid snapshot becomes the source for route publishing.

What is the difference between Draft and Live?

Draft routes are saved but not serving traffic. Live routes are available for OpenModels routing, assuming the provider application is active.

When should I pause a route?

Pause a route when upstream capacity, pricing, latency, or availability is not production-ready. Publish it again after the route is stable.

Where do I check provider revenue?

Use Usage for request and revenue summaries. Use Payouts for confirmed balance, payout method, estimates, and payout history.