SP Cambo
All documentation

Quick start

From a new account to a working request. Nothing here requires a provider account of your own.

1. Create an account

Sign up with an email address and a password of at least 12 characters. No payment method is stored, and nothing renews automatically.

Create your account , then sign in. Your dashboard is the authoritative view of your balance, keys and usage.

2. Buy a package

Open Buy tokens & credits and choose a package. Each package publishes its price, its included units, its exact lifetime in seconds and the model aliases it covers.

Checkout produces a Bakong KHQR code. Scan it with your banking app. The countdown you see is driven by the server, not your local clock. When you have paid, you can ask SP Cambo to re-check immediately — but only our backend can mark an order paid, and access activates only after that verification succeeds.

3. Issue an API key

Go to API keys and create a key. Scope it to the models you intend to call, and give it a label that identifies where it will live, for example laptop-cli or ci-runner.

Copy the full secret into your password manager or environment. Normal key lists show only the prefix and last four characters. If you need the current secret later, open API Keys and choose Copy key; the authenticated reveal is throttled and audited. Rotate the key if you suspect exposure.

4. Pick a model alias

Browse the model catalogue and copy a public alias. Aliases are stable: SP Cambo can change upstream routing for reliability without breaking your configuration, so always configure the alias rather than a provider-specific model id.

5. Make your first request

For Claude Code, export two variables and run it. Note that the base URL is the gateway root with no /v1 suffix — Claude Code appends its own path.

bash
export ANTHROPIC_BASE_URL="https://sp-cambo.store"
export ANTHROPIC_AUTH_TOKEN="sk-your-key"
export ANTHROPIC_MODEL="<your-model-alias>"

claude

Or call the Messages API directly:

bash
curl https://sp-cambo.store/v1/messages \
  -H "x-api-key: sk-your-key" \
  -H "anthropic-version: 2023-06-01" \
  -H "content-type: application/json" \
  -d '{
    "model": "<your-model-alias>",
    "max_tokens": 256,
    "messages": [{ "role": "user", "content": "Hello" }]
  }'

6. Verify it worked

Your dashboard overview shows the request within seconds. While a request is in flight its figures are marked Estimated: SP Cambo reserves an estimate up front and then settles against the usage the provider actually reported. Only settled rows are final.

Where to go next

  • Authentication — key scoping, rotation, and what to do if a key leaks.
  • Errors — the stable codes to branch on instead of parsing messages.
  • Billing model — how reservations, settlement and expiry actually work.