# Usage limits and allowances | answer.cloud Docs

> Canonical source: [Usage limits and allowances | answer.cloud Docs](https://www.answer.cloud/docs/account/limits/)

Check separate allowances for pages, CMS content, chat, analytics, deployments, uploads, MCP requests, and temporary first-launch credentials.

reference

Usage limits and allowances

Check separate allowances for pages, CMS content, chat, analytics, deployments, uploads, MCP requests, and temporary first-launch credentials.

Reviewed November 1, 2026

Allowances apply to different resources. Use the returned `max_bytes`, remaining deployment count, page warnings, and the intended site's plan as the authority for an operation. The defaults below describe new pricing-managed standalone websites as reviewed on November 1, 2026.

## Standalone allowances

| Resource                             | Free                          | Pro                         |
|------------------------------------|-------------------------------|-----------------------------|
| Indexed static pages per deploy    | 12                            | 500                         |
| Deployment starts per site per UTC day | 30                        | 200                         |
| ZIP artifact ceiling               | 10 MiB: 10,485,760 bytes      | 1 GiB: 1,073,741,824 bytes  |
| Active CMS pages, including drafts | 10                            | Within site capacity        |
| Chat-eligible published content pages | First 10                   | Within site capacity        |
| Analytics availability             | One calendar month after site creation | Ongoing               |
| Public site search                 | Upgrade required              | Included                   |

Static indexing limits are separate from CMS limits. A deployment may go live with skipped-page warnings, so inspect `pages_ingested`, `pages_skipped`, and `warnings` rather than assuming every shipped page was indexed.

Archived CMS entries free a Free CMS slot. Restoring an archived entry checks the allowance again. Chat eligibility is determined by published content ordered by creation time and ID; collection indexes and archived pages do not supply extra slots. Retrieval enforces the allowance even when older embeddings remain stored.

The analytics trial expires one calendar month after site creation, rather than after a fixed number of sessions. Reporting needs Pro afterward, and browser collection for that Free site is discarded. There is no enabled standalone overage meter or fixed session billing allowance in this implementation.

## Transport and request limits

`deploy_files` accepts 1–200 files and up to **512,000 decoded bytes total**. Base64 increases request size, but the decoded content determines this ceiling. Use `start_deploy` for complete websites. Its signed upload URL lasts 900 seconds. Finalization checks the actual uploaded ZIP size and deletes an oversized artifact.

MCP requests are limited to 60 per credential per minute, with a pre-authentication limit of 120 per IP per minute. Honor returned retry guidance. The standard managed-site deployment quota is shared across credentials for that site and resets by UTC day. Creating another key does not increase it. CMS operations do not consume deployment starts, but still count toward request limits.

## First-launch allowances

Temporary guest access lasts 24 hours and permits an initial launch plus five redeployments: six starts total. Claiming the account ends build access earlier. Use `deploys_remaining`, not the normal daily counter.

Bootstrap reservations are limited to three per email and five per IP over a rolling 24-hour window. The anonymous readiness assessment has its own short-lived credential and bounded request/upload attempts; it does not reserve a customer site. Preserve the original source and request key when recovering.

Legacy owners and companion sites can have different allowances. Consult [plan eligibility](https://www.answer.cloud/docs/account/plans/) and [deployment recovery](https://www.answer.cloud/docs/troubleshooting/deployments/) before changing targets or retrying.