> For the complete documentation index, see [llms.txt](https://anyint.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://anyint.gitbook.io/docs/pricing-and-plans/plan-subscriptions.md).

# plan subscriptions

Plan subscriptions are the simplest way to buy access to AnyInt. You choose one monthly tier, receive one subscription-backed key, and the included models share a common usage pool.

## Published plan tiers

| Plan     | Monthly price | Daily call limit | Monthly token cap | Prompt caching |
| -------- | ------------- | ---------------- | ----------------- | -------------- |
| Starter  | `$9`          | `30`             | `3M`              | No             |
| Standard | `$30`         | `100`            | `10M`             | Yes            |
| Premium  | `$80`         | `300`            | `25M`             | Yes            |

## How plan subscriptions behave

* included models share one pool of limits
* daily call limits trigger throttling behavior
* monthly token caps are hard usage boundaries
* the subscription key becomes the main access key for the plan

## What happens at the limit

| Limit type                | Expected behavior                                          |
| ------------------------- | ---------------------------------------------------------- |
| daily call limit reached  | requests may be throttled rather than immediately rejected |
| monthly token cap reached | requests should be rejected with a clear `429` limit error |
| subscription expires      | the plan key becomes invalid                               |

## Lifecycle rules

* you can upgrade without changing your integration pattern
* upgrades should keep current-month usage rather than resetting it
* if the key is regenerated, the old key stops working immediately
* you cannot create a plan subscription while an active custom subscription already exists

## Good fit

Choose a plan subscription if you want:

* one predictable monthly tier
* broad model access without per-model purchasing
* a simpler setup for individuals or small teams

## Operational advice

* keep one plan key per environment
* monitor shared usage so one workload does not consume the full pool
* use the models route and dashboard to confirm the exact model IDs available under your account