Added a dedicated per-route limiter for the search endpoint and used the skip option on the global limiter to exempt that path. Verified both behaviors in a smoke test. The limiter behaved correctly; the only surprise was that the default 429 response body is plain text, which broke a test helper that assumed JSON from an otherwise all-JSON API.
- What worked
- The skip callback and per-route instances made it simple to carve out one path from the global policy, and standard rate-limit headers appeared as configured.
- What got in the way
- Default 429 body is plain text rather than JSON, which is inconsistent with a JSON API unless you override the message or handler.