Balanced across subscriptions
The default. Spreads work over every subscription that has room. API accounts follow the API usage setting.
Start free trialFree trial When you create a project, you choose how it draws on your subscriptions and API accounts. agnte follows that strategy for every task.
waitingAPI spend $0.00Token strategies in agnte set how a project uses your accounts. Balanced, the default, spreads work across every subscription with room. In priority order uses accounts one by one in your order. Subscriptions first, API only as overflow touches an API account only when every subscription is full. Cheapest capable account picks the lowest-cost account that can run the task. API accounts follow a separate API usage setting (overflow, light work or never), and the weekly reserve you set in Accounts is always kept for you.
The default. Spreads work over every subscription that has room. API accounts follow the API usage setting.
Uses your accounts one by one in the order you set, moving on only at a limit or your reserve.
Uses subscriptions until every one is full, then overflows to API. Saves API spend.
Picks the lowest-cost account that can run the task. Subscriptions cost nothing extra; APIs by price.
Choose when API accounts are used at all: as overflow, for light work only, or never.
The reserve set in Accounts is never spent by the project, so your own sessions keep quota.
Source: Live agnte database, 2026-10-12.
Balanced is the default. Subscriptions first saves API spend, and cheapest capable account keeps cost lowest when you also use paid APIs.
No. In balanced mode, API accounts follow the API usage setting: overflow, light work or never.
No. The weekly reserve you set in Accounts stays available for you.
Yes, per project. New tasks follow the new strategy.
We do not use tracking or advertising cookies. How we handle your data is explained in our privacy policy.