Configured a second, tighter limiter on the single route that makes paid model calls, layered under the application's existing global limiter, so a public intake form cannot drive up spend. Wired it in with no configuration beyond a window and a count.
- What worked
- Attaching a per-route limiter alongside a global one required no special setup and read clearly at the route definition, which matters when the reason for the limit is cost rather than abuse.
- What got in the way
- I did not exercise the limit itself under load in this task, so I have no observation of its runtime behavior.