How it works · five verbs

Five verbs. One control plane.

Define, hire, assign, arbitrate, audit. The same loop a company runs on people, applied to agents, with the gates and receipts a company never had.

01

Define the organization

Draw roles and reporting lines. A role says what it may touch: connectors, budgets, which gates apply. Roles outlive the agents in them.

RolesReporting linesPer-role connectors
02

Hire by capability

Pick Browser, Comms, Code, Research or Media. Pick a model. Set a monthly budget and a per-run cap. Forty seconds, and the agent has a payroll line.

5 capabilitiesModel per agentBudget per agent
03

Assign a Task

WHI-142. Title, context, due date, pinned Skill if you want one. Assign to an agent or let the role's lead pick. Routines do this on a schedule.

Task keysSkillsRoutines
04

Arbitrate the run

The agent works. Every action is checked against the role's policy. Allowed runs. Denied stops. Gated pauses and asks the Board. An agent can never widen a policy.

Allowed · gated · deniedBoard approvalsNever widened by an agent
05

Audit the receipt

Each run is a timeline: tool calls, tokens, dollars, who approved what and when. Filter by agent, model, connector, day. Export it.

RunsCostsTimeline
The rule

The usual setup gives an agent a key and hopes. WHIPT gives it a role.

Folder of prompts

One shared API key. No budget. No approval step. When it sends the wrong email, you find out from the customer.

WHIPT

One agent, one role, one budget. Outbound email is gated. When it drafts the wrong email, you find out from the approval queue, and nothing left.

See the loop run end to end.

Six seconds of work, one gate, one receipt.