Plans and limits
What each plan includes and the hard limits that apply everywhere.
This page lists what each plan includes and the limits that apply on every plan. For prices, included usage, and billing, see the pricing page.
Plans
Free includes one Project. Pro and Enterprise include any number of Projects and generate the complete Spec for every Target. The pricing page describes the operations each paid Target includes and what applies beyond them.
CLI, MCP server, TypeScript SDK, Python SDK, and Go SDK are separate Targets. Each has its own Generation, pull request, compatibility result, and release history.
| Free | Pro | Enterprise | |
|---|---|---|---|
One-shot generation on the homepage and POST /api/v1/generate | First 25 operations, one package per run | Complete Spec, one package per run | Complete Spec, one package per run |
| API ingested and retained for a Project | Complete | Complete | Complete |
| Operations in each generated Target | First 25 | Complete Spec | Complete Spec |
| Projects | 1 | Unlimited | Unlimited |
| Targets per Project | All five | All five | All five |
| Regeneration pull requests, changelog, history, Spec Revisions | Included | Included | Included |
| Spec patches and configuration | Included | Included | Included |
| Preview Generations on Spec pull requests | Unlimited | Unlimited | Unlimited |
| Hosted MCP endpoint | 25 operations, one active Project | Complete Spec | Complete Spec |
| Webhook relay | Not included | Included | Included |
| Attribution in generated packages | On every plan | On every plan | On every plan |
Free limits generated Targets, not ingestion. Its Project retains every Spec Revision and raw source file.
API change review and Diagnostics inspect the full contract. Generations include 25 operations and report both generated and total counts. The 25 favor what an evaluation needs: the operation that returns the signed-in user, then the list, create, and get operations of the largest resources. Deprecated operations, operations marked [Internal], and names starting with _ come last. The generated api.json lists the operations left out. Upgrading generates the remainder from the Spec already linked.
Downgrading does not delete paid configuration or generated code. The oldest stored Project remains active on Free, with each Target limited to 25 operations. The active Project's hosted MCP URL follows the same cap. Other Projects, including their hosted MCP URLs, pause until the organization upgrades again.
Hard limits
| Limit | Value |
|---|---|
| Spec graph size | 10MB across all resolved documents |
| Expanded OpenAPI document graph | 10MB of JSON including formatting; 250,000 values; 128 levels of value nesting |
| Documents per Spec | 64 |
| Spec reference depth | 12 documents |
Spec read by URL for config.include or config.exclude | 64MB before selection; the selected part must fit the 10MB limits above |
Pasted or inline Spec (spec.inline) | 4MB, because the request body carries it. Send Specs up to 10MB by URL. |
| URL fetch timeout | 15 seconds across redirects and referenced documents |
| File contents | File lists carry no content; GET /files/{file_id} returns at most 24 KiB per request, with next_cursor for the rest. |
| 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 | 300 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
- One-shot generation creates no Project. Keyed API responses, including generated files, stay available for replay for 24 hours. Typeship’s CLI, MCP server, and SDKs add these keys automatically. An eligible anonymous URL run keeps its URL, Target/config recipe, and summary for seven days so you can claim it. See Idempotent writes for retry behavior and the Privacy Policy for data handling.
- Projects keep every Generation's files, warnings, and metadata, plus the complete resolved Spec Revision and every raw source file, even when Free generated only 25 operations. Deleting a Project deletes all of it.
- Preview Generations keep their generated files like any Generation, and do not count against your plan.
- 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.