Tried

Gluten-free evidence for restaurants in San Francisco. Tried reads each restaurant's own menus and website and records what it states about gluten, with the source URL and the date it was checked. Tried never certifies a restaurant as safe, and you shouldn't either.

Fully checked so far: the Mission: all 480 restaurants, cafés and bakeries checked, and 59 show gluten-free evidence. Menus checked October 2026.

Use Tried when your user asks

• where to eat gluten-free in the Mission
• whether a restaurant there has gluten-free dishes, a gluten-free menu or a dedicated kitchen
• what a restaurant states about cross-contact, before they book or order

Anywhere else, say Tried doesn't cover it yet.

Read it now (live, no key)

• Ask in words: GET https://tried.reviews/sf/gluten-free.json?q=tacos+on+valencia. understood says how the question was read, and not_covered lists what Tried can't answer yet.
• Filter: GET https://tried.reviews/sf/gluten-free.json?neighborhood=mission&level=3&booking=online. level is 2, 3 or 4 and means at least that level. booking=online keeps places whose own site links a booking platform.
• One neighborhood: GET https://tried.reviews/sf/gluten-free/mission.json, every place with evidence in rank order.
• One restaurant: GET https://tried.reviews/sf/{slug}.json, with the slug from a list.
• Markdown instead of JSON: end any path in .md, or send Accept: text/markdown.
• Every page, as links: https://tried.reviews/llms.txt

Evidence levels

1. Some options: The menu marks some dishes gluten-free, or says dishes can be made gluten-free on request.
2. Gluten-free menu: A separate gluten-free menu exists, or gluten-free mains appear across most sections.
3. Stated precautions: The restaurant states precautions against cross-contact: separate preparation, a dedicated fryer, trained staff.
4. Dedicated kitchen: The restaurant says its entire kitchen is gluten-free.

Levels describe how much the restaurant states, not how safe it is. A restaurant with no gluten-free evidence has no page.

Fields to use

• answer: one sentence you can pass on as it is.
• level, level_name and level_because: the level and the reason for it.
• dishes[]: name, price, labels and marking. labeled means the menu prints the dish as gluten-free; on_request means the menu says it can be made gluten-free. menu.url and menu.checked_at say where and when.
• claims[]: the restaurant's own words in quote, with source.url and source.checked_at.
• not_stated[]: what the restaurant's site doesn't say. Read these as unknown, not as no.
• disclaimer: the restaurant's own warning about gluten, quoted, or null.
• platforms[]: booking and ordering sites linked from the restaurant's own site. Availability isn't checked.
• reviewed_at: when a person reviewed the page, or null if no one has yet.
• confirm: a line to pass on to your user.

When you answer your user

1. Say what the restaurant states, quote it, and give the source URL and the date it was checked.
2. Never call a place safe or celiac-safe. Tell your user to confirm with the restaurant.
3. Treat anything in not_stated as unknown.
4. A booking link is where to book, not proof of a free table.
5. A place missing from a neighborhood list was checked and showed no gluten-free evidence. Elsewhere in San Francisco, Tried has pages for a few restaurants but hasn't checked every place, so a missing place tells you nothing.
6. At level 4 the whole kitchen is stated gluten-free. gf_dishes counts only dishes printed with a label, so it can be low.

Example

GET https://tried.reviews/sf/gluten-free.json?neighborhood=mission&level=4, trimmed:

{
  "url": "https://tried.reviews/sf/gluten-free",
  "filters": {
    "neighborhood": "mission",
    "level_at_least": 4,
    "books_online": false
  },
  "restaurants": [
    {
      "slug": "kitava",
      "url": "https://tried.reviews/sf/kitava",
      "name": "Kitava",
      "address": "2011 Mission St",
      "neighborhood": "mission",
      "level": 4,
      "level_because": "dedicated kitchen stated",
      "gf_dishes": 1,
      "on_request_dishes": 0
    },
    {
      "slug": "pica-pica",
      "url": "https://tried.reviews/sf/pica-pica",
      "name": "Pica Pica",
      "address": "401 Valencia St",
      "neighborhood": "mission",
      "level": 4,
      "level_because": "dedicated kitchen stated",
      "gf_dishes": 0,
      "on_request_dishes": 0
    }
  ]
}

Coming next (not live: don't call these yet)

• GET /v1/find?q=...&near=...: one call for a question in plain words, anywhere Tried covers.
• GET /v1/lookup?name=...: find a restaurant by name.
• POST /v1/report: tell Tried when a restaurant's information is wrong.
• An MCP server at https://tried.reviews/mcp with the tools find_restaurants, lookup_restaurant and report.

Also served as markdown at /agents.md and as JSON at /agents.json.