Pricing & usage
Accly plans define Gateway API access, model tiers, API keys, daily budgets, daily request limits, RPM rate limits, and billing status.
One-time balance
The Free plan includes a $1 one-time model balance for trying Accly in the hosted app. Free does not support Gateway API keys.
This balance does not reset daily. When the Free balance is exhausted, new model requests are blocked until you upgrade.
The final successful Free request can consume the remaining balance. The next request is blocked with free_balance_exhausted.
Promotional balances and trials
Promotional balances, gift credits, trial access, or plan-like benefits can affect the usage available to your account while they are active.
Promotional benefits do not remove model tier rules, daily budgets, RPM, daily request limits, subscription state, abuse controls, or campaign-specific limits. See Redeem Codes for how promotional codes are applied.
Daily budget: Balanced
Balanced is the default and recommended Gateway mode for most paid-plan API usage.
Balanced routes requests through Accly’s optimization layer. That layer can refine agent-facing system instructions, routing structure, and tool-use framing so common coding-agent and automation failures are reduced before the request reaches the selected model route.
Balanced is designed to improve reliability, speed, and cost efficiency without changing your main user context, application data, or the core task you send. Use Balanced for regular API calls, CLI tools, internal prototypes, coding agents, background automations, and workflows where better cost-to-quality is more important than exact provider-native request behavior.
Paid plans have a daily Balanced model budget:
| Plan | Balanced daily budget |
|---|---|
| Starter | $8 |
| Pro | $20 |
| Max | $60 |
When the daily Balanced budget is exhausted, new Balanced requests are blocked with budget_exceeded. Daily budgets reset at midnight UTC.
Daily budget: Premium
Premium is a strict passthrough mode for workflows that need the request sent as directly as possible.
Premium avoids Accly’s Balanced optimization layer. Accly does not adjust prompt structure, tool-use framing, or routing instructions for optimization before sending the request through Premium-capable routes. Use Premium when exact raw formatting, original model behavior, eval consistency, regression tests, or provider-specific response characteristics matter more than cost optimization.
Premium mode uses a separate daily budget from Balanced:
| Plan | Premium daily budget |
|---|---|
| Starter | $5 |
| Pro | $12 |
| Max | $40 |
Free uses Balanced mode only.
Choosing Balanced or Premium
| Use case | Recommended mode | Why |
|---|---|---|
| Coding agents, CLI tools, and agent automations | Balanced | Better cost control and fewer common agent/tool-usage failures |
| Regular app API calls and internal prototypes | Balanced | Default mode with the best cost-to-quality tradeoff |
| High-volume exploratory usage | Balanced | Uses the larger Balanced daily budget on each paid plan |
| Prompt regression tests and evals | Premium | Keeps request behavior closer to strict passthrough |
| Format-sensitive workflows where every instruction wrapper matters | Premium | Avoids Balanced prompt and tool-structure optimization |
| Debugging provider-native behavior | Premium | Reduces Accly-side request shaping before routing |
The mode choice affects routing behavior and which daily budget is consumed. It does not bypass model tier access, API key permissions, RPM, daily request limits, abuse controls, provider availability, or subscription status.
What Balanced and Premium do not change
Balanced and Premium are Gateway routing modes. They do not change your account plan, increase your RPM, unlock unavailable model tiers, or remove policy enforcement.
Accly does not use Gateway API requests, prompts, context, or generated outputs to train Accly-owned foundation models. Gateway payload content is processed to route and generate the response; usage metadata can be processed for billing, cost tracking, reliability, debugging, analytics, and abuse prevention. See AI Safety & Data.
Hosted app messages
Free includes 15 messages per hosted app conversation in the product plan configuration.
This is not the main Gateway API limit. API usage is primarily controlled by daily budgets, RPM, daily requests, model tier access, API key access, and subscription status.
Rate limit: RPM
RPM means requests per minute. It controls short-term request speed.
| Plan | Gateway API access | RPM |
|---|---|---|
| Free | No | Hosted app only |
| Starter | Yes | 35 |
| Pro | Yes | 65 |
| Max | Yes | 65 |
If you exceed RPM, the gateway returns rate_limit_exceeded. Wait for the short reset window before retrying.
Free RPM applies to hosted app usage. Free does not include Gateway API access or API keys.
Daily requests
Daily requests are separate from RPM. They control total request capacity for the day.
| Plan | Daily requests |
|---|---|
| Free | 0 API daily requests |
| Starter | 400 |
| Pro | 1100 |
| Max | 2500 |
Daily request quota resets at midnight UTC. When daily requests are exhausted, the gateway returns daily_limit_exceeded.
Daily budgets vs daily requests vs RPM
These limits protect different parts of usage:
| Limit | What it controls | Example |
|---|---|---|
| Daily budget | Model-cost capacity for Balanced or Premium mode | A high-cost model can exhaust budget before request count |
| Daily requests | Total request count for the day | Many small requests can exhaust daily request quota |
| RPM | Short-term request speed | A burst can hit RPM even with daily capacity remaining |
Model tiers
Plans also control model tiers:
| Plan | Tiers |
|---|---|
| Free | Basic |
| Starter | Basic, Advanced |
| Pro | Basic, Advanced, Thinking, Beta |
| Max | Basic, Advanced, Thinking, Beta |
If you request a model tier your plan cannot use, the gateway returns model_not_allowed.
API keys
API keys are available on paid plans.
| Plan | API keys |
|---|---|
| Free | No |
| Starter | Up to 10 |
| Pro | Up to 10 |
| Max | Up to 10 |
Free does not support API keys.
Priority beta
Pro and Max include access to Beta-tagged model tiers while those models are available.
Beta availability can change. If a model is tagged Beta, Free and Starter cannot use it.
When limits are hit
| Situation | What happens |
|---|---|
| Free balance exhausted | Next Free request is blocked with free_balance_exhausted |
| Daily budget exhausted | New requests in that mode are blocked with budget_exceeded |
| Daily requests exhausted | New requests are blocked with daily_limit_exceeded |
| RPM exceeded | Request is blocked with rate_limit_exceeded |
| Too many concurrent requests | Paid requests wait briefly, then can fail with concurrency_queue_timeout |
Why Max has the same RPM as Pro
Max is designed for higher daily capacity, not higher resale-style throughput. It includes larger daily budgets and daily request capacity while keeping RPM controlled.
| Plan | Balanced | Premium | Daily requests | RPM |
|---|---|---|---|---|
| Pro | $20 | $12 | 1100 | 65 |
| Max | $60 | $40 | 2500 | 65 |
If you need higher per-minute throughput for a specific use case, contact Accly before building around that requirement.