specification: API Commons Rate Limits
specificationVersion: '0.1'
schema: https://raw.githubusercontent.com/api-evangelist/interface-research/main/schema/api-commons.yml#/$defs/RateLimits
provider: Antero Resources
providerId: antero-resources
created: '2026-05-04'
# Provenance stamped 2026-08-11: this artifact was written by the API Evangelist
# bulk sweep dated 2026-05-04, not harvested from the provider. See roadmap#35.
method: searched
generated: '2026-09-02'
source: https://www.sec.gov/os/accessing-edgar-data
modified: '2026-09-02'
reconciled: true
tags:
  - Energy
  - Natural Gas
  - Public Filings
  - SEC EDGAR
  - Rate Limiting
description: >-
  Antero Resources does not operate a first-party API. The reachable data
  surface (SEC EDGAR for CIK 0001433270) is throttled by the SEC's published
  fair-access policy: 10 requests per second, with a User-Agent header
  identifying the consumer required on every call. Limits apply to the SEC
  endpoint, not to Antero itself.
notes: >-
  Limits below are SEC EDGAR's published fair-access policy. Consumers must
  set a descriptive User-Agent (typically `Sample Company Name
  contact@email.com`) per the SEC's developer guidance.
sources:
  - https://www.sec.gov/os/accessing-edgar-data
  - https://www.sec.gov/developer
headers:
  userAgent: User-Agent
responseCodes:
  throttled: 429
limits:
  - name: SEC EDGAR Fair-Access Limit
    scope: IP
    metric: requests_per_second
    limit: 10
    timeFrame: second
    notes: >-
      Applies to all data.sec.gov and www.sec.gov endpoints. Exceeding the
      limit results in HTTP 429 / 403 responses; a descriptive User-Agent
      header is required on every request.
policies:
  - name: User-Agent Required
    description: >-
      The SEC requires every EDGAR API request to include a User-Agent header
      identifying the consumer (e.g. `Acme Corp ops@acme.com`). Requests
      without a meaningful User-Agent may be blocked.
  - name: Fair-Access Throttling
    description: >-
      The SEC enforces a soft 10 requests-per-second ceiling per IP across
      EDGAR endpoints. Sustained excess traffic can result in temporary IP
      blocks; back off on 429.
  - name: Cache-Friendly
    description: >-
      EDGAR encourages caching of immutable filing artifacts; the
      submissions JSON is updated incrementally so consumers can poll daily
      rather than per-second.
maintainers:
  - FN: API Evangelist
    email: info@apievangelist.com
x-evidence:
  checked: '2026-09-02'
  probes:
    - url: https://www.sec.gov/os/accessing-edgar-data
      status: 200
      observed: >-
        Verbatim from the SEC page - "Fair access. Current max request rate: 10
        requests/second." and "Please declare your user agent in request
        headers", with the sample header "User-Agent: Sample Company Name
        AdminContact@<sample company domain>.com".
    - url: https://data.sec.gov/submissions/CIK0001433270.json
      status: 200
      observed: >-
        Antero's filing index served without authentication; no RateLimit-*,
        X-RateLimit-* or Retry-After headers are published by the SEC, so a
        client has no runtime limit signal and must self-throttle to the
        documented 10 req/sec.
    - url: https://www.anteroresources.com/openapi.json
      status: 404
      observed: >-
        Antero Resources operates no API of its own, so it publishes no rate
        limits of its own. Every limit in this file is the SEC's.
x-provenance-note: >-
  Upgraded generated -> searched on 2026-09-02: the 10 req/sec ceiling and the
  User-Agent requirement were read verbatim from the SEC's own published
  fair-access policy rather than assumed by the bulk sweep. The limits still
  belong to the SEC endpoint, not to Antero Resources.