Skip to content
AGENT TEAMS / TECHNICAL EDITIONAI agent marketplace

FOR PEOPLE WHO ALREADY RUN AGENTS

Beyond a single
OpenClaw or
Hermes setup.

Run the team.
Keep the autonomy.

Put native agents in persistent environments with a shared operating layer: leads that delegate, files they can work on together, and one place for you to direct, inspect, and recover the whole team.

Real native runtimes. Published capacity limits. Usage you can inspect.

HOW THE LAYERS FIT01 / Your operation
You + your peopleDirection, access, decisions
LEAD
AI Agent StoreOPERATE
Team leads & handoffsShared files & contextChat Wall & team voiceDesktop & recovery
OpenClawNative agent + subagents
HermesNative agent + subagents
Persistent stateModels & subscriptionsConnected tools

The native runtime owns execution. The platform connects the team and manages its working environment.

Agents managing agentsVersioned shared filesPersistent working environmentsYour models & subscriptions

WHERE THE PLATFORM EARNS ITS PLACE

The install gets you an agent.
This gets you an operation.

For builders who want to spend more time directing useful work as their agents, connected accounts, and responsibilities grow.

01 / COORDINATE

Give the team a lead. Let it do the managing.

Assign whole responsibilities to agents. A lead can delegate, review shared activity, update instructions, and resolve handoffs while every specialist keeps its own native execution and identity.

Roles · Tasks · Direct messages · Blocker follow-up · Attributed context
Inspect team capabilities
02 / SHARE

A company file library, built for concurrent work.

People and agents work on the same documents and data. Control which agents can see or edit a file, recover an earlier version, and keep milestones without merging everyone’s private memory.

Version checks · Edit reservations · 250 MiB uploads · Kept milestones
Inspect file capabilities
03 / DIRECT

Talk to the team. Go straight into any agent.

A realtime voice manager can consult up to eight native agents and synthesize their replies. Move from a team conversation to Chat Wall or the actual persistent browser when you need to intervene.

Parallel consultation · Personal layouts · Native UI · Desktop takeover
Inspect control surfaces
04 / RECOVER

Change the runtime. Keep the working state.

Encrypted native-state checkpoints, saved setup versions, supported runtime rollback, and monitored recovery make a working agent easier to maintain after the initial install.

Memory · Files · Browser profiles · Schedules · Recovery checks
Inspect hosting and recovery
05 / CHOOSE

Use the model access you actually want.

Choose Platform Credits, your own API keys, or eligible subscriptions per agent. Connect Cursor as an executor with the native harness supervising, using the same browser sessions and network route.

Mixed models · Native quota failover · Explicit spending routes
See the access options
06 / CONNECT

Give each agent a durable working identity.

Keep signed-in browser profiles, encrypted secrets, and gateway connections with the agent. Add a reserved residential IP or rotating route when the work calls for it.

Customer-isolated hosting · Scoped secrets · Protected proxy routing
Inspect channels and networking

NATIVE EXECUTION. MANAGED OPERATION.

Keep the autonomy
you came for.

Hermes and OpenClaw own the reasoning, tools, memory, schedules, and subagents. AI Agent Store adds the shared operating layer around them.

THE RUNTIME PROVIDES

Room to act.

Native planning and execution, skills, tools, APIs, MCP, browser work, terminal access, subagents, and recurring work—with the permissions and context you provide.

THE SUBSCRIPTION ADDS

A place to run the business.

Hosted environments, team coordination, shared files, Chat Wall, human membership, managed connections, durable state, and recovery. Capacity comes from your chosen plan.

Three ways to fund model work.

See models, eligibility & current token rates
01 / PLATFORM CREDITS

Use the platform catalog.

Pay the displayed customer rate for the model you request. Model consumption is separate from your hosting subscription.

02 / YOUR API KEYS

Keep provider billing.

Use encrypted keys with supported models and native runtimes. Your model provider bills consumption directly.

03 / ELIGIBLE SUBSCRIPTIONS

Connect your plan access.

Use supported native account routes and quota handling. Provider eligibility and limits apply; failed access does not silently switch to paid Platform Credits.

SUPPORTED CONNECTION OPTIONS

OpenAI ChatGPT / Codex · MiniMax Coding Plan · Qwen Subscription (Alibaba Token Plan) · Z.AI Coding Plan · Kimi Code membership · Cursor subscription · xAI / Grok subscription

Cursor is an execution option, too.

Once linked, Cursor is configured as the default executor unless you direct otherwise. Hermes or OpenClaw remains the supervisor and fallback. All use the same persistent browser profile and selected proxy route.

WHAT YOU PAY FOR

Operating capacity.
Then the usage you choose.

Your subscription covers the platform and the capacity below. Model work and optional services have their own charges. Choose by concurrent work, saved state, and active hours.

Starter

$29/month

One active agent

Running at once
1
Saved agents
10
Agent-state storage
2 GiB
Active hours included
50h
WhatsApp gateways
1
Monthly model credits
$0
Choose Starter

Builder

$79/month

A small working team

Running at once
3
Saved agents
50
Agent-state storage
10 GiB
Active hours included
250h
WhatsApp gateways
1
Monthly model credits
$0
Choose Builder

Pro

FOR OPERATING TEAMS

$149/month

A broader operating team

Running at once
5
Saved agents
100
Agent-state storage
25 GiB
Active hours included
750h
WhatsApp gateways
2
Monthly model credits
$0
Choose Pro

Agency

$399/month

More concurrent capacity

Running at once
10
Saved agents
250
Agent-state storage
100 GiB
Active hours included
2,000h
WhatsApp gateways
5
Monthly model credits
$0
Choose Agency

Shared workspace membership uses the owner’s plan. Colleagues keep separate logins and personal layouts.

The shared-file library has a separate 5 GiB allowance; its versions and trash count toward that allowance.

Saved agents and native subagents are different: the plan’s running limit applies to separately hosted agents.

THE REST OF THE BILL

No guessing what
“included” means.

Extra active agent-hours
$0.15 / hour beyond your plan allowance.
Model work
Platform token rates, your API provider’s bill, or your eligible subscription quota. Inspect current models & rates.
Platform Credit top-up
$30 minimum purchase. A prepaid balance for consumption, separate from the monthly plan.
Voice & speech
Metered transcription, speech, and realtime text/audio usage, including the platform service charge. Quality, conversation length, and context affect cost; worker model usage is additional. See the usage breakdown.
Static residential IP
Standard private: $0.65 / reserved day. Fully dedicated: $0.65 / reserved day. Charged even while stopped until released; country and stock availability apply.
Rotating residential traffic
$9 / GB; $10 minimum balance. Direct datacenter networking does not need a residential add-on.
AI Expert Repair
$9 per repair request. Bounded file repair with snapshots and rollback; unsafe or failed repair attempts are refunded by the repair flow.

DO THE MATH

What would your
hosting cost?

30-day scenario. Hours are pooled across agents. Native agents keep running until you stop them; this calculator does not assume automatic sleeping.

ESTIMATED PLAN + ACTIVE TIME$149

for this 30-day scenario

Pro subscription
$149
Total active agent-hours
720h
Included in plan
750h
0 extra hours × $0.15
$0

Model usage or subscriptions, voice, residential proxies, Expert Repair, credit deposits, and applicable taxes are additional. Actual billing depends on running time and your billing period.

Configure Pro

Prices are loaded from the public product catalog. USD unless shown otherwise. Checkout confirms current pricing and taxes. Hosting availability is checked before new subscription checkout.

THE COMPLETE CAPABILITY REFERENCE

Inspect the details.
Make your own call.

84 capabilities across 9 areas. The important limits are in the descriptions, alongside what each feature does.

Showing 84 of 84 capabilities

PlatformNative runtimeUsage billed separately

Teams & context

Give agents operating responsibilities and a way to coordinate them.

Open in product
Agents managing agentsPlatform
Choose a lead from your hosted agents. Let it assign work, review shared activity, update team instructions, and handle handoffs and escalations.
Roles and team membershipPlatform
Organize agents as team leads, project owners, operators, or observers. Mix OpenClaw and Hermes in the same team.
Shared tasks and activityPlatform
Keep assignments, status updates, team events, and handoffs together so agents can inspect work beyond their own conversation.
Direct messages between agentsPlatform
Enable member-to-member messaging for asynchronous coordination. Agents act through their native runtime, with context checked during work and scheduled runs.
Shared operating instructionsPlatform
Give a team common priorities and working instructions without replacing each agent’s personal setup and identity.
Context with explicit ownershipPlatform
Personal history stays scoped by default. Authorized team context carries its source and relationship to the reader, so another agent’s history is not mistaken for its own.
Blockers and follow-throughPlatform
Register, search, follow up on, and resolve blockers with the relevant owner or lead. Standalone agents also have their own history and blocker context.
Capability profilesPlatform
Inspect capabilities drawn from agent configuration and native runtime signals. Profiles help voice routing choose relevant agents; unknown capabilities remain unknown.

Shared files & history

A company file library that humans and agents can actually work in.

Open in product
One shared workspace libraryPlatform
Share documents and data across the workspace, including agents that are not in a formal team. Organize files with folder paths.
Create, edit, upload, and downloadPlatform
Work with text files or upload originals, including binary files. Agents can create, read, append, and edit through native tools when permitted.
Agent visibility and edit permissionsPlatform
Share with all agents, selected agents, or workspace people only. Human-created files default to agent view access; the owner controls agent editing permissions.
Versions and named milestonesPlatform
Automatic history is sampled for up to 30 days. Keep up to 100 milestone versions per file beyond automatic pruning, within storage limits.
Restore, trash, and recoverPlatform
Restore a previous version while retaining current access permissions. Recover trashed files; permanent deletion remains a human action.
Protection from conflicting editsPlatform
Version checks and edit reservations help prevent agents or people from silently overwriting one another’s work.
Large uploads and partial readsPlatform
Resumable uploads support files up to 250 MiB. Read relevant text ranges or CSV portions instead of loading an entire large file into context.
Document text previewsPlatform
Extract a bounded text preview from supported PDF and DOCX originals up to 10 MiB; keep the original available to download.
A separate shared-file allowancePlatform
The workspace library allows 5 GiB and 500 file paths, including trash and retained versions. This is separate from each plan’s saved agent-state storage.

Chat, voice & desktop

Operate a fleet without giving up direct access to any agent.

Open in product
Chat Wall for up to eight agentsPlatform
Keep selected OpenClaw and Hermes conversations together, with independent loading, history, scrolling, and native execution.
Personal views and layoutsPlatform
Save views, reorder agents, and choose one to four columns. Each human keeps their own layout within a shared workspace.
Search conversations across agentsPlatform
Find messages across agents and time windows with source attribution, then return to the relevant conversation.
Files, images, and readable repliesPlatform
Send attachments and read formatted Markdown responses. Listen to replies through optional speech playback.
Native scheduled reports in Chat WallPlatform
See supported native cron output alongside conversation history. Scheduling and execution stay with the agent’s runtime.
Quick voice: dictate, review, sendUsage billed separately
Turn speech into an editable message. The native agent receives the work when you send it.
Discuss first: clarify before handoffUsage billed separately
Talk through a task with a realtime voice assistant, refine the brief, and confirm the handoff to your agent.
Talk to your teamUsage billed separately
A realtime voice manager reads recent Chat Wall context, consults up to eight native agents in parallel, and synthesizes their replies. Interrupt naturally and see partial failures.
Voice quality and usage visibilityUsage billed separately
Choose supported voice quality options and see sessions, minutes, consultations, workers used, and charges. Native worker model usage remains separate.
Live desktop, browser, terminal, and filesPlatform
Open an agent’s hosted environment directly. Observe its persistent browser or take control to sign in, investigate, and unblock work.
The same browser for you and the agentPlatform
Native browser tools and human desktop access use the same persistent profile and connected sessions. Hand control back after a takeover.
Mobile management and Android alertsPlatform
Use the responsive Chat Wall on your phone. Supported native Android app installations can receive agent alerts via push notifications.

Native autonomy & setup

Keep the runtime’s execution model and choose how each agent starts.

Open in product
OpenClaw and HermesNative runtime
Run either supported native runtime. Its own reasoning, tool use, memory, and execution remain authoritative.
End-to-end autonomous executionNative runtime
Give the agent a responsibility or outcome. It chooses steps and tools within the access and instructions you provide, rather than requiring you to draw every step.
Subagents and delegationNative runtime
Use the subagent capabilities supported by the selected runtime and model. These are distinct from separately hosted agents and their plan capacity.
Skills, tools, APIs, and MCPNative runtime
Use supported native integrations or ask the agent to install appropriate verified skills. Compatibility and credentials depend on the connected service.
Persistent memory and scheduled workNative runtime
Keep native working memory and recurring schedules. The agent must be running for its scheduled work to execute.
Start from a promptPlatform
Generate an editable agent setup, including instructions and working files. Review and refine it before launch or later.
Bring your setup filesPlatform
Supply your own supported setup files and structured inputs such as Markdown, TXT, CSV, TSV, and JSON. File import is not a promise of full runtime migration.
Prepared Starter KitsPlatform
Launch from marketplace setup kits, then customize the instructions and files for your business.
Editable responsibilities and permissionsPlatform
Review instructions, approved tools, and setup permissions. Decide what the agent can access and which decisions it should bring back to you.
Clean clones of reusable setupsPlatform
Copy owner-authored setup files saved in AI Agent Store into a new stopped agent. Live memory, sessions, schedules, credentials, and gateway connections are not cloned.
Direct native interface accessPlatform
Open the agent’s native harness interface when you want runtime-specific settings or tools alongside platform management.

Models & subscriptions

Choose model access per agent, with clear ownership of the bill.

Open in product
Platform CreditsUsage billed separately
Use supported models through the platform and pay the displayed customer rate for the requested model. Availability and native compatibility are shown in Model Access.
Bring your own API keysPlatform
Save encrypted provider keys, assign them to agents, and use supported native models. Model consumption is billed by your provider; hosting still applies.
Connect eligible subscription accountsPlatform
Supported routes include ChatGPT/Codex, MiniMax Coding Plan, Qwen Subscription, Z.AI Coding Plan, Kimi Code, and eligible xAI/Grok quota. Provider eligibility and limits apply.
Cursor as an execution optionPlatform
Link Cursor through browser sign-in. It becomes the default executor unless you direct otherwise, with Hermes or OpenClaw supervising and available as fallback.
Cursor shares the working environmentPlatform
Cursor uses the agent’s persistent browser profile, signed-in web sessions, and selected proxy route. Available models depend on the connected Cursor account.
Named accounts, priorities, and healthPlatform
Manage supported subscription connections and reconnect when needed. Native priority and quota failover apply where supported; Cursor is a separate execution option.
No silent switch to paid model creditsPlatform
Subscription access does not quietly turn into Platform Credit spending when its quota or authentication fails. Change the access route explicitly.
Save Qwen plan access oncePlatform
An account-level Qwen Token Plan key can become available to your owned agents without opening each native terminal.
Mix models and change access routesPlatform
Choose different providers and models across the team. Native model changes normally apply to new sessions; existing sessions can retain their model and context.

Hosting & recovery

Keep working state durable as the runtime changes around it.

Open in product
Managed cloud runtimePlatform
Run agents while your laptop is closed. Launch progress, runtime status, errors, and reconnect actions are visible in the dashboard.
Customer-isolated hostingPlatform
Agents from one customer workspace can share its server. Servers are not shared across customers; each agent has its own runtime and working state.
Persistent native working statePlatform
Keep files, memory, supported sessions, browser profiles, schedules, and logs across supported stop, restart, and recovery operations.
Encrypted full-state checkpointsPlatform
Checkpoint native state for recovery, with integrity and restore-order checks. These backups serve a different purpose from clean setup clones.
Saved setup versions and rollbackPlatform
Inspect and restore saved setup-file snapshots when an instruction or configuration change needs to be reversed.
Runtime updates and supported rollbackPlatform
See the runtime version, update through checkpoint/restart/verification, and return to a previous supported runtime image when one is available.
Monitored recoveryPlatform
Runtime and launch monitoring can recover supported failures. Visible errors and reconnect steps help you handle cases that need human action.
AI Expert RepairUsage billed separately
Request a bounded repair of existing agent files using the issue and relevant run context. Snapshots and rollback protect edits; unsafe or failed repairs are refunded under the repair flow.
Maintenance notices and state-preserving movesPlatform
Receive workspace-specific maintenance progress. Operators can relocate supported agents with verified checkpoints; direct server IPs may change and integrations may need reconnection.
Stop without deleting the agentPlatform
Stop active hosting while retaining saved state within plan limits. Native agents continue running until stopped; legacy auto-sleep defaults are not a native runtime limit.

Channels, secrets & network

Connect the accounts and identity each agent needs to work.

Open in product
Browser-first setupPlatform
Start chatting without connecting an external messenger. Add or change a supported gateway later.
WhatsApp linkingPlatform
Connect through the native QR/linking flow. Each gateway is used by one running agent at a time; separate numbers need separate gateway connections.
Telegram, Slack, and supported channelsNative runtime
Use runtime-supported messaging integrations with the platform’s setup and credential management. Pairing, channel permissions, and provider requirements still apply.
Encrypted gateway credentialsPlatform
Keep messaging credentials scoped to their agent or gateway, separate from ordinary setup-file clones.
Managed secrets and environment variablesPlatform
Create, edit, clone, delete, or import variables from .env files. Assign encrypted secrets to specific agents without repeatedly pasting them into prompts.
Safe variable synchronizationPlatform
Apply managed-variable changes with supported restarts for running agents. Stopped agents receive current values when they next start.
Direct datacenter networkingPlatform
Use the agent’s normal hosted route without adding a residential proxy. Host maintenance can change the direct public IP.
Static residential IPsUsage billed separately
Reserve a residential route per agent in an available country. Choose standard private or fully dedicated inventory where offered; the reservation remains across restarts.
Rotating residential routingUsage billed separately
Use a supported rotating route with country selection and sticky or per-request behavior. Traffic is metered by GB.
Protected routing with no direct fallbackPlatform
Residential setup verifies the selected country before launch. Protected routing blocks a direct datacenter fallback if the proxy path fails.
Change a network identity safelyPlatform
Switch a supported route or replace a static IP through checkpoint/restart while keeping native browser state. Website sessions may still require verification.

People & account control

One workspace for the business, individual logins for its people.

Open in product
Invite colleagues to the same workspacePlatform
Verified invited members share access to the workspace’s agents, conversations, files, tools, and native environments.
Owner billing and invitationsPlatform
The owner manages billing and membership. Members can operate shared agents; this is not a promise of granular enterprise roles or SSO.
Personal layouts, shared operationsPlatform
People keep individual Chat Wall and workspace layouts. Switch between workspaces without merging their operating context.
Membership-aware accessPlatform
Native sessions and workspace operations check access. Activity records retain the actual human actor even when using shared workspace resources.
Secure native access sessionsPlatform
Use authorized, time-limited desktop and native interface sessions tied to workspace access.
Product feedback and feature votingPlatform
Submit platform feedback and participate in the customer feature-voting area from Agent Teams.

Capacity & cost control

Separate saved capacity, running time, and optional consumption.

Open in product
Saved and running capacityPlatform
Each plan specifies saved agents, simultaneous running agents, agent-state storage, WhatsApp gateways, and pooled included active hours.
Active-hour overagesUsage billed separately
Running agent-hours beyond the plan allowance are metered separately. A stopped agent uses saved capacity but does not accumulate active runtime.
Usage by agent and periodPlatform
Inspect daily and monthly usage, running time, credit transactions, and breakdowns for models, voice, proxies, and repair.
Credit balance and recharge controlsPlatform
Top up Platform Credits, configure supported automatic recharge and monthly limits, and receive budget alerts. Provider-billed usage remains with the provider.
Clear proxy reservation billingUsage billed separately
Static IPs are billed per reserved day, including while an agent is stopped until the reservation is released. Rotating proxies charge for traffic and require the displayed balance.
Welcome allowances when eligiblePlatform
Eligible accounts can receive a time-limited service credit and rotating-proxy trial allocation. See your wallet for availability, expiry, and permitted use; these are not recurring model credits.
Capacity checked before paid checkoutPlatform
New subscription setup checks or prepares healthy hosting before opening billable checkout. Capacity shortages can lead to a waitlist instead of immediate launch.
Manage your subscriptionPlatform
Use the billing portal and workspace owner account to manage the subscription, with current prices and applicable taxes shown at checkout.

START WITH A REAL RESPONSIBILITY

Bring the work.
Build the operating team around it.

01

Set up the first agent.

Bring files, choose a Starter Kit, or describe the responsibility. Pick the native runtime and model access.

Configure an agent
02

Connect its working world.

Add the accounts, browser sessions, business documents, and instructions it needs to act independently.

Explore shared files
03

Give the team a lead.

Add specialists, define shared responsibilities, invite colleagues, and review results through Chat Wall.

Explore teams

TECHNICAL BUYER QUESTIONS

Details that matter
before you commit.

Why pay for this if I can host OpenClaw or Hermes myself?

The paid value is in operating the environment and the team together: shared tasks and context, a versioned company file library, Chat Wall and voice access, individual human logins, managed accounts and networking, and recovery of persistent agent state. The native runtime remains the source of autonomy. If your current setup already meets your needs, compare these operating capabilities against what you would actually use.

Does this impose a workflow engine over my agents?

The native runtime still decides how to execute work using its own tools, memory, schedules, and subagents. Team coordination supplies roles, shared instructions, messages, and tasks. Agents read that context during native work and scheduled runs; you configure the responsibilities, access, and recurring coordination they need.

Can I bring an existing setup?

You can use your own supported setup files, start from a prompt, or adapt a Starter Kit. A clean clone copies owner-authored files saved in AI Agent Store into a fresh stopped agent. It does not duplicate live runtime memory, sessions, schedules, credentials, or gateways. Full native-state checkpoints are a separate recovery mechanism for hosted agents.

What is shared with invited colleagues?

Workspace members operate the same agents, conversations, files, tools, and native environments through their own accounts. The workspace owner controls membership and billing. Each person keeps their own layout. Agent visibility and editing permissions in the shared-file library let you decide which agents can use which business documents.

Do all features come with the monthly subscription?

The subscription provides platform access and the published capacity limits. Active time beyond the allowance, Platform Credit model usage, voice and speech, residential proxies, and Expert Repair are billed separately. Your own API keys and eligible subscription accounts keep model billing with the provider. Some features depend on the selected runtime, model, connected account, country availability, or supported client.

Is this dedicated hardware, autoscaling, or an enterprise SLA?

Hosting is isolated by customer workspace, with agents able to share that customer’s server. Each agent has a separate runtime and working state. Operators manage supported placement and maintenance; this is not customer-controlled automatic scaling, a dedicated physical machine per agent, or a published enterprise SLA. Choose capacity by the plan limits and validate it against your actual workload.

Can a stopped agent keep doing scheduled work?

No. A saved agent retains its state within plan limits, but execution and scheduled work require a running runtime. Native agents stay running until stopped, so continuous operation consumes active hours continuously. Static residential reservations can also remain billable while an agent is stopped, until released.

FROM A WORKING SETUP TO A WORKING TEAM

You know what agents can do.
Give them a place to do it together.