Chapter 157 min read

Create a provider

Create a provider in Provider Management, complete basic settings such as the top-up ratio on its details page, and then add endpoints and provider keys to it and add them to provider groups.

A provider represents an upstream service or upstream account, for example your Anthropic account or a relay service. To create a provider, you only need to enter a name. After you create it, you add the request URLs and request formats to its endpoints, and the upstream API keys to its provider keys.

Before you begin#

Organization admins, organization super admins, and platform super admins can create providers. Without permission, the page doesn’t show the New provider button.
A provider belongs to the current organization. If you manage several organizations, first click the organization name on the left of the top bar and switch to the organization you want to configure.
Put several API keys for the same upstream under one provider, as its provider keys. Create separate providers only when you have several accounts with the same upstream that are topped up in different ways.

Supported upstreams#

You don’t need to select a type or a protocol when you create a provider. The requests a provider can handle are determined by the Request format that its endpoints select. The request formats cover these vendors: OpenAI, Anthropic, Google, xAI, Volcengine Ark, Alibaba Cloud Model Studio, MiniMax, Mistral AI, Cohere, Voyage AI, Jina AI, Hugging Face TEI, Deepgram, ElevenLabs, fal, Replicate, Stability AI, Runway, Luma AI, Kling AI, Meshy, Tripo, Hyper3D Rodin, Tencent Hunyuan 3D, AssemblyAI, Volcengine Doubao Speech, Baidu AI Cloud VOD (relaying MiniMax video generation), and TypeSafe.

Relay services and other compatible services: connect them with the format they are compatible with. Common formats are OpenAI Chat Completions and Responses, Anthropic Messages, and Google Generate Content.
Azure OpenAI and Vertex AI: connect them with the OpenAI and the Google formats respectively, and in the provider key’s Credential type, select Azure api-key, Azure Entra ID, or Google service account.
Another CCHP: connect it with the request formats it offers, and use an LLM key issued by that CCHP as the provider key. When you add the key, CCHP recognizes the upstream as CCHP and from then on reads the key’s balance and group multiplier there automatically; see Upstream ratios and balances. Request logs and tasks on both sides use the same session and task cchp_id. The gateway sends chain request headers such as X-CCHP-Session-Id only to upstreams recognized as CCHP; other upstreams never receive the client’s session ID.

Step 1: Create the provider#

Go to Org management → Provider Management, and click New provider on the right of the page header. When the organization has no providers yet, the button appears in the middle of the page.

In the New provider panel, fill in these fields:

Field	Description
Name	Required. The display name of the provider, for example `example-provider`
Website (optional)	The upstream’s website or console URL, for example `https://www.example.com`. It is used to show the provider icon and a link to the website, and doesn’t affect request forwarding

Click Create and add endpoint. The button is unavailable while the name is empty.

Result: The console opens the details page of the new provider. The new provider is enabled by default, its Top-up ratio is 1, and it has no endpoints or provider keys yet.

New provider panel: name and website New provider panel: name and websiteCCHP

If you already have a batch of API keys and Base URLs, click Smart import in the page header and paste the keys, Base URLs, or configuration. CCHP detects them and creates the providers, endpoints, and provider keys in one go.

Step 2: Complete the basic settings#

The left side of the details page is the section navigation. The Basic section holds the provider’s own information. You can skip this step and change these settings at any time later.

Setting	Description
Provider enabled	On by default. When it is off, none of this provider’s keys take part in routing, and requests in progress are not affected. Each key keeps its own enabled or disabled state, and turning the toggle back on restores the provider. The toggle takes effect as soon as you click it, and you must confirm when you turn it off
Name, Website	The values you entered when you created the provider. You can change them
Icon	Fetched automatically from the website URL. If you didn’t enter a website, it is fetched from the endpoint URL. If no icon is found, the first letter of the name is shown, and you can click Fetch again
Notes	Internal notes for admins
Top-up ratio	What you actually pay to top up with this upstream ÷ the credit you receive, both in US dollars. Enter `1` when you top up at face value. For example, if you pay $0.50 for $1 of credit, enter `0.5`. It is used only for routing and cost tracking (for example, the provider leaderboard), and is never billed to users
New API management token	Fill it in only when the upstream is New API. It is used to read the upstream account balance and group ratios. The token is stored encrypted and is not shown again after you save it
New API user ID	Needed for older versions of New API and for some New API forks. Leave it blank for newer versions. When it is filled in, CCHP sends it in the request headers of each of these forks

After you change any setting other than Provider enabled, the You have unsaved changes action bar appears at the bottom of the page. Click Save in it.

Warning: Enter the upstream’s group ratio in the Cost multiplier of each provider key, not in the Top-up ratio. If you enter the same group ratio in both places, the cost is counted twice. See Provider cost multipliers vs. user billing multipliers.

Provider details: the Basic section and the top-up ratio Provider details: the Basic section and the top-up ratioCCHP

Step 3: Add endpoints and keys, and join groups#

The new provider can’t receive requests yet. Complete the configuration in this order before users’ requests can use it:

Add endpointsEnter a Base URL and select the request formats the upstream supports Add provider keysEnter an upstream API key and set its model whitelist Join provider groupsAdd provider keys to groups so that users’ LLM keys can use them

Other sections of the details page#

Section	Purpose
Endpoints	Add the upstream’s Base URLs and request formats. See step 3
Keys	Add upstream API keys and model whitelists. See step 3
Balance	View the upstream balance of each key and the total, and set the Low balance alert line. See Upstream ratios and balances
Scheduled tests	Test this provider’s keys automatically on a schedule
Redirects	Provider-level model redirects, which apply to all keys of this provider: the requested model name is changed to the upstream’s model name before the request is sent. If a key has a redirect for the same model, the key’s redirect wins
Request/Response Overrides	Conditionally rewrite the requests sent upstream (for example, headers or the request body) or the responses returned to the client. You can apply them to This provider, All keys, or All endpoints
Network	Request timeout, First content timeout, and Idle timeout, plus Protocol preference, Connect timeout, Upload limit per connection, and Connections per host under Upstream connection. See Network settings
Network proxy	The proxies that carry all of this provider’s outbound requests (request forwarding, scheduled health checks, balance and multiplier reads, model sync, endpoint probes, and icon fetching). See Network proxies. Changes save right away
Upstream calls	Always call the upstream with streaming, Request body compression, Responses WebSocket upstream, and Streaming keep-alive. Responses WebSocket upstream defaults to Auto: a Responses turn that the client sends over WebSocket goes to the upstream over WebSocket first, and when the upstream doesn’t support WebSocket mode, the same turn is sent to the same upstream over HTTP without switching candidates. You can also choose WebSocket only or HTTP only
Key protection	The cooldown duration, recovery probes, consecutive-failure removal, and latency-based concurrency limit of this provider’s keys. See Provider keys. A single key can be set separately in the Advanced section of the key edit dialog
Limits	Limit this provider’s usage with limit rules

The settings in Network, Upstream calls, and Key protection are saved for the scope selected in Effective scope in the page header. By default they apply only to the current provider.

Frequently asked questions#

Deleting a provider shows “Can’t delete yet”#

You can’t delete a provider while other objects still use it, for example when it still has provider keys that haven’t been deleted. The message lists these objects. After you deal with them, click Delete provider in the Basic section. Deletion can’t be undone: the provider’s endpoints, its deleted keys, and its configuration are all removed, while request logs, billing records, and audit records are kept.