Skip to main content
Skip to content

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

LimitValueOn reaching it
Requests per network origin600 / 60s429 with Retry-After
Requests per key, per endpoint300 / 60s429 with Retry-After
File listing page size50 default, 100 maximumClamped silently, not rejected
Key expiry options7, 30, 90, 365 daysNo non-expiring option exists
Scopes2, both readsA missing scope is 403, not 401
Workspaces per key1Any other id is 404

Agents and workspaces

LimitValueNotes
Spending ceiling, new agentNothingA real value, not a placeholder. Raise it deliberately.
Models available6, across 2 providersChosen per agent, not per workspace
Maximum agentsSet by planRead from the live billing catalogue
Automatic PurchasingOffA separate acknowledged permission, never inherited from an autonomy setting

Connectors

LimitValueNotes
Connector availabilityLive registryOnly customer-connectable providers are listed
Operation classificationRead or writeAn endpoint declared read-only that uses a writing method is classified as a write

Files

RuleBehaviour
Type checkingBy file signature, not by extension. A renamed executable is rejected at upload.
FilenamesStored as a basename with control and bidirectional-override characters removed, so a name cannot disguise its own extension.
Empty filesRejected.
Malformed textInvalid UTF-8, embedded NUL bytes and invalid JSON are all rejected rather than stored.