💡 USDA Local Food Directory Auto-Enrichment for Market Profiles

[github-actions[bot]]

Summary

When a manager creates a new market profile, query the USDA Local Food Directories API to suggest matching entries and pre-fill profile data (name, address, hours, products sold, payment methods accepted including SNAP/EBT status). Reduces market onboarding from a 15-minute manual form to a 2-minute review-and-confirm flow, leveraging a free federal dataset of 7,800+ market listings.

Market Signal

The USDA National Farmers Market Directory contains 7,800+ market listings with structured data (location, hours, products, payment methods) available via a free REST API at usdalocalfoodportal.com/api/farmersmarket/. No competitor (Marketspread, ManageMyMarket, Eventeny) auto-populates from this public data source. The USDA is actively investing in this data — FY2026 saw $4M in cooperative agreements for SNAP mobile payments at farmers markets, signaling continued federal commitment to keeping the directory current.

User Signal

Manager onboarding friction is identified in the PRD as a critical barrier: "Onboarding completable for all three roles without support intervention." With a 90-day target of 5 markets, every minute of setup friction matters. The USDA directory data also provides SNAP/EBT acceptance status, which directly enriches existing ideas #429 (SNAP/EBT Vendor-Side Mobile Acceptance) and #69 (Manager-verified SNAP/EBT acceptance badge) with authoritative government data.

Technical Opportunity

The USDA REST API endpoint returns structured JSON with location, hours, products, and payment methods. The Go backend can query by latitude/longitude or name during market creation via a single HTTP call. The GraphQL mutation for createMarket can accept optional USDA-sourced defaults. No new infrastructure is needed — this is a lightweight integration point in the existing onboarding flow.

Assessment

Dimension	Score	Rationale
Feasibility	high	Free REST API, single HTTP call, no auth required. Minimal backend work.
Impact	med	Reduces onboarding friction significantly but is a one-time benefit per market, not an ongoing differentiator.
Urgency	med	Most valuable during the growth phase when many new markets are being onboarded. Not blocking for MVP.

Adversarial Review

Strongest objection: The USDA data might be so outdated that it creates more work to correct than to fill in fresh, since many market listings haven't been updated in years.

Rebuttal: The flow is suggestion-based: managers see proposed data and edit before accepting. Even partially correct data (name, address, geo-coordinates) saves time. The alternative — a completely blank form — is strictly worse for the 80%+ of markets that ARE in the directory with at least basic data. A one-time USDA data freshness audit during development can identify which fields are reliably current and which should be shown as "suggested" vs "confirmed."

Suggested Next Step

Audit the USDA API response schema for data quality and field coverage across a sample of 50 markets. Build a Go service function that queries by lat/lng during market creation and returns ranked candidate matches. Design the "suggested profile" review UI in the manager onboarding flow with clear edit affordances.