Is there a name for four services accidentally calling the same paid API for the same input?

Four different parts of the same app were each calling a paid Distance Matrix API separately for delivery estimates, sometimes for the exact same pickup and drop coordinates within the same request window.

Nobody designed it that way on purpose. Each part of the app was built and shipped separately, and each one just reached for the same API the way the last one had, with no shared layer between them.

Fixed it by keying a shared cache on the rounded coordinate pair and making every part check it before calling out, with a crash safe fallback if the cached value ever came back malformed. One call per coordinate pair instead of four.

Is there a name for this pattern beyond just "add a cache"? Feels like it should have one given how easy it is to build four times by accident.