Copyboys
Every Copyboy has its own inbox. Invite that address to any SaaS product and it signs up, gets its own API key and starts working.
Finish setting up
Three steps and your first Copyboy is at work.
| Copyboy | Status | Connections | Model | Spend · 30d | Useful ops |
|---|
Create the first one. It gets an inbox right away; invite that inbox to a product and the Copyboy onboards itself.
Spend per day
Connections
Every product this Copyboy has onboarded into, and how it works there: API, MCP server or a browser session.
| System | Access | Useful ops | Fail rate | Tokens | Spend | Cost / op |
|---|
Invite to any product. The Copyboy reads the invite, signs up, creates its own API key and the connection appears here.
Recent operations
Delete this Copyboy
Removes the Copyboy and its inbox. Invites sent to that address will bounce. Stored credentials stay encrypted in the vault until purged.
Activity Sample data
What your Copyboys did, most recent first. Each line is one confirmed write in a connected system, with what it cost.
No operations match these filters.
Report Sample data
How many Copyboys you run, which models and systems they use, what it costs, and what actually came out of it.
Spend per day
Every day’s bill, split into what produced a useful operation and what was paid for attempts that failed.
- Paid for completed operations
- Paid for failed attempts
Needs attention
Computed from the same data, with the money attached: what it costs, what it would cost done right, and who owns it.
Nothing stands out in this slice.
Access upgrades
These Copyboys work through a browser: Playwright clicks and screenshots, every step a vision call on an expensive model. Give them a door instead of a window, an API key or an MCP server. The Copyboy can usually provision the key itself.
Everything in this slice already runs over API or MCP.
| Copyboy | System · how it works today | Useful ops | Cost / op now | Over API / MCP | Avoidable |
|---|
Model fit
Prices are per 1M tokens, input / output. Most people hand every Copyboy the biggest model; the work profile says how much model each one actually needs. Estimated on API and MCP work only; browser work is counted under access upgrades.
| Copyboy · work profile | Runs on | Recommended | Spend now | If switched | Avoidable |
|---|
By team
Where the money went, by the people who sponsor each Copyboy.
| Team | Useful ops | Cost / op | Spend | Share |
|---|
By model
Which models the fleet runs on, what they cost per 1M tokens (in / out) and per useful operation.
| Model | $ / 1M | Copyboys | Tokens | Cost / op | Spend | Share |
|---|
By system
Where the work lands. Browser-driven systems are the usual cost outliers.
| System | Copyboys | Useful ops | Fail rate | Spend | Cost / op |
|---|
By Copyboy
Click a row to open that Copyboy. Sort by any column.
| Copyboy | Status | Model | Systems | Tokens | Spend | Useful ops | Cost / op | Fail rate |
|---|
Settings
Your account, the LLM key your Copyboys run on, and the domain their inboxes live at.
Account
One account, many Copyboys. Everything a Copyboy learns is stored encrypted under this account.
- Name
- Member since
OpenRouter key
The key your Copyboys use to read invites and drive the browser. Stored encrypted, verified against OpenRouter, only ever shown masked. Get one at openrouter.ai/keys.
Inbox domain
New Copyboys get an address at . Keep the default
or use your own domain: point its catch-all (MX) at the Copyboy inbound webhook.