Run hosted Hermes or OpenClaw agents with your existing subscriptions or API keys—no Platform Credits needed for that AI work. Or start easily with Platform Credits and switch anytime.
Agent Teams hosting is still billed normally. Subscription availability and quota are controlled by each provider and native harness route.
Native account stack
Primary subscription
Use existing eligible quota first
Second named account
Native failover when supported
Provider API key
Direct provider billing when selected
Platform Credits
Simple prepaid access when selected
Subscription sign-in stays in the native harness. AI Agent Store does not store those OAuth tokens.
One agent, three payment routes
Start fast, optimize costs later, and keep different agents on different providers without rewriting their setup files.
Fastest start
Launch without opening a separate provider account. Usage is deducted from your prepaid AI Agent Store balance at the published model rate.
Direct provider billing
Save provider keys once, assign them to the agents that need them, and let the native harness discover the models available to that account.
Use subscriptions you already have
Sign in from the native Hermes or OpenClaw interface when the provider and harness support subscription access. AI Agent Store does not collect the OAuth tokens.
Multiple accounts, native control
Use different subscriptions and API keys across your agents at the same time. Connect multiple accounts for supported providers, name them, and set priorities in Hermes or OpenClaw so quota-aware failover can use the next available account.
Currently supported native routes
The list can grow as Hermes, OpenClaw, and providers add compatible native authentication routes.
Switch models at any time
Select another available model in the native Hermes or OpenClaw UI. New native sessions use the new choice without restarting the whole agent, while existing sessions keep their original context and model.
Agent Teams observes the actual model requested for accurate Platform Credit billing and status. Native subscription or BYOK usage remains with that provider account.
Native software updates
Agent Teams checkpoints the agent, applies the latest supported runtime image, restarts it, and verifies that the native interface comes back. When a previous version is available, you keep a rollback path.
Clear answers before you connect
No. AI work through your own accounts uses your subscription quota or direct provider billing. Platform Credits are an optional convenience for AI access and pay for optional platform services such as voice, residential IPs, and Expert Repair. Hosting is covered by your Agent Teams plan.
Yes. Use multiple subscriptions and API keys across your agents at the same time. For supported routes, name accounts and set priorities so quota-aware failover can use another available account. Each account keeps its own quota and billing.
Yes. Start with Platform Credits or connect your own accounts immediately, then change AI access anytime. If you selected extra monthly credit funding, choose a plan without that extra funding to stop future credit purchases; changing AI access alone does not change your subscription.
Normally, no. The new model applies to new native sessions. An existing conversation can keep the model it started with, so begin a new session when you want the switch to take effect immediately.
If you configured another eligible account, the native harness can move to the next account according to its priority and failover behavior. Agent Teams does not silently convert the request into paid Platform Credits.
No. Hermes and OpenClaw keep control of conversation context, planning, tools, schedules, and subagents. AI Agent Store provides hosting, secure access, checkpoints, communications, and billing visibility.
Start with the access you prefer
Start with your own subscriptions or API keys, or use Platform Credits for convenience. Switch AI access anytime as your team, quotas, and model preferences change.
