Limits.
PAMbase has two sets of quotas: user plans (the person whose memory is stored) and developer plans (your app's API consumption and reach). Crossing a cap returns 402 limit_exceeded at the point of the write or connect — never on a read. Plans and prices live on Pricing.
User plans
Every user has exactly one memory store across all apps, on every plan — plans change its size, not its count. See Memory.
| Plan | Memories | Connected apps | Memory stores |
|---|---|---|---|
| Free | 500 | 3 | 1 |
| Plus | 10,000 | Unlimited | 1 |
| Pro | 100,000 | Unlimited | 1 |
Developer plans
Quotas for your app: API call volume per month and the number of users that may connect to it.
| Plan | API calls / mo | Connected users |
|---|---|---|
| Sandbox | 10,000 | 50 |
| Starter | 200,000 | 1,000 |
| Growth | 2,000,000 | 25,000 |
Pro / Enterprise | Unlimited | Unlimited |
What counts
Metering tracks the following against your developer plan:
- API calls — every request to the REST API.
- Hosted tokens — input + output tokens for Gateway chat (the hosted-inference path).
- Memory writes — memories persisted via
POST /v1/memoriesand hosted chat. - Context requests — calls to
GET /v1/context. - Connected users — distinct users with an active connection to your app.
A user hitting their memory cap gets 402 limit_exceeded on the next write that would exceed it; a user adding one app past their connected-apps cap gets it at connect time; your app exceeding its monthly API-call quota gets it on the call that crosses the line. Handle it like any other error and prompt an upgrade.
Users can see their consumption via GET /v1/usage in the Hub. Plan upgrades take effect immediately. Compare tiers on Pricing.