Own accounts, execution profiles and payers

The idea

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.

The problem
Work could quietly change its model, machine or payer, or need someone's session token.
Why it matters
Each run uses the configured route and payer or stops with a reason, and listed work never uses paid APIs.
Where it stands
In production as of

Recorded evidence

  • Production · A task on the owner's own subscription

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

  • A harness around swappable agents

    The parts of a worker's harness are pluggable: models, tools, context, rules, checks, decisions, verification, memory and evaluation. Each is set per organization, repository, person and run.

  • Call and queue admission

    PostgreSQL slots cap concurrent provider calls per fleet, org and account. Queue claims interleave organizations. A call with unknown usage keeps its full reservation held.

  • Bring your own model keys

    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.

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.