Public launch limits are conservative while the API is in early production. Treat 429 as authoritative if it is returned by the edge or API layer.

​
Client behavior

1

Prefer event or status polling with backoff

Formation status can be polled, but agents should back off after each request instead of polling in tight loops.
2

Avoid duplicate writes

Before retrying a write, read the current entity or proposal state. This matters for legal filing and treasury-adjacent workflows.
3

Escalate repeated failures

If the same entity or proposal fails repeatedly, stop and surface the failure to a human operator.

​
Suggested backoff

const delayMs = Math.min(1000 * 2 ** attempt, 60000) + Math.random() * 1000;

​
High-risk operations

Do not automatically retry legal filing, dissolution, treasury disbursement, or credential expansion after an ambiguous result. Re-read state and escalate if the effect is unclear.