For cost-conscious OpenClaw, Hermes, and OpenCode users
Cost-efficient compute for agent workloads.
Point your OpenAI or Anthropic client at Blue Claw and run recurring agent work on lower-cost open models. Change one setting and keep your stack.
Already have an account? Go to Console.
01 - The Problem
Recurring agent work gets expensive.
Agents run in loops. They review code, triage inboxes, summarize transcripts, and index documents, making the same kind of call thousands of times. At that volume the cost per call is what decides whether the workload is worth running, and on premium APIs it adds up fast.
02 - The Switch
Change the endpoint. Keep the workflow.
Blue Claw serves native OpenAI and Anthropic routes: chat, Responses, Messages, models, images, speech, audio, and embeddings. Point your client at it, keep your SDK and tool wiring, and route recurring work to lower-cost open models. Each model lists the endpoints it supports. It runs on a network of independent GPUs, so the same calls cost less. See how it works.
OpenAI SDK
from openai import OpenAI
client = OpenAI(
base_url="https://staging-api.blueclaw.network/v1",
api_key="your-api-key",
)
response = client.chat.completions.create(
model="MODEL_ID",
messages=[{"role": "user", "content": "Hello!"}],
)
print(response.choices[0].message.content)Anthropic SDK
from anthropic import Anthropic
client = Anthropic(
base_url="https://staging-api.blueclaw.network",
api_key="your-api-key",
)
message = client.messages.create(
model="MODEL_ID",
max_tokens=1024,
messages=[{"role": "user", "content": "Hello!"}],
)
print(message.content[0].text)Anthropic clients take the API's root as their base URL. Use a model that lists /v1/messages.
Claude Code
export ANTHROPIC_BASE_URL="https://staging-api.blueclaw.network"
export ANTHROPIC_AUTH_TOKEN="your-api-key"
export ANTHROPIC_MODEL="MODEL_ID"
export ANTHROPIC_DEFAULT_OPUS_MODEL="MODEL_ID"
export ANTHROPIC_DEFAULT_SONNET_MODEL="MODEL_ID"
export ANTHROPIC_DEFAULT_HAIKU_MODEL="MODEL_ID"
# Removes pre-release betas and their fields from each request.
export CLAUDE_CODE_DISABLE_EXPERIMENTAL_BETAS=1
claudeAnthropic says it doesn't support routing Claude Code to non-Claude models through any gateway. The protocol is documented and this setup uses it, but a Claude Code update could break it, and neither we nor Anthropic can promise otherwise. Use a model that lists /v1/messages.
Codex
# ~/.codex/config.toml
model = "MODEL_ID"
model_provider = "blueclaw"
[model_providers.blueclaw]
name = "Blue Claw"
base_url = "https://staging-api.blueclaw.network/v1"
env_key = "BLUECLAW_API_KEY"
wire_api = "responses"Codex speaks only the Responses route, so use a model that lists /v1/responses. Its web_search tool does nothing here, because the model server silently drops it. Leave apply_patch off, because the model server rejects its grammar.
opencode
// ~/.config/opencode/opencode.json
{
"$schema": "https://opencode.ai/config.json",
"provider": {
"blueclaw": {
"npm": "@ai-sdk/openai-compatible",
"name": "Blue Claw",
"options": {
"baseURL": "https://staging-api.blueclaw.network/v1",
"apiKey": "{env:BLUECLAW_API_KEY}"
},
"models": {
"MODEL_ID": {
"name": "MODEL_ID",
"limit": { "context": 128000, "output": 8192 }
}
}
}
},
"model": "blueclaw/MODEL_ID"
}Set limit.output to a sensible cap. The default can reach 256k tokens, which inflates the hold on your balance. This sample uses @ai-sdk/openai-compatible for chat. Use @ai-sdk/openai for Responses or @ai-sdk/anthropic for Messages. Don't name the provider vllm, because opencode then replaces your configured models.
OpenClaw
// ~/.openclaw/openclaw.json
// OpenClaw uses JSON5, so comments are supported.
{
"agents": {
"defaults": {
"model": {
"primary": "blueclaw/MODEL_ID"
}
}
},
"gateway": {
"port": 18789,
"mode": "local",
"bind": "loopback"
},
"models": {
"mode": "merge",
"providers": {
"blueclaw": {
"baseUrl": "https://staging-api.blueclaw.network/v1",
"apiKey": "${BLUECLAW_API_KEY}",
"api": "openai-completions",
"headers": {
"User-Agent": "OpenClaw/BlueClaw"
},
"authHeader": true,
"models": [
{
"id": "MODEL_ID",
"name": "MODEL_ID",
"api": "openai-completions",
"input": ["text"]
}
]
}
}
}
}Hermes / env
# Hermes-style agents, LiteLLM routers, and most
# tools that speak the OpenAI API read these variables:
export OPENAI_BASE_URL="https://staging-api.blueclaw.network/v1"
export OPENAI_API_KEY="your-api-key"
# Then point your agent at a model that lists /v1/chat/completions:
# model = "MODEL_ID"curl
curl https://staging-api.blueclaw.network/v1/chat/completions \
-H "Authorization: Bearer your-api-key" \
-H "Content-Type: application/json" \
-d '{
"model": "MODEL_ID",
"messages": [{"role": "user", "content": "Hello!"}]
}'- Streaming in each protocol's standard format
- Tool calling with your existing wiring
- Open-model presets for recurring agent work
- Drop-in switch: change the base URL, keep the stack
Run today
Native OpenAI and Anthropic routes for recurring agent work. Each model lists the endpoints it supports.
- Chat completions
- Responses
- Messages
- Models
- Images
- Speech
- Audio
- Embeddings
Metered per request against your prepaid credit balance.
03 - Pricing
Predictable cost, no surprise bills.
You run on prepaid USD credits: buy what you use, with no subscriptions and one balance. Per-request pricing is metered against a live price sheet, with per-key spend caps so agent workloads stay inside budget.
| Workload | Premium APIs | Blue Claw |
|---|---|---|
| Recurring chat & agents | Metered at frontier per-token rates | Capable open models, lower marginal cost |
| Embeddings & indexing | Per-token, adds up at scale | Batch-friendly, lower cost |
| Image generation | Premium per-image pricing | Open image models |
| Heavy / async jobs | Full price, no queueing discount | Async job mode with cost ceilings in development |
Live per-model pricing is on the Models page in the console. See the quick start to try it on one workload first.
04 - Trust & Privacy
Clear privacy boundaries, baked in.
Practical constraints are part of the product story, not a footnote.
See the privacy policy for details.
- No content stored by Blue Claw
- Blue Claw doesn't store prompts, inputs, or outputs.
- Who sees your work
- Work goes to a decentralized set of worker nodes run by independent operators, who can see and may log what's sent. A vendor-marked model also sends it to that vendor, named on the model.
- Billing and usage records
- Billing and usage facts stay in a permanent log tied only to an account ID. Limited operational metadata is kept for abuse prevention, reliability, and debugging.
- Not every workload yet
- No TEE, E2EE, or confidential-compute guarantee yet. Review sensitive or regulated workloads before using the service.
05 - Get Started
Bring one real agent flow.
Sign in with your email, and we send a 6-digit code with no password. Then buy prepaid credits in the console to start making requests.