Skip to main content
AgentMuxer tool purchases use your account’s credit balance. Model-provider charges are separate: AgentMuxer spending limits do not cap your OpenAI, Anthropic, or other model usage.

​
Who pays?

When you connect an agent and sign in, its AgentMuxer purchases use your account’s balance. Manage connected-agent controls in your dashboard.

​
Balance and spending limits

Applications default to no limit. Without an application limit, the application can spend your available account balance, subject to other account controls. No limit does not mean free execution. For example, an application with a 10lifetimelimitand10 lifetime limit and 3 already spent has at most $7 left, before accounting for calls on hold. Adding credits or rotating a key does not reset that application’s spending. In Applications → Manage, enter a positive limit or leave it blank for no limit. A new limit must cover money already spent and calls on hold. When a proposed purchase would exceed the available limit, AgentMuxer refuses it; you can increase the limit or remove it in the dashboard.

​
Tool permission and payment confirmation

These controls answer different questions:

Framework tool permission

May this agent call the tool? Configure this in your agent framework, such as OpenAI approvals or Claude’s tool permissions.

AgentMuxer payment confirmation

Does a paid purchase need a person to confirm it? Configure this in your account’s Overview.
Approving a tool in your framework does not override AgentMuxer’s balance, spending limits, or payment-confirmation setting. The SDK does not change these account settings.

​
Unattended applications

If your account requires human payment confirmation, a headless application may stop with an approval request instead of completing a paid call. Use an integration that supports that confirmation flow, or turn off payment confirmation in Overview when you want unattended purchases.
Payment confirmation is an account-wide setting. Changing it affects both application keys and your personal-agent connections. Application spending limits remain enforced.
Check compatibility for the confirmation capabilities of your integration.

​
Charges and uncertain outcomes

Free catalog search does not spend credits. AgentMuxer charges a paid call when the provider returns a successful HTTP response (2xx). A provider error or a failed provider request is not charged. A successful HTTP response does not guarantee that the answer is correct or useful for your task. An idempotent replay returns the existing purchase outcome without another execution or charge. Keep the original idempotency key and request when retrying a purchase.
A timeout in your agent does not prove that the provider call failed or that no purchase occurred. Check the existing invocation or retry with the original key; a new key can create a new purchase.

​
Review usage

Open Applications to see Spent and On hold, then select History for that application’s calls. Your dashboard also shows account usage and credit controls. For purchase terms, fees, and refunds, see the Terms of Service. For an unexpected charge, contact support with the invocation ID, without API keys.