Skip to Content
Plans

Plans

Accly plans control Gateway API access, API keys, model tiers, weighted request units, rate limits, request-count guards, hosted app access, and billing status.

PlanPriceAPI keysModel tiersDaily request unitsRPM
Free$0NoBasicHosted app trial onlyHosted app only
Starter$15/monthUp to 10Basic, Advanced40035
Pro$30/monthUp to 10Basic, Advanced, Thinking, Beta100065
Max$100/monthUp to 10Basic, Advanced, Thinking, Beta400065

Free

Free is for trying Accly in the hosted app before subscribing. Free does not include Gateway API keys.

ItemValue
Price$0
Free trial allowanceOne-time hosted app trial
Hosted app messages15 per conversation
RPMHosted app only
Daily API requests0
Model tiersBasic
API keysNo
Hosted app accessYes
Gateway API accessNo

The free trial allowance does not reset daily. When it is exhausted, upgrade to continue using Accly models.

Starter

Starter is for regular personal or small-team usage that needs API access and Advanced model tiers.

ItemValue
Price$15/month
Daily request units400
Request-count guard400 requests/day
RPM35
Model tiersBasic, Advanced
API keysUp to 10
Hosted app accessYes
Gateway API accessYes

Starter is the first plan that supports Accly API keys.

Pro

Pro is for heavier daily usage, Thinking-tier models, and Beta-tagged model access.

ItemValue
Price$30/month
Daily request units1000
Request-count guard1000 requests/day
RPM65
Model tiersBasic, Advanced, Thinking, Beta
API keysUp to 10
Hosted app accessYes
Gateway API accessYes

Max

Max is for users who need the largest daily unit capacity available in the current plan set.

ItemValue
Price$100/month
Daily request units4000
Request-count guard4000 requests/day
RPM65
Model tiersBasic, Advanced, Thinking, Beta
API keysUp to 10
Hosted app accessYes
Gateway API accessYes

Max has the same RPM as Pro. It is designed for higher daily capacity through more request units and a larger request-count guard while keeping per-minute throughput controlled.

Unit weighting

One API call does not always equal one unit. Lightweight model requests can consume one unit. Heavier models, larger context, long outputs, cached context reads, and agentic coding workflows can consume more units.

Request units reset daily at midnight UTC. They do not roll over and do not represent cash value.