Partner with WorkerKit.

Two tracks

Choose the way you work with us.

One program for the products workers connect to, and one for the people who put workers to work. Both start from the same short application below.

• Technology partners For software and service vendors. Make your product a place AI workers can do the job: your app among the connectable apps, scoped access your customers grant and control, and a public page in the app directory built around what workers do in your product.
• Solutions partners For consultants, agencies and advisors. Build and run AI workers for the businesses you serve: private kits as client deliverables, Team plans with central admin and one shared wallet, and Enterprise co-build for the largest rollouts.

Technology partners

Your product, in the hands of AI workers.

Workers reach apps through scoped, revocable grants, so the integration story you tell your customers is the one the platform enforces.

• A page in the app directory. Connectable apps carry a public hub: AI workers for your product, with the capabilities a worker has there and the kits that use it. The directory is brand first: Gmail and Outlook are pages, "email" is not.
• Access your customers control. Every worker's reach into your product is granted per app and per level, Off, Read or Write, behind the app firewall. Customers narrow or revoke it themselves, and the worker keeps running with whatever is left.
• MCP speaks for you already. If your product exposes an MCP server, workers can use it today: customers register it as a custom MCP server, and the Set up with AI flow writes the connection details from your docs.
• Kits carry your product to the job. Publishers build kits around the apps in the catalog, and every kit states its loadout before anyone installs it, so your product shows up wherever it does the work.

The directory this track feeds is public: browse it at the app directory, and see how a connection is described at connected app.

Solutions partners

Run fleets for the businesses you serve.

The delivery model is built in: you write the worker as a kit, and the client runs it in their own account, with their own grants, their own receipts and their own bill.

• Private kits as deliverables. Package an engagement as a private kit. Your client installs it in their own account, and the instruction, the loadout and the schedule arrive exactly as you wrote them. On Team plans, private kits are shared across the client's whole account.
• Team, flat. $299 a month for up to 10 users, not per seat: central worker admin, 50,000 pooled tool calls a day, and one shared wallet with spend controls you can point a finance team at.
• Enterprise for the big rollouts. SSO and SAML, identity sync with an offboarding cascade, a compliance pack, and a private kit program with co-build when the fleet becomes something the company runs on.
• Accountability you can hand over. Every run leaves a receipt. The safety layer, the app firewall, redaction and contact rules, ships on every plan, and model tokens carry no markup: provider list price, or the client's own keys.

Plans and limits are on the pricing page, and the delivery mechanism has its own definition: private kit.

What you get

What acceptance brings.

Three things every accepted partner gets, on either track, from the day the agreement is in place.

• Partner directory and featured placement. A public directory of accepted technology and solutions partners, with featured placement on the surfaces where buyers already look.
• Partner badge. A program mark for your publisher profile and pages, showing membership in the partner program. It marks the relationship, not an audit: WorkerKit does not certify partners' work.
• Early access and a named contact. Accepted partners see new capabilities before general release, and get a named WorkerKit contact who knows their integration or practice.

Programs are governed by individual partner agreements.

How it starts

From application to launch.

Three steps, and no paperwork up front.

• Apply. The form below takes a few minutes: who you are, which track, and what you want to connect or build.
• Scoping call. We walk through your product or practice, agree what the first integration or engagement looks like, and name an owner on each side.
• Launch. Technology partners go live among the connectable apps; solutions partners ship their first client kit. From there the work is real: pages, kits and clients, not a logo wall.

Questions

Partner questions, answered.

• What kinds of partners does WorkerKit work with? Two kinds. Technology partners are software and service vendors whose product AI workers connect to and work in. Solutions partners are consultants, agencies and advisors who build and run workers for the businesses they serve. The application form covers both; pick your track and we take it from there.
• How does my product become connectable by AI workers? Workers reach apps through scoped, per-app grants: Off, Read or Write, behind the app firewall, revocable at any time. Products with an MCP server can be connected by customers today as a custom MCP server. Joining the connectable app catalog itself, with a public page in the app directory, is what the technology track scopes with you.
• Can I build and run workers for my clients? Yes, and the delivery model matters: you build the worker as a kit, and your client runs it in their own WorkerKit account, with their own app grants, their own run receipts and their own billing. Private kits are the deliverable, Team plans give a client central admin and one shared wallet, and Enterprise adds SSO, compliance and co-build.
• What does the partner program cost? Applying costs nothing and there is no program fee. Partners and their clients run on the public plans: Free, Pro at $29 a month, Team at $299 a month flat for up to 10 users, Enterprise custom. Model tokens carry no markup on any of them.
• Does partnering make me a WorkerKit agent or affiliate? No. Partners are independent businesses; the program is a commercial collaboration governed by an individual partner agreement, and nothing in it authorises anyone to act or sign on WorkerKit's behalf. Your clients hold their own WorkerKit accounts under their own terms.

Everything the program feeds is live now: the app directory, the kit directory and the publishers behind it. If your work ships as expertise rather than software, start at For Publishers.