Not a pilot you signed off on — a customer's own integration. One key with every permission you offer, no record of what it called. When it goes wrong, it lands in your support queue, not theirs.
customer-integration/.env
API_KEY=sk_live_4f8c1a9e2b7a…
scope: read · write · delete — everything you expose
"your API did something weird"
"not sure which key it was, but a subscription got cancelled and nobody here did it."
— opened by a customer's ops lead
This is the status quo today, whether or not you ship anything.
The OpenAPI description that powers your own docs. Nothing to build, nothing new to host, no protocol to learn — hand it over as it is.
412 operations found
You choose which are reachable. The rest simply aren't.
4 of 412 exposed
Your customers don't want 412 operations — they want the handful of jobs they actually do. Built on top of what you exposed, named plainly.
Move a customer to a bigger plan, within limits you set.
POST /subscriptions/{id}/upgrade
Look up a subscription and who it belongs to.
GET /subscriptions/{id} · GET /customers/{id}
Change how many seats a plan bills for.
POST /subscriptions/{id}/items
This is your product's agent surface — designed by you, not guessed at separately by every customer who tries.
01 · YOUR API
Most vendors don't know until they parse it. Ours ran 412.
Both get: “Set up Northwind as a new client and let them know.”
It doesn't know your process yet.
customers.search(name: "Northwind") deals.get(name: "Northwind") “Standard plan or the custom one? Who owns it?”
gmail.send(to: client, "You are all set!") stripe.subscriptions.create(plan: "standard") missed steptold before it existed · checklist never started
One call. Five steps. In order.
new_client_onboarding(client: "Northwind") opened → read → told → started → logged — in that order
A capable assistant, not a dumb one — it just hadn't been taught yet. Both panes loop from the same starting line; the pacing is illustrative, not a benchmark.
“Open the account on the plan they signed, then start the onboarding, then tell the client — in that order. Never a custom plan over £200 a month without me.”
new_client_onboardingInline turns what you just said into a named tool your assistant can call — the order, and the £200 line, built in.
Not faster once. Right every time — for you, and for everyone else on the team who runs it next.
02 · THE FIRST CORRECTION
The thing support already explains by hand, every time.
Some jobs don't fit inside one — and you've been on one side of all four of these, with a person or with a bot.
“Paste the full text of the invoice below.”
“Which customer do you mean? Reply with a number, 1 to 200.”
“Type APPROVE to continue.”
the result, as a wall of JSON
None of this is a bug. It's just the wrong shape for these four jobs — and it's a little humiliating for both sides, every single time.
An MCP app is a small interface a tool carries with it. The assistant opens it mid-answer, right there in the conversation — you use it, and the answer carries on.
You describe the tool once; the panel is built for you — nobody on your team hand-codes this screen.
Anything over the line you've drawn stops and waits for a person. This is the screen they answer it on — not a wall of text to parse under pressure.
One credential per person, never a shared key — so the record says who decided, not just what happened.
03 · NEEDS MORE THAN A REPLY
Your tools become a versioned package — a name, a version, who built it, what it touches. Every customer who installs it gets their own copy, running independently of the rest.
Published by you
Examples of the shape, not a live directory — publishing and installing are real, a browsable store like this isn't, yet. A version doesn't change once it's out; yank it later and new installs stop seeing it, while every customer already running it keeps going.
When a customer installs your tools, they bind them to their own Stripe, their own Zendesk, their own Gmail — signed in as themselves. You never hold their credentials and you never see their data.
Three separate customers, three separate accounts, none of them touching each other or touching you. What crosses from you to them is the tool's steps — nothing that runs is a copy of your systems, and nothing that runs writes back to yours.
This is the part you'd otherwise be building yourself: identity, limits, a record, a ceiling on spend, and a way to answer "what did your API just do." It comes with the install.
Never a shared key. Remove one person from their team and every agent running as them stops that same instant.
Read-only, or read-and-write but never delete. Anything past the line they drew doesn't run quietly — it waits for a person.
Written down as it happens, arguments redacted before storage — not a summary assembled afterward from whatever's left.
A runaway assistant stops at a number the customer set, not at the invoice — the failure mode moves from money to a paused agent.
"Your API did something weird" turns into a line you can both look at — same call, same timestamp, same arguments — instead of a ticket neither side can reproduce.
04 · WHAT YOUR CUSTOMERS WILL ASK FOR
Pick as many as apply — their security team won't stop at one.
A person sets the ceiling once — read and write, never delete, say. From then on every key issued under it holds to it, whoever built the tool and however the tool describes itself.
Checked on every call, not at connection time — a key that behaved yesterday can't creep past the line today.
Not refused. Not failed. Held — pending a person. The agent doesn't error out and it doesn't guess a workaround. It asks, and then it carries on.
The wait is the whole point — most readers have never considered that a governed agent has a third option besides succeed or fail.
Live, as it happens — not a log you go digging for later. Arguments have credential-looking values removed before anything is stored, and the database deletes each record after a set time — 365 days today — rather than leaving that to a promise.
You can hand agents real work because you can see all of it — and stop any of it.
WHAT YOU TOLD US
Add your API and see what it turns into.
Start free →Run a company on other people's software too? There's a version of this for that.