Plans and limits
What each plan includes, what is metered, and the hard limits that apply everywhere.
Full pricing is on the pricing page. This page is the reference for what gates on which plan and the limits that apply regardless of plan.
Plans
Pro is priced per platform, per linked project, per month, with unlimited generations while linked. A platform is one generated target for a project: an SDK in one language (TypeScript, Python, and Go each count as one), the CLI, or the MCP server. A TypeScript SDK, a Python SDK, and a CLI are three platforms. Each language a project generates is its own package, its own pull request, and its own hosted generation. Enterprise covers large APIs, many projects, the hosted MCP endpoint, and contracts.
| Free | Pro | Enterprise | |
|---|---|---|---|
Ad hoc generation on the homepage and POST /v1/generate | Unlimited, first 25 operations, one platform per run, nothing stored | Same | Same |
| Hosted generations | Unlimited, first 25 endpoints each | Unlimited, whole spec | Unlimited, whole spec |
| Platforms per project | 1: an SDK in one language | Any, billed each | Any, billed each |
| Endpoints included per project | 25 | 250, then $1.50 per endpoint per month | Custom |
| Regeneration pull requests, changelog, history, spec versions | Manual runs only; automatic regeneration is Pro | Included | Included |
| Spec patches and config | Applied to every generation | Included | Included |
| Preview builds on spec PRs | Unlimited | Unlimited | |
| Hosted MCP endpoint | Included | ||
| Webhook relay | Included | Included | |
| Attribution in generated packages | On every plan | On every plan | On every plan |
The endpoint meter is measured on the spec after patches, so removing operations with a patch reduces what is metered. It is counted once per project, whatever a project generates: endpoints belong to the spec, so a project building three languages does not pay for its endpoints three times.
Hard limits
| Limit | Value |
|---|---|
| Spec size | 10MB, pasted or fetched |
| Pasted spec in a browser request | About 4.5MB. Larger specs go in by URL. |
| URL fetch timeout | 15 seconds |
| Inline files in an API response | 3.5MB. Above that, files_omitted and a per-file endpoint. |
| Spec patches per project | 50 |
| Global parameters | 20 |
| Pagination rules | 100 keys |
| API list page size | 100 |
| Anonymous generation | 20 requests per minute per IP |
| Authenticated API requests | 60 requests per minute per key |
| Webhook relay | 1MB per event, 5,000 events per session, events kept 24 hours, sessions 48 hours idle |
| Project name | 80 characters |
| Package name | 214 characters, valid for its registry |
What is stored
- Ad hoc generation stores nothing. Files are returned and forgotten.
- Projects keep every generation's files, warnings, and metadata, plus every distinct spec version's raw text. Deleting a project deletes all of it.
- Preview builds keep their generated files like any generation, and are not metered.
- Relay events are transient: 24 hours at most.
- API keys are stored as a hash. The full key exists only in the response that created it.