Evidence review
What to inspect before changing anything
Start with the delivered website and the real user journey. Record the current state so the team can distinguish an observed problem from an assumption and compare the same surface after deployment.
- 01Identify login, scan, upload, message and generation endpoints
- 02Measure normal burst and sustained traffic
- 03Review current keys, windows and bypass paths
Implementation
A practical improvement plan
Make the smallest coherent change that solves the observed problem. Keep normal code review, accessibility, security and product checks in the loop instead of optimizing for the scan alone.
- 01Set endpoint-specific limits and budgets
- 02Combine account, IP and risk signals where appropriate
- 03Return stable errors and Retry-After guidance
Verification
How to verify the result
Verification should test the intended outcome and the most likely regression. Use the production delivery path whenever headers, caching, rendering or third-party services affect the result.
- 01Run controlled burst and distributed tests
- 02Confirm legitimate retries recover
- 03Monitor blocks, latency and infrastructure cost
Common pitfall
A shortcut to avoid
A single global IP limit can punish shared networks while determined attackers rotate addresses.
Further reading
Primary guidance and references
These sources provide standards, security guidance or the interpretation framework used to keep this guide bounded. Product-specific implementation still requires review in the actual codebase.