Base URLs
SP Cambo has two surfaces. Sending a request to the wrong one is the most common setup mistake.
The two surfaces
The control plane manages your account: packages, orders, entitlements, API keys and usage. The inference gateway serves model requests. They authenticate differently and they are not interchangeable.
| Purpose | Base URL | Credential |
|---|---|---|
| Account, packages, orders, keys, usage Used by this website. Not intended for your application code. | https://sp-cambo.store/api/v1 | Browser session (from signing in) |
| Anthropic-compatible inference Root only. The client appends /v1/messages itself. | https://sp-cambo.store | SP Cambo API key |
| OpenAI-compatible inference Must end in /v1. Configure the Responses wire API. | https://sp-cambo.store/v1 | SP Cambo API key |
The /v1 trap
Anthropic-compatible clients append /v1/messages to whatever base URL you give them. If you include /v1 yourself, the client will request /v1/v1/messages and every call will fail with a not-found error that looks like an outage. Use the root for ANTHROPIC_BASE_URL.
OpenAI-compatible clients are the opposite: their base URL must end in /v1.
What you will never see
SP Cambo does not publish, and will never ask you to configure, an upstream provider URL or an internal routing endpoint. If a setup guide anywhere tells you to point a client at an internal host or a loopback port, it is not ours. The only hosts you need are in the table above.
Local development
In a local development environment these URLs point at your own running services rather than production, which is why they are read from configuration rather than hard-coded. The values in the table are the ones this build is configured with, so they are always the correct ones for the site you are reading.