generated: '2026-09-10'
method: searched
source: https://api-docs.fraud.net/docs/public-apis/b2edb775739e6-api-documentation
provider: Fraud.net
providerId: fraud-net
limit_count: 0
description: >-
  Fraud.net publishes NO rate limits. The API documentation article covers introduction,
  key concepts, data safety, authentication, update semantics, webhooks and data backfill
  and never mentions a quota, a burst, a throttle or a 429. The published Swagger 2.0
  contract declares no 429 response on any of its 13 operations and defines no
  rate-limit response header. No X-RateLimit-*, RateLimit-* or Retry-After header is
  documented. This replaces a 2026-05-04 scaffold that asserted 10 req/min, 1,000
  req/month and a full X-RateLimit-* header set; none of that came from Fraud.net and it
  has been removed.
headers: {}
headers_note: >-
  None published. An agent has no runtime signal for remaining quota or backoff on this
  API; the only backoff signal is a 503/504, which the contract does describe.
responseCodes:
  throttled: null
  quotaExceeded: null
  serviceUnavailable: 503
  gatewayTimeout: 504
limits: []
related_performance_signal:
  field: data.timer
  detail: >-
    Every Check response returns `timer`, the milliseconds Fraud.net spent scoring, and
    the company publishes a "under 100 milliseconds" target. That is a latency signal, not
    a rate limit, and must not be read as one.
x-evidence:
  - {url: 'https://api-docs.fraud.net/docs/public-apis/b2edb775739e6-api-documentation', http_status: 200, fetched: '2026-09-10', finding: 'no rate limit, quota or throttling section'}
  - {url: 'https://api-docs.fraud.net/api/v1/projects/cHJqOjk1NTE0/table-of-contents?branch=master', http_status: 200, fetched: '2026-09-10', finding: 'the entire developer portal is 1 service + 2 articles; no rate-limit page exists'}
  - {source: 'openapi/fraud-net-public-apis-openapi.json', finding: 'no 429 declared on any of 13 operations; no rate-limit header parameter anywhere'}