Skip to content

Authentication

CloudService uses bearer-token authentication. Every request includes an Authorization header with your API key.

Getting a key

Use the CloudService API key provided to you, or choose API credit, Claude tokens, or OpenAI tokens on the CloudService pricing page. First-time buyers receive a fresh API key after payment confirmation. CloudService is prepaid access, not a subscription SaaS.

Sending the key

Include the key in the Authorization header of every request:

request
Authorization: Bearer YOUR_CLOUDSERVICE_API_KEY

The header name and format are identical to OpenAI's. OpenAI-compatible SDKs use it unchanged with the matching /v1 base URL; native Anthropic clients use the same Bearer key with their origin-only gateway URL.

Key type and base URL

Do not infer the URL from the key name. Select the billing surface and client protocol below, then use only models returned by that key's authenticated catalog.

Start with the key you bought

Choose one billing path

Your choice is remembered across the documentation. Then select the card that matches your client protocol.

For a key funded with a dollar credit balance.

OpenAI-compatible Chat Completions or Responses

Use with: Codex, OpenCode, Cursor, Roo Code, SDKs, and direct HTTP

Base URL to enter

https://api.yourdomain.example/v1

Native Anthropic Messages

Use with: Claude Code, Claude Desktop, and native Messages clients

Base URL to enter

https://api.yourdomain.example

The protocol decides whether the client field ends in /v1. OpenAI-compatible clients use a base URL ending in /v1. Native Anthropic clients use the origin only, without /v1, because they append /v1/messages themselves. A Claude token key therefore reaches /token/v1/messages when the native client builds its request.

Use the key's matching billing surface and only models returned by its authenticated catalog. A Claude token key and an OpenAI token key are provider-scoped; neither can be swapped onto the other's models.

Claude Desktop is a native Anthropic client with its own third-party inference settings. Follow the Claude Desktop guide; it does not read Claude Code's configuration.

Key properties

  • Active / inactive. Revoked keys are rejected with a 401.
  • Expiry date. Hard expiry. After expiry the key returns 403.
  • Per-key budgets. Token-budget keys hold a prepaid token allowance; credit keys hold a USD balance. An exhausted balance returns 402 insufficient_credit — not 429. Authentication itself still succeeds, so read-only endpoints such as model discovery keep working.
  • Per-key rate limits. Configurable requests-per-minute. Returns 429.
  • Per-key provider scope. Keys can be OpenAI-compatible only, Claude-compatible only, or both. Requests outside the key scope return 403.

Security

  • Treat your key like a password. Don't commit it.
  • Use environment variables (CLOUDSERVICE_API_KEY) — never inline it in client-side code.
  • If a key is lost or leaks, sign in to the customer dashboard and use Replace lost key. The remaining entitlement moves to the replacement and the old secret stops working immediately. Contact support only if you cannot access the self-service flow.

Next: Quick Start — your first request in under a minute.