# Base44 Superagent: What It Does, How It Spends Credits, Plans

> What a Base44 Superagent is, how it works across Gmail, Slack and your browser, how it spends credits, and which features need Builder or Enterprise.

_Source: https://professionalstoolkit.com/articles/base44-superagent — The Professional's Toolkit · updated November 2026_

---

A Base44 Superagent is a personal AI agent that works for you across your connected tools, your files, its own memory and every app in your workspace. You reach it in the Base44 chat or on WhatsApp, Telegram, iMessage, Slack or LINE, and it can browse the web, sit in on video meetings, run scheduled jobs and edit your Base44 apps once you approve. Every plan gets one, Free included, but it spends the same workspace credits you build with: on Free that is 25 message credits a month, at most 5 a day. **A phone number and webhooks start on Builder**, and more than one Superagent per person needs an Enterprise plan. Our read: switch it on for routine admin, and budget credits before you schedule anything.


**0.2** — Credits per minute of a Superagent phone call (Builder plan or higher), before any AI chat or background work.



- **~0.01 credit** — Per Superagent browser click or page read; about 0.03 per extraction
- **Builder+** — Plan needed for a Superagent phone number and webhooks
- **25 a month** — Free plan message credits a Superagent runs on, at most 5 a day


## A workspace assistant, not a chatbot bolted to an app

Base44 now runs three AI layers, and mixing them up causes most of the confusion. The AI chat builds and edits your apps. An in-app agent lives inside a single app, talks to that app's users and is paid from your integration credits, from about 3 credits a message on the Automatic model. A Superagent sits above both: it works for you, the builder, across your tools rather than inside one environment [1]. Base44 launched it in March 2026 and draws its own line against chatbots. A chatbot answers questions; a Superagent runs scheduled jobs, reacts to events and chains workflows.

The practical difference is who gets served. An in-app agent replies to a customer who opens your booking tool. A Superagent replies to you on WhatsApp with a summary of yesterday's sign-ups, because it can answer questions about any app in the workspace, while messages from anyone other than the owner stay closed. If all you need is a question-answering box for visitors, Base44 itself says the plain chatbot is the simpler build.

Privacy works at the workspace level. Owners and admins can read, message, and see the memory and files of every Superagent in the workspace, so a shared workspace is not a private notebook. On every plan except Enterprise, Base44 can also use workspace data to train AI models, with no opt-out setting. Deleted Superagents can be restored for 30 days, though their integrations are disconnected at deletion and never come back.

## Getting one running: channels, connectors and guardrails

You can start a Superagent in the browser, or by scanning a QR code in WhatsApp, Telegram or iMessage; on LINE you simply message it, and LINE works only in select regions. A new Base44 account gets starter credits to run one without entering payment details, and Superagents do not count toward the Free plan's 5-app limit. *Trying one costs no app slot.* The order below leaves the riskiest permissions for last:

1. **Pick the channel.** The web chat suits long tasks and voice; the messaging apps suit quick requests. Mentioning it in Slack works on every Slack plan, free ones included.
2. **Choose a memory mode.** Separated memory, shared memory or no memory; what it remembers can be cleared in one step.
3. **Connect tools read-only first (Builder or higher).** On the Builder plan or higher, Gmail, Google Calendar, Drive, Docs, HubSpot and Notion can be attached with read-only access, so it can look things up without sending, editing or deleting. Your own MCP server can be connected too, also from Builder up.
4. **Set the security rules.** Require approval before it updates or deletes data, let it flag pasted secrets, and add Connector Rules per service, such as read-only email.
5. **Add skills.** Only workspace owners and admins can switch skills on from the catalog, write them in chat or upload them as a file.

Check plan gates before you design around a tool. Base44's connector pages list the Google and Slack connectors on the Builder plan or higher, and a shared connector can be limited to read-only access. Our [Base44 integrations guide](/articles/base44-integrations) maps the connector catalog and its gates in full.


> 💡 **Connect tools read-only first:** On the Builder plan or higher (connectors need Builder), Gmail, Google Calendar, Drive, Docs, HubSpot and Notion can be attached to a Superagent with read-only access, so it can look things up without sending, editing or deleting anything.


## Letting it act: browser, meetings, goals and phone calls

By default a Superagent browses in its own secure cloud browser, which needs no installation but is signed in to none of your accounts and reaches public sites only, never localhost or private addresses. For sites where you are already logged in, the Chrome-only Superagent by Base44 extension lets it fill in forms and finish tasks there. Only one session controls the browser at a time. **Before any button that charges money, it stops and asks.** Base44's changelog adds that payment goes through only when the button, amount and site match what you approved.

Meetings need a connected Google or Outlook calendar. The Superagent joins any meeting with a video link, such as Google Meet or Zoom, as a notetaker, then saves notes and action items to its notes library and emails them to you. Meetings without a video link do not appear at all. Notes are documents you both edit, while memory stays behind the scenes. A note can be shared to the web for anyone with the link, and since notes can pull personal details from email and calendar, review one before sharing it.

For longer jobs, goal mode breaks the work into tasks that sub-agents handle across runs; goals cannot be set from voice mode yet. Sub-agents running in parallel can use more credits, and their results stay in the chat unless you ask for them to be saved. A single turn can run up to 20 minutes before timing out. Voice mode adds camera and screen sharing, the latter on desktop browsers only, and Base44 keeps text transcripts but no recordings.

On Builder and above it can also get a dedicated US phone number, place outbound calls, press keys through phone menus and answer up to 20 trusted callers. Consent from the people it calls is your job. It can change your Base44 apps from chat after asking and run existing backend functions (which need the Builder plan or higher), but it cannot publish an app, connect a domain or touch your plan or billing. On a Wix site it works with one site at a time and, by default, confirms before changing anything.

## Workflows that keep running while you are away

Superagent workflows are either scheduled or triggered by an event, such as an email arriving or data changing, and you create them by describing them in chat. In a Slack channel it can post scheduled results and reply in the thread when mentioned. Every run spends message credits, exactly like chatting. A workflow that fails several runs in a row pauses itself, though runs started with Run Now do not count. On Builder or higher you can also send signed webhooks when a message is created or completed, up to 5 per Superagent; after a downgrade to Free they stop until you return to Builder.

The credit edge is where workflows go wrong. When credits run out, they simply cannot run: they are not paused, and missed runs never catch up later. On the Free plan, a Superagent's scheduled runs skip until the daily or monthly reset. Out-of-credits notices go out only on paid plans, and only when the workspace's monthly pool is empty, not when one member hits a limit. *A silent skip is the real risk.* After the first week, open the Credit usage tab in the agent's settings, which shows the plan summary and a rolling session meter.


> ⚠ **Missed workflow runs never catch up:** When workspace credits run out, Superagent workflows cannot run and missed runs are not run later; out-of-credits notices go out only on paid plans.


## Where the credits go

A Superagent draws on two pools. Message credits pay for processing messages and running workflows; integration credits pay for actions such as image generation, file processing, uploads and download links [2]. Credits belong to the workspace, so every invited collaborator draws on the same pool, and AI usage from WhatsApp or Telegram group chats is billed to the agent's owner. Unused credits expire at each monthly reset and do not roll over (the only exception is a one-cycle carryover when you upgrade from a monthly plan to a higher monthly plan); see our [Base44 pricing guide](/articles/base44-pricing).

Browser work is metered per step: about 0.01 credit for each click or page read and about 0.03 for each data extraction, with failed attempts free, all as Base44's estimates [3]. By our arithmetic, 1,000 clicks or page reads come to about 10 credits and 100 extractions to about 3. The per-step browser charges are small; the AI chat and background work around each step can use more credits on top. Phone calls run 0.2 credits per minute, so a 30-minute call uses about 6 credits before any chat or background work it triggers.

Scale those rates against the plan. Free allows 25 message credits a month, at most 5 a day, which rules out a busy schedule. Builder grants 250 message credits a month, an average of about 8 a day over a 30-day month by our arithmetic (a pace, not a daily limit), shared with everything else the workspace builds. Builder costs $40 per month billed annually or $50 per month billed monthly, per workspace. Base44 shows the exact cost only after each run, so measure a week of real use before adding schedules.


> 💡 **Ask sub-agents to save results:** Work done by Superagent sub-agents stays in the chat unless you ask the Superagent to save it, so request a note or a file at the end of a goal.


## What each plan adds to a Superagent

| Superagent feature | Lowest plan |
|---|---|
| One Superagent on the workspace's shared credits | Free |
| Dedicated US phone number, up to 20 trusted callers | Builder |
| Signed webhooks, up to 5 per Superagent | Builder |
| Backup and restore of Superagent data | Elite and Enterprise plans |
| Turn Superagents off workspace-wide, control template links | Enterprise (Business or Enterprise) |
| More than one Superagent per person | An Enterprise plan |

The last two rows sit in Base44's Enterprise offering, which the help center splits into a self-serve Business plan and a sales-led Enterprise plan; neither price is published. The workspace-wide switch and the template-link control are listed for both, and more than one Superagent per person comes with an Enterprise plan. Outside Enterprise plans, the documentation suggests one Superagent used as a single assistant with separate conversations, and Viewers cannot create one. If you cancel a paid plan, the Superagent keeps working and its data is not deleted, but its phone number is released for good once the plan drops below Builder.


## FAQ

**Which AI model does a Base44 Superagent use?**

The chat model can be left on Automatic, and a separate model can be chosen for scheduled and background automations. Base44's changelog says Superagents have defaulted to GLM 5.2 since August 2026.

**Can I share my Superagent with someone else?**

Yes. You can share it with collaborators, or create a template link that lets anyone copy it, choosing whether skills, memory, files and tasks go with it; connectors are never included, so whoever copies it reconnects their own accounts.

**Can I use a Superagent from my phone?**

Yes, through WhatsApp, Telegram, iMessage, Slack or LINE, or in the Base44 app for iOS and Android. Up to 5 messages can queue while it is busy.

**Can a Superagent move to another workspace?**

Yes, a Superagent can be moved to another workspace together with its conversation history, but the move cannot be undone, and it cannot be the only Superagent in its workspace.




> ⚠ **Admins can read every Superagent:** Workspace owners and admins can read the conversations, memory and files of every Superagent in the workspace.

## The bottom line

A Base44 Superagent earns its place when your work already lives in Gmail, a calendar, Slack and a few Base44 apps, and you want one assistant that reads across them, takes notes and runs routine jobs. Start small, with read-only access and an approval rule for edits, then watch the Credit usage tab. Move to Builder when you need the phone number, webhooks or the Google and Slack connectors, and plan for scheduled runs that skip silently when the pool runs dry.



## Sources

[1] Base44 docs: Using Superagents — https://docs.base44.com/Getting-Started/superagent (2026-11)
[2] Base44 docs: Customizing your Superagent — https://docs.base44.com/superagents/customizing-your-superagent (2026-11)
[3] Base44 docs: Browsing with your Superagent — https://docs.base44.com/superagents/browser-control (2026-11)
[4] Base44 pricing page — https://base44.com/pricing
[5] Base44 documentation — https://docs.base44.com/Account-and-billing/Credits
[6] Base44 Terms of Service — https://base44.com/about-us/legal/terms-of-service
[7] Base44 Privacy Policy — https://base44.com/about-us/legal/privacy-policy