The rate-limited API you only call once

Your enrichment pipeline calls a third-party API capped at a thousand requests a day. Every outbound call already goes through hoody-curl, so you add a hook on the curl service: before a request leaves, the script checks shared state for that URL. Hit: it short-circuits with the stored response and nothing goes out. Miss: it forwards, stores the answer, and the next identical call never leaves the box.

Nothing in the pipeline changed. No cache client, no Redis, no wrapper library. The cache appeared underneath the code, in the path the requests were already taking.

The quota stops being a ceiling, and repeats stop counting against it. The API answers once; the cache answers the rest.

The API answers once; the cache answers the rest.