Managed models, voice, and proxies share the monthly plan’s weekly usage. Want to use your own API keys or supported AI subscriptions? Request access in Settings; approval is manual and does not change the payment plan.
Agent Teams hosting is still billed normally. Subscription availability and quota are controlled by each provider and native harness route.
Native account stack
Weekly included usage
Shown as a percentage of the week
Optional extra usage
Off until you turn it on
Own keys on request
Approval is manual
Optional extra usage
Off until you turn it on
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.
Included
Managed models, voice, and proxies share one weekly allowance, shown as a percentage. When it runs out, wait for the reset or turn on optional extra usage. The computer stays while the subscription is paid.
On request
Want to use your own API keys or supported AI subscriptions? Request access in Settings; approval is manual. Approval does not change the payment plan.
On request
Want to use your own API keys or supported AI subscriptions? Request access in Settings; approval is manual. Approval does not change the payment plan.
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 records the model so usage history can show the allowance used. Approved own-account work stays on that 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
Want to use your own API keys or supported AI subscriptions? Request access in Settings; approval is manual. Approval does not change the payment plan. Reseller customers do not have this option.
After approval, you can use supported subscriptions and API keys. 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.
Want to use your own API keys or supported AI subscriptions? Request access in Settings; approval is manual. Approval does not change the payment plan.
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 turn that request into extra usage.
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
The monthly plan includes weekly usage. Own API keys or supported AI subscriptions can be requested in Settings. Approval is manual and does not change the payment plan.
