Where does Arcjet make a rate-limit decision?
Your app calls Arcjet where a request needs checking. Start with one endpoint, such as generating a preview. Choose what to count together, such as requests by the same signed-in user. Keep the app’s sign-in and permission checks in place.
Can you see who would be blocked before enforcing a limit?
Dry-run mode reports what the rule would do without blocking the request. Review the results for ordinary customers who may repeat a task. Decide what retry information your app should show if you later enable blocking.
What should you count when estimating cost?
Check the plan and usage fees for web requests, plus how long the plan keeps logs. List the endpoints that will call the service and estimate the requests to those endpoints. Keep a copy of your choices about the identity, window and behavior when the service is unavailable.
Would a normal customer run into the preview limit?
On paper, list three preview requests by one fictional customer and a separate request by another. Use an example rule allowing two previews per account within one window.
- Mark the decisionsThe third preview from the first account is over the limit. The second account still has its own allowance.
- Compare modesWrite the result in a dry-run report, then write what your app should tell the first customer under enforcement.