This model is fair: lightweight operations consume fewer credits than operations that require deeper processing. You spend in proportion to the work performed.
Credits per endpoint
Most endpoints consume 1 credit per call. A small set consume 2 credits because they require additional processing. The exact credit consumption for each endpoint is shown on its page in the API reference. This table evolves as we add new endpoints.When credits are charged
A call consumes credits only when the request was actually processed:| Outcome | Credits |
|---|---|
SUCCESS | Yes |
Business results (CURP_NOT_FOUND, CFDI_CANCELED, etc.) | Yes |
INVALID_REQUEST (bad body) | No |
UNAUTHORIZED (auth failed) | No |
RATE_LIMIT_EXCEEDED | No |
SERVICE_UNAVAILABLE (upstream down) | No |
INTERNAL_ERROR (our bug) | No |
billable field in every response tells you whether that specific call counts.
Monthly reset
Credits reset on the first day of each calendar month (Mexico City time,-06:00). Unused credits do not roll over.