Run hosted Hermes or OpenClaw agents with Platform Credits, your provider API keys, or supported customer-owned subscriptions. Keep model choice and account failover inside the native harness where they belong.
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 an eligible plan 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
Connect more than one account for a supported provider, give each one a clear name, and set its priority in Hermes or OpenClaw. The harness decides when an eligible fallback is needed; AI Agent Store only hosts the runtime and shows the result.
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. Subscription access depends on the provider plan and the native Hermes or OpenClaw authentication route. Agent Teams shows the native options that are actually available instead of treating every chat subscription like an API plan.
Yes, where the native harness supports that provider route. Name the accounts, set their priority, and let the harness use eligible quota-aware failover. The harness—not AI Agent Store—owns that selection logic.
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
Launch with Platform Credits, then connect eligible subscriptions or provider keys when you are ready to optimize cost and model choice.
