Quickstart
Create a key, copy its gateway base URL, and point your SDK at it.
1. Create a key
In the dashboard, open API Key and create a key. Two fields decide how it behaves:
| Field | Values |
|---|---|
| Platform | The upstream provider this key is bound to. One key serves one platform |
| Mode | safe forwards to the provider; mock answers locally for development |
Creating a safe key also asks for the platform's real API key: the gateway
stores it encrypted and forwards with it — the provider still sees your key.
2. Copy the safe-key and the base URL
The safe-key is shown when the key is created. It is also stored encrypted, so you can copy it again from the dashboard at any time.
A key only works on the platform it was created for. Replace the vendor's entire base URL with the gateway base URL for that platform:
| Platform | Vendor base URL (replace this) | Gateway base URL (use this) |
|---|---|---|
| OpenAI | https://api.openai.com/v1 | https://sluiceline.com/openai |
| DeepSeek | https://api.deepseek.com | https://sluiceline.com/deepseek |
| Claude | https://api.anthropic.com | https://sluiceline.com/anthropic |
| fal.ai (sync) | https://fal.run | https://sluiceline.com/fal |
| fal.ai (queue) | https://queue.fal.run | https://sluiceline.com/falqueue |
| ByteDance Seedance | https://ark.ap-southeast.bytepluses.com/api/v3 | https://sluiceline.com/seedance |
Replace the whole base URL
Two of them already end in a version segment — OpenAI's /v1 and Ark's /api/v3
— and the whole URL is what you replace. Request paths are written as the vendor
documents them after that segment: /chat/completions, never
/v1/chat/completions. Claude's base URL has no version segment, so its path
really does begin with /v1/messages.
The credential each platform expects, and the full path rules, are in One-click switching.
3. Point your SDK at the gateway
curl https://sluiceline.com/openai/chat/completions \
-H "Authorization: Bearer $SLUICELINE_SAFE_KEY" \
-H "Content-Type: application/json" \
-d '{"model":"gpt-6-astra","messages":[{"role":"user","content":"hi"}]}'The base URL and the credential are the only two values that change. The gateway resolves the safe-key, applies its quotas, and forwards to the provider with your real key.
Without writing code
Playground sends a request through the gateway from this site. A mock key consumes no provider credit and no quota.