generated: '2026-09-18'
method: searched
source: >-
  https://www.autotrac.com.br/produtos-para-voce/embarcadores/,
  https://www.autotrac.com.br/solucoes/solucao-mercado-segurador/, the full sitemap_index.xml
  (745 URLs), the WordPress REST search index, the /fale-com-a-gente/perguntas-frequentes/ FAQ,
  and the third-party integrator guides at documentacao.senior.com.br and wiki.atua.com.br —
  read 2026-09-18.
provider: AutoTrac
providerId: autotrac
specification: API Commons Rate Limits
specificationVersion: '0.1'
schema: https://raw.githubusercontent.com/api-evangelist/interface-research/main/schema/api-commons.yml#/$defs/RateLimits
limit_count: 0
headers: {}
response_codes: {}
limits: []
description: >-
  AutoTrac publishes no rate limits. It publishes no API reference at all — the "Serviço API de
  integração" is marketed on two product pages and documented nowhere public, so there is no
  quota, throttle window, burst ceiling, 429 behaviour, or Retry-After/X-RateLimit header a
  consumer could read before contracting. The only public signal about the integration surface
  is the Atua integrator guide's instruction that the customer's server IPs must be sent to
  AutoTrac for allow-listing, which is an access control, not a rate limit. The previous version
  of this file was an API Evangelist scaffold with invented per-tier limits (stamped as such on
  2026-08-11); it is replaced here by this measured zero.
note: >-
  limit_count 0 is a measured zero, not an unchecked field. If AutoTrac issues limits inside its
  customer integration documentation, they are behind the commercial agreement and were not
  reachable by this pass.
maintainers:
  - FN: Kin Lane
    email: kin@apievangelist.com