Every limit in one place

The numbers scattered through these pages, collected, with what happens when you reach each one.

Nothing here is new; every figure appears on the page it belongs to. It is collected because “what is the maximum page size” is a question people ask once and want answered without reading a page about pagination.

The API

Limit	Value	On reaching it
Requests per network origin	600 / 60s	`429` with `Retry-After`
Requests per key, per endpoint	300 / 60s	`429` with `Retry-After`
File listing page size	50 default, 100 maximum	Clamped silently, not rejected
Key expiry options	7, 30, 90, 365 days	No non-expiring option exists
Scopes	2, both reads	A missing scope is `403`, not `401`
Workspaces per key	1	Any other id is `404`

Agents and workspaces

Limit	Value	Notes
Spending ceiling, new agent	Nothing	A real value, not a placeholder. Raise it deliberately.
Models available	6, across 2 providers	Chosen per agent, not per workspace
Maximum agents	Set by plan	Read from the live billing catalogue
Automatic Purchasing	Off	A separate acknowledged permission, never inherited from an autonomy setting

Connectors

Limit	Value	Notes
Connectors in the catalogue	202	202 connectors across 33 categories
Custom connector routes	4	Generic REST, generic webhook, external MCP, bring-your-own-key
Operation classification	Read or write	An endpoint declared read-only that uses a writing method is classified as a write

Files

Rule	Behaviour
Type checking	By file signature, not by extension. A renamed executable is rejected at upload.
Filenames	Stored as a basename with control and bidirectional-override characters removed, so a name cannot disguise its own extension.
Empty files	Rejected.
Malformed text	Invalid UTF-8, embedded NUL bytes and invalid JSON are all rejected rather than stored.