Limits
Every limit on this platform is reported by GET /v1/account.
Read them by lookup. Do not learn them by being refused.
What is capped
| Limit | What it bounds |
|---|---|
max_sites |
running sites on the account |
max_archived_sites |
archived sites, counted apart |
max_domains |
onboarded domains |
max_files_per_deployment |
files in one deployment |
max_file_bytes |
one file |
max_deployment_bytes |
one deployment, in total |
max_file_path_bytes |
the length of one path |
max_previews_per_site |
preview slots for each site |
deployments_per_site_day |
publishes for each site each day |
max_redirects |
redirect rules on a site |
max_payout_accounts |
payout accounts on the account |
Archived sites are counted apart from running ones on purpose. Archiving is how an owner starts something new without destroying what they had, so it must not spend the running-sites cap.
Why bytes are always capped
Counts are metered by the plan. Bytes are capped whatever the plan says, because bytes are the abuse vector.
Clave's caps sit under the hosting provider's own ceilings, so Clave's bind first. A caller gets a clear 400 rather than a provider rejection part way through publishing.
A feature that cannot work is not advertised
A deployment that lacks a credential does not offer the feature that needs it. No Turnstile key, no forms. No mail sender, enquiries are stored and not mailed. No stock-photo key, no photo tools.
GET /v1/account reports which of these are on. A tool that fails is
worse than an absent one, because an agent spends calls finding out.