Plans & Limits
Every account runs on a plan that sets its limits. Your personal account has its own plan, and each organization has its own.
Today, Free is the only self-serve plan, so the tables below show the Free tier. Paid Pro and Enterprise tiers with higher limits are on the way and will be published here once they are available.
Rate limits
Every tool call is rate-limited, per caller and per tool. The free tier's limits are:
| Window | Free tier |
|---|---|
| Per minute | 10 |
| Per hour | 100 |
| Per day | 500 |
Exceeding a limit returns a rate-limit error that tells you how long to wait before retrying.
Reading prompts and resources
Fetching a prompt (prompts/get) or reading a resource (resources/read) is counted against its own, more generous limit — reads are cheap, so they are not throttled at the tool-call rate:
| Window | Free tier |
|---|---|
| Per minute | 60 |
| Per hour | 1,000 |
| Per day | 10,000 |
Like tool calls, reads are counted per item. They do not consume your monthly tool-invocation quota below.
Fetching apistash/agent-doctor uses these prompt-read limits. Its subsequent list_agents
inventory and each get_agent read are normal tool calls: they consume monthly tool invocations
and use the tool rate limits above. The Doctor proposes phases of at most ten definitions;
previous calls can leave fewer reads available. See the audit workflow.
Monthly tool-invocation quota
Each account has a monthly quota — over the calendar month, UTC — on the total number of tool calls, both built-in and custom:
| Plan | Tool calls / month |
|---|---|
| Free | 1,000 |
Successful calls count, as do calls that fail because of invalid input; failures caused by apistash itself do not.
Content limits
These caps apply to customer-owned content in both personal accounts and organizations. Platform prompts, including apistash/agent-doctor, consume no customer prompt slots:
| Limit | Free |
|---|---|
| Custom tools | 5 |
| Prompts | 25 |
| Versions per prompt | 5 |
| Agents | 25 |
| Versions per agent | 5 |
| Resources | 10 |
| API keys | 5 |
| Max upload size | 1 MiB |
| Total resource storage | 10 MiB |
For an organization, organization-owned and team-owned custom tools, prompts, resources, and agents each share their respective organization allowance. These are not separate allowances for each team. Prompts and agents also have their own per-item retained-version caps, regardless of whether they are personal, team-owned, or organization-owned.
When you reach a create limit, the API responds with 402 Payment Required, reporting the current
value against the limit. The corresponding codes are custom_tool_limit_reached,
prompt_limit_reached, resource_limit_reached, and agent_limit_reached. An update or restore
that cannot create another retained version uses prompt_version_limit_reached or
agent_version_limit_reached.
Organization limits
Organizations have additional limits on collaboration:
| Limit | Free |
|---|---|
| Seats (members) | 5 |
| Teams | 2 |
Each plan also caps how many custom roles an organization and its teams can define.
Your personal space in an organization
Inside an organization you also get your own personal space — private prompts, resources, and custom tools that you can draft before promoting them to a team or the whole organization, plus private agent definitions whose ownership remains fixed to the space where they were created. This space has its own limits, held separately from the organization's shared limits above, so your work-in-progress never eats into the organization's quota — and no single member can use up what the organization is saving for its teams.
| Your personal space (per member) | Free |
|---|---|
| Prompts | 5 |
| Agents | 5 |
| Custom tools | 2 |
| Resources | 5 |
| Total resource storage | 5 MiB |
| Tool calls / month | 500 |
Every allowance in this personal space is per member and separate from the organization's shared organization/team pools. Versioned prompts and agents use the organization's corresponding per-item version cap.
Your plan consumption against these limits is shown separately from Activity in the dashboard.
Single sign-on
Single sign-on — letting your team sign in with their business email through your identity provider — is an Enterprise feature. The Enterprise plan includes an allowance of verified domains for SSO.
Viewing plan consumption
Your current plan and live plan consumption against these limits are shown in Billing.
What your agents are actually calling and reading — and which of your content nobody uses — is a separate view: see Activity & Analytics.