Build on the Bench your clients already run.
Every contractor’s stack is custom glue — a CRM here, a measuring tool there, spreadsheets holding it together. Bench is the operation underneath, and it’s open to build on. Ship skills and agents that ride the same approval rails the shop already trusts.
Skills and agents, on the same operation.
You’re not bolting onto a black box. You’re building on the platform the shop already works in — so what you ship shows up where the work happens.
Skills
Package a piece of how a shop runs into a skill your clients’ agents can call — the same way the built-in skills work today.
Agents on the rails
Wire skills into agent workflows that move deals, schedule work, and draft follow-ups — gated by the same approval steps you already trust.
The REST surface
Read and write the operation directly over HTTP at benchagi.com/api. Any language, any framework — it’s the same data your agents see.
Simple keys. The owner always signs off.
API key auth
Pass your key in the X-API-Key header on every request. No OAuth dance to start building.
Instance-scoped
Each key is scoped to one instance. Your client’s data stays isolated — keys never reach across tenants.
Owner-approved
The covenant holds for code, too: anything an agent does on a client’s account is owner-approved before it lands.
curl https://benchagi.com/api/agent/deals \
-H "X-API-Key: your_instance_key" \
-H "Content-Type: application/json"Three steps to your first build.
- 1
Get a key
Generate an instance-scoped API key from the dashboard. It authenticates every call you make.
- 2
Ask about API access
Walk the REST surface — the resources, the shapes, and how auth and rate limiting work.
Ask about API access - 3
Ship a skill
Build in any language against the REST API, keep every action behind its approval gate, and put it in front of the shops already running Bench.