USDA SNAP Retailer Locator
The USDA Food and Nutrition Administration (FNA) - renamed from the Food and Nutrition Service (FNS) on June 1, 2026 - publishes an open, public geospatial API for the Supplemental Nutrition Assistance Program (SNAP) Retailer Locator. The data is hosted as an Esri ArcGIS Feature Service (snap_retailer_location_data) rather than a bespoke fns.usda.gov or api.fns.usda.gov endpoint, and is embedded directly in the public retailer locator tool at fna.usda.gov/snap/retailer-locator. It exposes point-in-time location records - name, address, city, state, zip, county, store type, latitude/longitude, and Healthy Incentive Program participation - for every currently authorized SNAP retailer nationwide (roughly a quarter million records as of the review date), queryable anonymously over REST with no API key, in JSON, GeoJSON, or PBF, with CSV/Shapefile/KML export also available through the ArcGIS Hub item page. Data is refreshed on a recurring basis by FNA; the service is read-only (Query only - no write capabilities).
More than an index entry, but the surface is still mostly links rather than artifacts — the cohort most likely to move a full band from modest, well-targeted work.
API Evangelist profiles USDA SNAP Retailer Locator the way a machine reads it — 6 machine-readable artifacts across 2 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — USDA SNAP Retailer Locator scores 25.9/100 (emerging), with a separate agent-readiness read of 39/100 (agent aware). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile USDA SNAP Retailer Locator
Each block below is one kind of artifact we hold for USDA SNAP Retailer Locator. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 2
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
USDA SNAP Retailer Locator Retailers API
Query SNAP retailer location records.
USDA SNAP Retailer Locator Service API
Feature service and layer metadata.
Open Collections 1
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
USDA SNAP Retailer Location Data API
OPEN COLLECTIONRate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Usda Snap Rate Limits
RATE LIMITSSecurity Posture 1
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for USDA SNAP Retailer Locator — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Access & Security 1
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Company 1
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/usda-snap · machine-readable index on apis.io