DEV Community

Cover image for I built an accessibility data API because every restaurant app ignores wheelchair users
Dave Sirota
Dave Sirota

Posted on

I built an accessibility data API because every restaurant app ignores wheelchair users

#api #saas #webdev #mcp

Every restaurant app tells you the wait time, the Yelp rating, the Instagram vibe. None of them tell you if you can get through the front door in a wheelchair.

That's the problem ROLLIN solves. We score 56,000+ restaurants across 6 US states on actual wheelchair accessibility — level entry, accessible restrooms, parking, wide aisles, elevator access. Every location gets a 0-100 score based on verified, multi-source data.

Today I'm sharing the API that powers it.

The API

Base URL: https://joinrollin.com/api/v1

Search accessible locations:

curl "https://joinrollin.com/api/v1/locations?lat=40.7128&lng=-74.0060&radius=2&min_score=70" \
  -H "X-Api-Key: YOUR_KEY"
Enter fullscreen mode Exit fullscreen mode 
{
  "success": true,
  "count": 23,
  "next_cursor": null,
  "results": [
    {
      "name": "Blue Ribbon Sushi",
      "score": 87,
      "score_label": "Good",
      "features": {
        "wheelchair_entry": true,
        "accessible_restroom": true,
        "level_entry": true,
        "accessible_parking": false,
        "wide_aisles": true,
        "elevator": null
      },
      "distance_miles": 0.3,
      "verified": true
    }
  ]
}
Enter fullscreen mode Exit fullscreen mode

That's real data. Not mocked, not a demo. 56K scored locations, live right now.

What you can build with it

Some ideas we're genuinely excited about:

  • Travel apps — add an accessibility layer to trip planning
  • Restaurant discovery — filter by "actually accessible," not just "ADA compliant" (there's a huge difference)
  • Navigation apps — route wheelchair users to places they can actually enter
  • Corporate tools — help companies pick accessible venues for team events
  • Healthcare platforms — recommend accessible dining near hospitals and rehab centers

Why this data matters

There are 5.5 million wheelchair users in the US. Most of them have learned not to trust "accessible" labels because the bar is so low. A single grab bar in a bathroom technically qualifies. That doesn't help someone who can't get past the front step.

ROLLIN scores are different. We check 6 specific physical features, cross-reference multiple data sources, and weight them by actual impact. A restaurant with a ramped entrance and accessible restroom scores differently than one with just a parking spot. The scores evolve as we get more data.

Get a key in 30 seconds

  1. Go to joinrollin.com/portal.html
  2. Create an account
  3. Generate a free API key

Free tier: 10 requests/min, 1,000/month. Enough to prototype anything.

Full docs: joinrollin.com/developers.html

Endpoints

Endpoint What it does
GET /v1/locations Search by coordinates, radius, score, cuisine
GET /v1/locations/:id Full detail for one location
GET /v1/regions List coverage areas and location counts
POST /v1/feedback Submit accessibility corrections
GET /v1/score/:id Detailed scoring breakdown (Business+)

Already happening

Someone grabbed a free key today, built a Python SDK, and had it published on GitHub within hours. That's exactly the kind of energy we want around this.

If you build something, I want to hear about it. Drop a comment or reach out — projects@stacklinestudio.com

Nobody should have to call ahead to ask if they can get into a restaurant. That's the system we're fixing.

Top comments (0)