Bureau Of Alcohol Tobacco Firearms And Explosives Atf Authentication

Authentication

Bureau of Alcohol, Tobacco, Firearms and Explosives (ATF) declares 0 security scheme(s) across its OpenAPI definitions.

AlcoholExplosivesFederal-GovernmentFirearmsGeospatialLaw EnforcementOpen DataPublic SafetyRegulationsTobacco
Methods: Schemes: 0 OAuth flows: API key in:

Security Schemes

Source

Authentication Profile

Raw ↑
generated: '2026-09-05'
method: probed
provider: Bureau of Alcohol, Tobacco, Firearms and Explosives (ATF)
providerId: bureau-of-alcohol-tobacco-firearms-and-explosives-atf-
source: >-
  Live anonymous requests on 2026-09-05 to every public ATF API endpoint found by
  contract discovery. No credential of any kind was presented and every request
  succeeded.
summary: >-
  There is no authentication. ATF's entire public API surface — the eRegulations
  JSON API and both ArcGIS feature services — answers unauthenticated GET requests
  with data. No API key, no OAuth client, no signup, no registration, no rate-limit
  token. For an agent this is the simplest possible posture: no onboarding step
  exists to complete.
schemes: []
posture:
  anonymous: true
  registration_required: false
  key_issuance: none
  oauth2: false
  openid_connect: false
  mutual_tls: false
  signing: none
evidence:
  - surface: ATF eRegulations API
    url: https://regulations.atf.gov/api/regulation
    status: 200
    detail: 200 application/json with no Authorization header sent.
  - surface: ATF eRegulations search
    url: https://regulations.atf.gov/api/search?q=firearm
    status: 200
    detail: 200 application/json, 1,596 total_hits, anonymous.
  - surface: Federal Firearm Licensees locations (ArcGIS Feature Service)
    url: https://services6.arcgis.com/PrP5ZtrES07DmVmv/arcgis/rest/services/Federal_Firearm_Licensees_locations/FeatureServer/0/query?where=1%3D1&returnCountOnly=true&f=json
    status: 200
    detail: 200 {"count":77514}, anonymous. Item `access` is "public" in ArcGIS Online.
  - surface: ATF Office Locations (ArcGIS Feature Service)
    url: https://services6.arcgis.com/PrP5ZtrES07DmVmv/arcgis/rest/services/ATF_Office_Locations/FeatureServer/0/query?where=1%3D1&returnCountOnly=true&f=json
    status: 200
    detail: 200 {"count":537}, anonymous.
  - surface: /.well-known/oauth-authorization-server
    url: https://www.atf.gov/.well-known/oauth-authorization-server
    status: 403
    detail: >-
      No authorization-server metadata anywhere. The 403 is an Akamai edge refusal
      of our crawler, not an ATF answer; the same path on regulations.atf.gov
      returns the app's HTML shell, which is equally not a discovery document.
gated_surfaces:
  - name: ATF eForms
    url: https://eforms.atf.gov/
    note: >-
      Licensee-facing form filing behind a Login.gov account. It is a web
      application, not a documented API; no machine interface is published.
  - name: eTrace / National Tracing Center
    url: https://www.atf.gov/firearms/etrace-internet-based-firearms-tracing-and-analysis
    note: >-
      Restricted to credentialed law-enforcement agencies. Not a public API and
      not scored as one.

Work with this as data

Every security artifact here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for security posture

4 MCP tools reach this
  • find_securityBrowse and filter every security artifact in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This security artifact
curl "https://apis.io/api/v1/security/bureau-of-alcohol-tobacco-firearms-and-explosives-atf--authentication"
All security posture
curl "https://apis.io/api/v1/security?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.