Batch API Metering: Requests vs Evaluated Pairs

A ten-pair request is operationally different from a one-pair request even when both are one HTTP call.

Name the authoritative unit

Name the authoritative unit is the first design decision for batch API metering. A ten-pair request is operationally different from a one-pair request even when both are one HTTP call. Write the boundary down before choosing endpoints or drawing clinical-looking UI so reviewers can test the actual promise.

Expose observed units

For batch API metering, expose observed units should remain observable rather than becoming hidden adapter behavior. Give resolution, lookup, and interpretation separate states, then decide which failures a user may retry.

Make limits predictable

Make limits predictable needs an operational test, not only a happy-path example. Add a bounded timeout, stable error handling, request IDs, privacy-safe logging, and a fixture that proves the batch API metering workflow fails closed.