Limits and quotas

A quota is a fixed usage allowance. When it is used up, repeating the same request does not add more capacity.

AgentGrid.io has Free, Lite, Pro, and Business plans. Billing and artifact capacity are team-scoped, even though visibility and creation access are workspace-scoped. The live pricing page is authoritative for current prices and entitlements; see Plans and usage.

Artifact capacity

Every plan includes unlimited agent seats. Deleting an artifact may free artifact capacity.

Free URL and Figma import allowance

Free teams receive five successful imports total across Import from URL and Import from Figma. This is one combined allowance, not five of each.

Artifact capacity and import allowance are separate checks. Deleting an imported artifact does not restore a consumed import. When the allowance is exhausted, follow the upgrade path instead of retrying.

Folder and ZIP imports

• Maximum transport size: 50 MiB.
• Maximum file count: 1,000 files.
• Import one folder or one archive at a time.
• Include source files and required assets.
• Exclude dependencies, build output, and ignored files such as node_modules.
• Apps require an entry point; Markdown imports require .md files.
• Import creates a new artifact and does not remain synchronized with local files.

See Import a folder or ZIP.

Time and credential limits

Connections may end after revocation, approval expiry, or a long inactive stretch. See Token lifetimes and reconnecting.

Workspace and permission boundaries

• anima list spans all reachable workspaces—the workspaces the agent has permission to access. --workspace <id> filters to one.
• Creation and duplication require access to the destination workspace.
• If an agent can create in several workspaces, --workspace is required because there is no default.
• Workspace access does not change the team's billing plan.
• Publishing requires publish; sharing requires share. Agents publish only after an explicit human request.

When a limit is reached

A human sees the applicable upgrade or correction path. A terminal failure cannot be fixed by repeating the same request. An agent should report a terminal quota denial and stop retrying. Invalid import content can be corrected and retried; an exhausted team or import quota cannot.

See Terminal states and Troubleshooting.

Questions and answers

Are artifact capacity and the Free import allowance the same limit?

No. Artifact capacity counts team artifacts. The Free allowance counts five successful URL and Figma imports combined.

Does deleting an imported artifact return a Free import?

No. Deletion may free artifact capacity, but it does not restore a consumed URL/Figma import.

Which import failures can I fix and retry?

Correct invalid paths, malformed archives, unsupported structure, the wrong artifact type, or a missing entry point. An exhausted quota requires cleanup or an upgrade instead.

Scope

A quota is a fixed usage allowance. A terminal failure cannot be fixed by repeating the same request.

Plans are Free, Lite, Pro, and Business. Billing and artifact capacity apply to the team and cover all its workspaces. Access is workspace-scoped. Agents consume no seats. Use Plans and usage and the live pricing page rather than copying prices.

Artifact capacity

Deletion may free artifact capacity.

URL/Figma import allowance

A Free team has five successful imports combined across Import from URL and Import from Figma. It is not five per method. Capacity and import allowance are independent. Deleting an imported artifact does not refund an import.

Treat an exhausted allowance as terminal for that attempt: relay the upgrade path and do not retry.

Folder and ZIP constraints

• Up to 50 MiB and 1,000 files.
• One folder or .zip per import.
• Include source and assets; exclude dependencies, build output, and ignored files.
• app needs an entry point; markdown needs .md files.
• Import creates a new, unsynchronized artifact.

Correct invalid paths, malformed archives, unsupported structure, or a missing entry point before retrying. See Import a folder or ZIP.

Time limits

Workspace rules

Discover scope with anima workspaces. Omit --workspace from list to span all readable workspaces; add it to filter. For creation or duplication, omit --workspace only when create access exists in exactly one workspace. Otherwise there is no default.

Require source read access and destination create access for duplication. Never probe a denied workspace. Publishing additionally requires publish and an explicit human request.

Failure classes

• Terminal: quota exhausted, workspace denied, capability denied, revoked identity, expired/deleted artifact.
• Retry after correction: malformed ZIP, invalid path, unsupported structure, missing entry point.
• Retryable: a temporary network or server failure may succeed later. Wait between attempts and stop after a small number of retries.
• Check before retry: duplicate timeout or lost response. Duplication is non-idempotent, which means repeating it may create another artifact. List destination artifacts first.

See Terminal states.

Questions and answers

Which limit applies before creating an artifact?

Check the destination team's artifact capacity. For URL or Figma import on Free, also account for the separate five-import combined allowance.

When may an agent omit --workspace?

For creation or duplication, only when create access exists in exactly one workspace. Otherwise require an explicit destination ID.

How should an uncertain duplicate be retried?

List recent artifacts in the destination first. Duplication may create another artifact when repeated after a timeout or lost response.