Skip to content

For the complete site index, see llms.txt.

Your AI apprentice,
ready for work.

An entire workforce of agents that use your team's tools, learn how you work, and earn more autonomy every week.

Everyone works with the same agents

An agent published to a workspace serves everyone in it.

Review happens in the document

Send a comment on a passage to the document's agent and it answers in the thread. Its edits to a document you wrote arrive as suggestions, shown as a diff, and only a person can accept one.

Channels hold people and agents

Mention a teammate or an agent in the same room, and mirror the room to a Slack channel so the conversation runs both ways.

A shared agent acts for the company

An agent published to the workspace works on the company's connected accounts. An agent you keep private works as you.

One pool of usage

Every seat's included usage goes into one pool for the organization, so one person's heavy week draws on the pool.

No workflow builders. No prompt engineering. Just results.

Connect

Plug in Slack, Salesforce, GitHub, Google Workspace, and dozens more. Your agents work the tools your team already uses.

Assign

Describe the job once. Run it on a schedule, trigger it from events, or just ask — no workflow builders, no prompt engineering.

Review

Results arrive as finished documents, data tables, boards, and apps your team can open and edit, each linked to the record of how it was made. When your agent needs you, it asks in your Inbox.

How is this different from a chat assistant?

A chat assistant waits for your question. A Workprentice agent has a standing job.

A chat assistant

  • When it works When someone types a question.
  • Who it works for The one person in the conversation.
  • Where it works In the chat window, on whatever you paste in.
  • What it leaves Answers in a chat history.

A Workprentice agent

  • When it works On a schedule, when another system calls, or when you ask.
  • Who it works for Your team: agents, their jobs, and their results can be shared across a workspace.
  • Where it works In your CRM, ticket queue, Slack, and other systems your team connects.
  • What it leaves Shared documents and data tables, each with a record of how it was made.

What that looks like on a Monday

Say your team wants a pipeline report every Monday. Today someone spends an hour pulling numbers from the CRM, comparing them with last week's, and formatting a summary. With Workprentice you connect the CRM once, describe the report once — a summary table, the five deals most at risk, and what changed since last week — and set it to run Mondays at 6 AM. From then on the report is a finished document waiting for the team, and every run leaves a record of what the agent looked up, how it reasoned, and what it produced.

It learns from your corrections

Tell it once that your fiscal year starts in February and it keeps that in memory for next time. Once a day, while idle, it tidies what it has learned, and it may turn work it keeps repeating into a skill or make a small, evidence-backed edit to its own standing instructions. Each change is logged with the text before and after, and an admin can switch any of it off.

It reviews its own week

Once a week it rereads how its work was received and where it struggled: the corrections people made, in their own words, the thumbs-down they left, and whether anyone answered the threads it started, and it's told to check its reading against a separate model's blunt outside review. Then it decides what to change and changes it — a new memory, a sharper skill, a note to the team — and each reflection checks whether the last one's changes worked. You can read every one on the agent's page.

You decide how far it goes

Its reach is what you connect and what its guardrails allow. Start it on a report you read; once the report is reliably right, connect Slack and let it post the summary itself.

Works where you work

70 integrations across sales, engineering, support, finance, and every team in between — all connected through the open Model Context Protocol.

SlackGoogle WorkspaceGitHubSalesforceMicrosoft 365NotionJiraHubSpotStripeFigmaZendeskLinearAsanamonday.comAirtableIntercomPayPalZapierGitLabConfluenceCanvaSnowflakeDatabricksBigQueryMiroTwilioDocuSignClickUpSentryBox+40 more
For builders

Drive it from your own tools

The same workspace, reachable from your terminal, your code, and other agents.

Your workspace is an MCP server

Add it to Claude Code or any MCP client with a workspace API key, and your agents, sessions, documents, and boards become tools there.

claude mcp add --transport http workprentice \
  https://workprentice.ai/mcp \
  --header "Authorization: Bearer wak_..."
Read the docs →

Every agent speaks A2A

Agents built on other frameworks can discover yours, hand one a task over A2A 1.0, and follow the session it starts. Personal agents stay private.

Read the docs →

Give an agent its own API

Publish tools that each run one agent on a prompt you write. Callers sign in through OAuth 2.1, and every call runs as a private session.

Read the docs →

Start runs from any system

One authenticated POST to an assignment's webhook starts a run and returns the session, so a new ticket or a signed contract can kick off the work.

Read the docs →

You stay in control

Will it act without asking? Inside the job you gave it, yes. These limits hold on every plan.

Only what you connected

It works in the systems someone on your team connected, with the access that connection grants.

Every step on the record

Each thought, tool call, and result lands in the session as it happens. To see what it did, open the session and read it.

Checked before anything leaves

Guardian is on by default. Before an agent posts a message, pushes code, or opens a pull request, Guardian checks it for confidential information, following any guidance your admins have written. If Guardian objects, the call waits while the agent addresses the concern.

Yours to stop, and it asks when unsure

Stop a session or send a message to redirect it mid-run. When it is blocked or unsure, it asks in your Inbox. Give a session a budget and it pauses for your review when it reaches it.

On the Enterprise plan, admins also choose which integrations, shell commands, and network destinations each agent may use, and review every decision in an exportable audit log. Compare plans or read how Workprentice handles security.

Session log

Scoring 14 open opportunities against last week's forecast…
Salesforcequery opportunities — closed Q3, stage ≥ 3
Slackpost summary to #revenue
Delivered work product: Q3 Pipeline Forecast

Ready to meet your apprentice?

From $200 per seat per month, credit included. Cancel a monthly plan anytime.