What this page does and does not answer
| Question | Public answer |
|---|---|
| what repo-backed request-rate constants exist by build profile | this page answers that directly |
| what DDX-balance thresholds and burst constants appear in the public source set | this page answers that directly |
| what the currently hosted public deployment is enforcing right now | this page does not guarantee that; verify the target deployment, observed 429 behavior, and current public release posture before hardcoding limits |
Repo-backed request-rate tiers by build profile
These values are defined in operator constants and are release-conditional rather than universally fixed.| Build profile | Tier 0 (< 1,000 DDX) | Tier 1 (>= 1,000 DDX) | Tier 2 (>= 1,000,000 DDX) | Burst behavior |
|---|---|---|---|---|
Default (not alpha1, not no_rate_limit) | 900/hour (1 per 4s) | 1,800/hour (1 per 2s) | 180,000/hour (50/s average) | Tier bursts 1, 5, and global cap 50 |
alpha1 | Same request-rate tiers as default | Same request-rate tiers as default | Same request-rate tiers as default | Same burst constants as default |
no_rate_limit | Tiered hourly and per-tier burst guards are compiled out | Tiered hourly and per-tier burst guards are compiled out | Tiered hourly and per-tier burst guards are compiled out | Global burst-cap constant becomes 100000 |
Feature-gate caveats
| Build/runtime mode | Material difference from default constants |
|---|---|
feature = alpha1 | Collateral tranche table differs from non-alpha1 defaults |
feature = no_rate_limit | Burst cap changes (RATE_LIMIT_BURST_CAP = 100000) and core hourly tier constants are not applied the same way |
Burst-cap and edge controls
| Parameter | Value |
|---|---|
| Default global burst cap | 50 |
no_rate_limit burst cap | 100000 |
| Nginx non-whitelist note | 30 requests / minute appears as a code comment, not as a standalone generated API constant |
Live-deployment reading rule
- Treat the tables below as repo-backed build-profile facts, not as a timeless promise that every deployment enforces the same hosted quota at this moment.
- When your client depends on exact production retry behavior, combine this page with REST Rate Limits, observed
429 RateLimitresponses, and current deployment context. - Do not collapse repo constants, staging behavior, and live public-host posture into one undocumented “global limit.”
Collateral tranche reference by build profile
Tranches map DDX-balance upper bound to collateral cap.Default profile (not alpha1)
| DDX upper bound | Collateral cap |
|---|---|
1,000 | 10,000 |
1,000,000 | 1,000,000 |
0 fallback tranche | 100,000,000 |
alpha1
| DDX upper bound | Collateral cap |
|---|---|
1,000,000 | 10,000 |
0 fallback tranche | 10,000,000 |