POST /v1/enrich/restaurant

Every returned restaurant includes vegan_dining.menu: all food dishes, stored prices and ingredients, without drinks or descriptions. No option is required. Search accepts at most 10 restaurants per request. Credits stay unchanged. Google-labeled menus return an empty menu with null counts and excluded: "source_not_permitted".

Ingredients as printed on the restaurant's menu, when listed. May be incomplete. Not for allergy decisions.

Menus deduplicate by normalized dish name. The first stored food row supplies display fields. Original sections are grouped with main courses first; other sections retain stored order, and unknown sections come last. False is_vegan includes unconfirmed classifications. Menus are never truncated: JSON responses above 250 KB return 413 full_menu_too_large; streaming Search emits an error event with status 413. Reduce the Search limit or retrieve restaurants individually.

curl -X POST "https://api.compassfoodtechnologies.com/v1/enrich/restaurant" \
  -H "Content-Type: application/json" \
  -H "X-Compass-API-Key: $COMPASS_API_KEY" \
  -d '{
    "name": "Example Ramen House",
    "address": "123 Example Street, Brooklyn, NY"
  }'

EnrichResponseMatched: 76 contract leaves. A row is one contract leaf. Optional leaves, missing restaurant evidence, and fast mode can omit fields. This count is the schema, not a promise that every response contains every field.

Abridged EnrichResponseMatched example — 31 of 76 contract leaves. Illustrative values, not a live payload.

{
  "compass_request_id": "req_example_ramen_house_enrich",
  "matched": true,
  "identity_status": "resolved",
  "match_confidence": 0.97,
  "compass_id": "cmp_example_ramen_house_001",
  "restaurant": {
    "compass_id": "cmp_example_ramen_house_001",
    "name": "Example Ramen House",
    "vegan_score": {
      "overall": 70,
      "scoring_version": "v5.0-menu",
      "base": 70,
      "vegan_main_count": 4,
      "vegan_dish_count": 6,
      "is_fully_vegan": false,
      "vegan_adj": 0,
      "vegan_adj_reason": "not_enough_reviews",
      "quality_adj": 0,
      "quality_adj_reason": "no_standout",
      "scored_at": "2026-10-23T12:00:00.000Z"
    },
    "vegan_dining": {
      "dishes_availability": "yes",
      "vegan_dish_count": 6,
      "matching_dish_count": 2,
      "matched_dishes": [
        {
          "name": "Shoyu Vegan Ramen",
          "category": "Pasta & Noodles",
          "match_type": "variant",
          "evidence_id": "ev_dish_example_shoyu_vegan_ramen",
          "vegan_basis": "validated_menu_classification"
        },
        {
          "name": "Spicy Miso Vegan Ramen",
          "category": "Pasta & Noodles",
          "match_type": "variant",
          "evidence_id": "ev_dish_example_spicy_miso_vegan_ramen",
          "vegan_basis": "validated_menu_classification"
        }
      ],
      "truncated": false,
      "menu_collected_at": "2026-10-07T16:00:00Z",
      "menu_collected_at_status": "known",
      "match_status": "matched"
    }
  },
  "ai_generated": true
}

HTTP 200 with matched: false means Compass could not confirm the record. compass_id is null. Do not call Decide and do not take the first match_candidates entry.

Name matching ignores case, spacing, and punctuation. When more than one record matches, such as two locations of one chain, identity_status is ambiguous and each candidate includes its stored address.

EnrichResponseUnmatched: 28 contract leaves. A row is one contract leaf. Optional leaves, missing restaurant evidence, and fast mode can omit fields. This count is the schema, not a promise that every response contains every field.

Abridged EnrichResponseUnmatched example — 13 of 28 contract leaves. Illustrative values, not a live payload.

{
  "compass_request_id": "req_example_ramen_house_unmatched",
  "matched": false,
  "match_confidence": 0.41,
  "compass_id": null,
  "match_candidates": [
    {
      "compass_id": "cmp_example_ramen_house_candidate",
      "name": "Example Ramen",
      "match_score": 0.62,
      "address": {
        "street": "100 Example Ave",
        "city": "Portland",
        "state": "OR",
        "postal_code": "97201",
        "country": "US"
      }
    }
  ],
  "ai_generated": true
}

The public compass_id on Search, Enrich, and Decide is currently the Firestore document ID. It is not the immutable compass_place_id.

Within the lifetime of a live record, compass_id stays the same across rescores and re-syncs. After a merge, the old ID keeps resolving only while the redirect alias and the live target both still exist.

Retirement, physical deletion, and a city wipe or rebuild can remove an ID. /v1/changes does not emit merge or redirect events. A deleted event can come from a closed or archived record, a retained deletion tombstone, or a qualifying RETIRED compass_place_id alias. A canonical city wipe removes that city's own records. An alias or tombstone shared with a restaurant that stays is left in place, and the wipe does not write a new deletion marker for a record it removes. The feed is not a complete deletion record.

Store the mapping, re-resolve when you need the current record, and handle an ID that no longer resolves. After a documented city rebuild, reconcile that city's data instead of relying only on /v1/changes.

Pass compass_id to Decide for a fit, not_fit, or unknown verdict per user profile — or see Integration patterns for the full chain.