Bring your own model keys

The idea

A person or org connects its own provider API keys after one free read-only check, and sign-in tokens or credential files are refused before anything is stored.

The problem
Teams want to use their own provider contracts.
Why it matters
Work runs on the customer's keys through a verified, refusal-first intake.
Where it stands
In production as of

A step-by-step replay of this idea is not published yet. The library adds one when a recorded run shows it.

Where it lives in the product

  • Work on your own subscriptions

    An owner's Claude or Codex subscription serves their requests and the org's own work through any employee, never another person's request, and its turns do not count against the dollar budget.

  • Own accounts, execution profiles and payers

    Hosted work uses API keys. A subscription runs only through the vendor's product or the person's own runner. Executor, model, host and payer inherit from the platform through org, role and worker.

  • Model failure handling and outage recovery

    An unusable answer moves one tier up in the same call. Quota or auth failures put an arm on cooldown. A timeout retries at lower effort. A transient outage parks the item on a backoff timer and resumes the same run.

Turn the numbers into shipped work.

Crewshal runs these choices for you: a persistent AI worker with memory and rules, on your Claude and Codex subscriptions.