One documented gateway for OpenAI-compatible and Claude-compatible clients.
Use a CloudService API key with the protocol your client already understands. API-credit keys draw down a published-price balance; token-budget keys draw down a provider-scoped token allowance.
Start with the client, then choose the matching key.
API credit
A single prepaid USD credit balance can cover supported OpenAI-compatible and Claude-compatible routes. Each completed request is charged at the customer-facing model rates published by CloudService.
Token budget
A prepaid token allowance is tied to the family selected at purchase: Claude, OpenAI, combined Claude + OpenAI, Gemini, Grok, Qwen, or an exact-model entitlement such as DeepSeek V4 Flash.
Protocol compatibility
“Compatible” describes the request and response protocol. It does not mean every vendor-specific feature is available in every client. Check the relevant setup guide and the model capabilities returned to your key.
Use the route that matches both the key and client.
Do not interchange credit and token URLs. Native Claude clients use an origin-style gateway; OpenAI-compatible clients use a base URL ending in /v1.
| Route | Base URL | Notes |
|---|---|---|
| API credit · OpenAI-compatible | https://api.cloudservice.services/v1 | For Codex, SDKs, and clients configured for OpenAI-compatible APIs. |
| Token budget · OpenAI-compatible | https://api.cloudservice.services/token/v1 | For a compatible token-budget key and OpenAI-style client. |
| API credit · native Claude | https://api.cloudservice.services | For native Claude clients that append /v1/messages themselves. |
| Token budget · native Claude | https://api.cloudservice.services/token | For a Claude-capable token key in a native Claude client. |
A reliable first-request workflow.
- 01
Choose the target client
Open the client-specific guide before buying a key. It states the protocol, base URL shape, and supported billing modes.
- 02
Create the matching key
Choose API credit for a USD credit balance or a token plan for a fixed allowance. A key keeps its billing family and scope when renewed.
- 03
Fetch the model catalog
Call the authenticated /models route and copy an API model ID exactly. The available list is scoped to the key and active routes.
- 04
Send a small verification request
Start with a short prompt and a small output limit. Record the HTTP status and request ID if support is needed.
Compatibility boundaries worth knowing.
- Model availability is determined by the authenticated catalog, not by a static marketing list.
- A Claude-only token key does not open OpenAI-family models, and an OpenAI-only token key does not open Claude-family models.
- Tools, images, reasoning controls, and other optional features depend on both the selected model and the client integration.
- CloudService publishes customer billing rates; internal provider-cost accounting is separate and is not a customer charge.
Continue with a focused resource
Connect with the correct route the first time.
The guided setup asks what you are configuring, recommends a compatible key, and keeps the base URL visible before you continue.