Unified Scoring
Every jurisdiction normalized to a consistent 0-100 scale. An 87 in New York means the same as an 87 in Los Angeles.
Restaurant Health Scores.
One API.
Normalized 0-100 inspection scores across 400+ US jurisdictions. Connect once, query everywhere.
GET /v1/restaurants/rst_nyc_29104
{
"id": "rst_nyc_29104",
"name": "Joe's Pizza",
"city": "New York",
"foodsafe_score": 87,
"score_grade": "A",
"last_inspection": "2025-11-15",
"critical_violations": 0
}Trusted by teams building with food safety data
Delivery Platforms
Franchise QA
Real Estate
Insurance
Up and running in minutes
No scraping. No jurisdiction research. No score normalization. We handle all of that so you can ship.
Connect
Get your API key in 30 seconds. No credit card required for the free tier.
Query
Search by restaurant name, address, or coordinates. Fuzzy matching across all jurisdictions.
Score
Get normalized 0-100 scores instantly - comparable across every city and county we cover.
Everything you need. Nothing you don't.
Built for production workloads - batch lookups, webhooks, and historical data included from day one.
400+ Jurisdictions
Counties and cities across 38 states, covering the largest markets in the US food service industry.
Real-Time Updates
Daily syncs from major metro health departments. Scores reflect the most recent inspection data available.
Batch Queries
Look up 500 restaurants in a single request. Optimized for pipelines that need to score entire franchise networks at once.
Webhook Alerts
Get notified when scores change. Subscribe to individual restaurants or entire chains for real-time push notifications.
Historical Data
Up to 24 months of inspection history. Analyze score trends, flag deteriorating locations, and satisfy audit requirements.
Major metros. Growing daily.
38 states and expanding. Coverage is added based on public data availability and developer demand.
Northeast
- New York City, NY
- Philadelphia, PA
- Boston, MA
- Newark, NJ
- Providence, RI
- Hartford, CT
- Baltimore, MD
- Washington, DC
South
- Miami, FL
- Orlando, FL
- Tampa, FL
- Atlanta, GA
- Charlotte, NC
- Nashville, TN
- Houston, TX
- Dallas, TX
- Austin, TX
- San Antonio, TX
Midwest
- Chicago, IL
- Detroit, MI
- Columbus, OH
- Cleveland, OH
- Indianapolis, IN
- Minneapolis, MN
- Kansas City, MO
- St. Louis, MO
West
- Los Angeles, CA
- San Francisco, CA
- San Diego, CA
- Sacramento, CA
- Seattle, WA
- Portland, OR
- Phoenix, AZ
- Las Vegas, NV
- Denver, CO
Straightforward pricing
Start free. Scale as you grow. No hidden fees, no surprise invoices.
Free
$0
500 requests / month
- Single restaurant lookups
- Basic score endpoint
- JSON responses
- Community support
- No credit card required
Starter
$29
/mo
10,000 requests / month
- All free tier features
- Batch queries (up to 100)
- All API endpoints
- 90-day inspection history
- Email support
Most Popular
Pro
$99
/mo
100,000 requests / month
- All Starter features
- Batch queries (up to 500)
- Webhook alerts
- 24-month inspection history
- 99.9% uptime SLA
- Priority support
Need more than 100K requests/month, custom SLAs, or dedicated infrastructure?
Talk to SalesFrequently asked questions
Each health department uses a different inspection scoring system - some use letter grades, others use point deductions from 100, and others use pass/fail with violation counts. We map every raw inspection outcome to a normalized 0-100 scale by analyzing violation severity weights, maximum deduction schedules, and historical grade distributions for each jurisdiction. An 87 on our scale means roughly the same level of food safety risk regardless of where the restaurant is located.
We sync daily with health departments that publish real-time or near-real-time data. For jurisdictions with less frequent publication cycles, we sync on whatever schedule their portal supports - typically weekly. Each API response includes a
data_freshness field showing the timestamp of the last successful sync for that jurisdiction.
Yes. The batch endpoint accepts a list of restaurant IDs or a chain name filter and returns scores across all matching locations. You can also filter by geography, score range, or last inspection date. Chain name matching uses fuzzy logic to handle variations like "McDonald's", "McDonalds", and "Mc Donald's" as the same entity.
The API returns a
404 with a not_found status and a coverage field indicating whether the restaurant's jurisdiction is supported. If the jurisdiction is covered and the restaurant is missing, you can submit a coverage request via the API and we'll add it in the next sync cycle, typically within 24 hours.
Yes. All API keys have access to a sandbox base URL (
sandbox.foodsafescoreapi.com/v1) that returns realistic but synthetic data. Sandbox requests don't count against your monthly quota and include a fixed set of test restaurants documented in the API reference.