Toolaby for coding agents
Your coding agent sets up the pricing, gates the paid code, checks its own work and proves on Test that the paid feature unlocks, before you load it.
npx -y toolaby@latest agentsMake exporting data a Pro feature for $5 once.
Works with your coding agent
Set up
The plugin in Claude Code. One command for Codex, Cursor, VS Code and Gemini CLI. Any other agent, by hand.
/plugin marketplace add toolaby/claude-plugin
/plugin install toolaby@toolaby
It brings
Node.js 20 or laterOn Test unless told --live
Your agent calls toolaby_sign_in and gives you a link and a code. Approve it in the browser: it acts as you, with your roles.
wire writes them into your project: how this extension sells, where gate() goes, how to check it, and what only you can do.
Each of the 30 MCP tools is also npx -y toolaby@latest <command> --json, for an agent without MCP.
What it can do
30 tools over MCP, each also a command, on Test until you say Live.
Arguments
{ "tool": "acme--word-counter", "billing": "one_time", "amount": 5, "currency": "usd", "name": "Pro" }Result
{ "ok": true, "message": "Price created on your Stripe account.", "plan": { "id": "default", "name": "Pro · Lifetime" } }One-time or a subscription, with a trial, devices and seats. Each plan is a price on your own Stripe account, and each feature names the plans that unlock it.
1import { toolaby } from './toolaby.js';23toolaby.startBackground({4handlers: {5async exportAll({ tableIds }) {6const permit = await toolaby.gate({ feature: 'export' });7if (!permit.allowed) return { permit };8return { ok: true, file: await buildExport(tableIds) };9},10},11});One call before the paid action: gate() asks, and showPaywall() answers a refusal with your plans, in your extension’s own popup.
npx -y toolaby@latest check --jsonexit1{ "ok": false, "side": "Test", "findings": [ … { "code": "FEATURE_KEY_UNKNOWN", "level": "error", "message": "The code gates on \"export\", which is not a feature of the tool: every buyer would be refused. …", "file": "popup.js", "fix": "npx -y toolaby@latest features acme--word-counter --features '[{\"key\":\"export\",\"name\":\"export\"}]'", "docs": "https://toolaby.app/docs/gating" } ]}
Each finding has a code that never changes and says what to fix, with the command when there is one. The agent fixes it and checks again, until no error is left.
check --jsontoolaby_get_toolcheck --browser --builttest-unlock acme--word-counter --plan defaultcheck --browser --as defaultUNLOCK_OKtest-unlock gives your Test buyer the plan, with no card and no person. Then check loads the extension in Chromium as that buyer, and the paid feature has to unlock.
Look a buyer up, give access, make a coupon for the store’s reviewer, refund or cancel. What takes something away says so, and on Live asks you first.
Copy to Live, the Live key, then pack makes the zip and refuses secrets and Test keys. The upload and the review stay yours.
Safe by design
Your agent works where nothing charges anyone, and a change real buyers would see waits for your word.
Refund a licence on Live (https://toolaby.app) with {"tool":"acme--word-counter","email":"rosa@example.com"}. This takes something away and cannot be undone here.Ask the person to confirm, then call toolaby_refund again with the same arguments and confirm: "4f2a9c" (valid 5 minutes).
Needs your word
Refund a licence on Live
This takes something away and cannot be undone here.
toolaby_refund({
"tool": "acme--word-counter",
"email": "rosa@example.com"
})confirm: "4f2a9c"valid 5 minutes, for these arguments only
Every command and the MCP server act on Test unless told --live. Test buyers, cards and keys never reach Live by themselves.
On Live, every change answers a summary and a confirm code first, valid for 5 minutes and for those arguments only.
api-keys create writes TOOLABY_API_KEY into your .env and never prints it. The extension holds only the tool key, which is public.
Every change goes through the same checks as the dashboard. A member whose role cannot change a tool is refused.
Your agent is told these are yours, and never to report them as done.
Approve the sign-in
Once, on each side
Connect Stripe on Live
Configure → Payments
Upload to the Chrome Web Store
And submit it for review
Make the first real purchase
On Live
The session above ends: “I can run the Live-copy steps when you're ready, but the Stripe connection, store upload, and first real purchase are yours to do.”
Docs for agents
Every page is Markdown at its own address, and all of them are one file. The skills tell your agent to search them before it writes Toolaby code, over MCP or by address.
https://toolaby.app/llms.txt
# Toolaby > Toolaby runs accounts, licences, subscriptions, trials, seats and the paywall for Chrome extensions that sell, on the developer's own Stripe account. A developer wires an extension to a tool with `npx -y toolaby@latest`, sets plans and features in the dashboard or from a coding agent, and gates paid work with `gate()`. Every page below is also Markdown at its address with `.md`. ## Instructions for agents - Set up once: `npx -y toolaby@latest agents` registers Toolaby's MCP server (`npx -y toolaby@latest mcp`) in Claude Code, Codex, Cursor, VS Code and Gemini CLI. These docs alone, with no sign-in, are an MCP server at https://toolaby.app/api/mcp.- Before writing Toolaby code, search these docs (`toolaby_search_docs`, or `npx -y toolaby@latest docs search <query>`) and read the page. Every page is Markdown at its address with `.md`. The client's methods are in https://toolaby.app/docs/reference/client.md: never guess one.- In an extension wired to Toolaby, read `TOOLABY.md` at the project's root first. Never edit the `toolaby*` files: `npx -y toolaby@latest upgrade <tool>` replaces them.- Gate paid work with `gate()` in the code that does the work; `has()` is for display only. A feature key in code must exist on the tool, and a plan must sell it.- Everything acts on Test unless told `--live`. On Live, a change first answers a `confirm` code: send it only on the person's word. …
On every docs page, under its title. Here, for the agents guide:
Questions
Answered the way the docs answer them.
Any agent that connects to MCP servers. npx -y toolaby@latest agents sets Toolaby up in Claude Code, Codex, Cursor, VS Code and Gemini CLI at once, and Claude Code also has a plugin with the skills and five commands. Windsurf and any other client take the server by hand: the command npx, with -y toolaby@latest mcp. Set up your agent