BytesBrains Cruise for OpenClaw

Every model your Cruise key can reach — as an OpenClaw provider —
with budgets, per-project keys, and one cost ledger that stay on the gateway.

What this is

BytesBrains Cruise is one OpenAI-compatible endpoint in front of every model provider. This repository is the OpenClaw client: an installable provider plugin that discovers models from GET /v1/models for your key, plus a verified recipe for manual config.

Your keys, budgets and ledger stay on the gateway. OpenClaw only holds a cru_ key and talks to the base URL you configure.

Published as @bytesbrains/openclaw-cruise-provider on npm and ClawHub.

Install the provider plugin (preferred)

The plugin refreshes the model list from Cruise so you do not hand-edit windows or costs from a screenshot. Costs and limits come from each row’s x-cruise metadata. The two lane rows in openclaw.plugin.json are offline seeds only (setup / no-auth fallback); live discovery replaces them when a key is present.

# ClawHub (preferred for OpenClaw plugins)
openclaw plugins install clawhub:@bytesbrains/openclaw-cruise-provider

# or npm
openclaw plugins install npm:@bytesbrains/openclaw-cruise-provider

# or from this checkout (development)
npm run build
openclaw plugins install .

export CRUISE_API_KEY=cru_demo_…   # or cru_live_…
openclaw gateway restart
openclaw models list --provider cruise

Onboarding can also take --cruise-api-key. Default production base URL is https://cruise.bytesbrains.net/v1; point models.providers.cruise.baseUrl at https://cruise-demo.bytesbrains.net/v1 for the demo (must be https under *.bytesbrains.net).

Secrets never enter the published artifact — only dist/, openclaw.plugin.json, README, and the license. npm run pack:check (and gitleaks with .gitleaks.toml on the extracted tarball) fail the release if a Cruise key shape appears. Keys stay in the environment.

Releases (maintainers)

A release is a tag, not a merge. Bump package.json version, update CHANGELOG.md, merge to the release branch, then:

git tag v0.1.0
git push origin v0.1.0

Two workflows fire on v*:

@bytesbrains/openclaw-cruise-provider@0.0.1 is already on npm and ClawHub. Later versions: bump, tag vX.Y.Z, and let the workflows publish. npm Trusted Publisher is configured for bytesbrains/openclaw-cruise + release.yml. Keep CLAWHUB_PUBLISH_TOKEN for tag publishes (and ClawHub trusted publishing for workflow_dispatch if you enable it).

Try it before anyone issues you a live key

1. Get a cru_demo_ key from bytesbrains.com/cruise (or whoever runs your BytesBrains demo).
2. Put the key in the environment — a shell profile or a secret manager, not a checked-in config file:

export CRUISE_API_KEY=cru_demo_…

3. Prefer the plugin path above. Or add a Cruise provider under models.providers (OpenClaw's OpenAI-completions path) by hand — point at the demo host first:

{
  env: { vars: { CRUISE_API_KEY: "cru_demo_…" } },
  agents: {
    defaults: {
      model: { primary: "cruise/bb/agentic-coding" },
    },
  },
  models: {
    mode: "merge",
    providers: {
      cruise: {
        baseUrl: "https://cruise-demo.bytesbrains.net/v1",
        apiKey: "${CRUISE_API_KEY}",
        api: "openai-completions",
        models: [
          // Prefer ids from GET /v1/models for your key — do not invent provider ids.
          {
            id: "bb/agentic-coding",
            name: "Cruise agentic coding (lane)",
            reasoning: true,
            input: ["text"],
            // Costs and windows: take them from GET /v1/models for the key you present.
            // Zeros here are placeholders so config validates; the gateway still meters.
            cost: { input: 0, output: 0, cacheRead: 0, cacheWrite: 0 },
            contextWindow: 128000,
            maxTokens: 8192,
          },
        ],
      },
    },
  },
}

A fuller starter lives in examples/openclaw.json5.

For real traffic, switch baseUrl to https://cruise.bytesbrains.net/v1 and use a cru_live_ key the same way.

Model ids

Name the model as Cruise names it, from GET /v1/models with your key — not as the upstream provider does. A hardcoded gpt-4o reaches Cruise as a model it does not route.

A bb/… id is a lane: Cruise picks a member per request. Prefer a lane for agent work (bb/agentic-coding); pin a specific model id only when you need that vendor.

OpenClaw selects models as provider/model — for this plugin that is cruise/<cruise-id>, e.g. cruise/bb/agentic-coding. OpenClaw currently wants each model declared in the provider's models array unless you use the Cruise provider plugin above, which refreshes that list from GET /v1/models. Keep any hand-written array short and refresh it from Cruise when lanes or measurements change.

When Cruise refuses

Cruise answers spending refusals with HTTP 429 and OpenAI's insufficient_quota on purpose, so stock OpenAI clients fail correctly. Branch on error.code, never on HTTP status alone — several codes share 429 and mean different operator actions.

Period cap vs wallet empty: both look like “out of quota” to a generic OpenAI client. OpenClaw (or any agent) should read error.code: budget_exhausted is a time-bound project limit; wallet_exhausted is no prepaid balance left. Confusing them leads to pointless retries or the wrong human escalation.

Auth failures (Missing bearer token, Incorrect API key) use type: authentication_error and are not spending refusals — fix the key or env wiring first.

Ground rules for this client

• Holds a cru_ key, never a provider credential. Blast radius is one revocable, budget-capped key.
• Key in the environment / secret store, never in a committed config. Settings sync and git history are how keys leak without an event to notice them by.
• Traffic only to the configured Cruise base URL. No telemetry, no second host.
• Rehearse on the demo first. cruise-demo.bytesbrains.net with a cru_demo_ key costs nothing and holds no provider credential in the deployment.

See SECURITY.md for reporting.

Product & package

Licence

See LICENSE.txt.

Contributing

See CONTRIBUTING.md. PRs land on dev by default.