- Resolve candidates (products / venues / facilities)
- Select a candidate (user confirmation or programmatic choice)
- Create an intent referencing the canonical ID (e.g.,
product_id,venue_id,facility_id)
Resolve a product
POST /resolve/products
Return canonical product candidates (optionally across multiple merchants).
Request Body
Human-friendly query like “PS5 Pro” or a model name.
Optional identifiers like GTIN/UPC/SKU.
Optional allowlist of merchants (e.g.,
["target", "bestbuy", "walmart"]).Maximum number of candidates to return.
Example
Response (example)
Resolve a restaurant/venue
POST /resolve/venues
Return canonical venue candidates for reservations.
Request Body
Venue name or partial name (e.g., “Nopa”).
Location constraint.
City name (recommended if you don’t have lat/lng).
Latitude for geo search.
Longitude for geo search.
Search radius in miles (required for lat/lng searches).
Optional allowlist (e.g.,
["resy", "opentable"]).Example
Response (example)
Resolve an appointment facility
POST /resolve/appointment-facilities
Return canonical facilities for appointment-based intents (passport, DMV, etc.).
Request Body
Appointment kind (e.g.,
passport, dmv).Country code (e.g.,
US).Location constraint (geo or city/state).
Latitude.
Longitude.
Radius in miles.
Optional allowlist of providers relevant to the kind (varies by region).