One tool a visitor's AI can call

lookup_venue_context

A visitor’s native AI interprets what they see and asks. NuvoGuide matches those observations to your published catalogue and returns the facts you have approved. The assistant explains them in its own voice. Your venue’s images are not required or requested.

• Call it when a visitor looks at something in an enrolled venue and asks about it.
• Send a visual description, any text read from a label, and the question. Do not send an image, audio, or video.
• A match returns that record's approved facts. Speak them in the assistant's own voice.
• An ambiguous result names the candidates and one distinguishing fact each. Ask which one they mean.
• Unknown means the look is not in the catalogue. Say so. Do not invent a record.

OpenAPI 3.1: http://localhost:3100/api/demo/openapi

Try the demo. It answers from four fictional records.

curl -s http://localhost:3100/api/demo/lookup \
  -H "content-type: application/json" \
  -d "{\"visualDescription\":\"A coffee demonstration booth\",\"visibleText\":\"C12\",\"question\":\"Is there a live demo?\"}"

A private development build can still match from a still photograph when that fallback is switched on. That path is separate from this lookup, and it is not a live Meta Connector.

Example request

Venue context, a visual description, any visible text, and the visitor’s question.

{
  "draft": true,
  "venueId": "venue_demo_expo",
  "visualDescription": "A coffee-equipment demonstration booth with a machine on the counter.",
  "visibleText": "C12",
  "question": "Is there a live demo?"
}

Example responses

matched

{
  "draft": true,
  "status": "matched",
  "objectId": "obj_booth_c12",
  "name": "Northwind Brews demonstration",
  "contentVersion": 1,
  "approvedFacts": [
    "Live demonstration of coffee extraction",
    "Starts at 2:30 PM",
    "Booth C12",
    "Duration 15 minutes"
  ],
  "alternatives": [],
  "assistantInstruction": "Speak in your own voice. Use only these approved facts. Do not add facts that were not returned."
}

ambiguous

{
  "draft": true,
  "status": "ambiguous",
  "objectId": null,
  "contentVersion": 1,
  "approvedFacts": [],
  "alternatives": [
    {
      "objectId": "obj_mug_white",
      "name": "White enamel mug",
      "distinguishingFact": "White enamel camp mug"
    },
    {
      "objectId": "obj_mug_blue",
      "name": "Blue enamel mug",
      "distinguishingFact": "Blue enamel camp mug"
    }
  ],
  "assistantInstruction": "Do not pick a record. Name the alternatives and the distinguishing fact for each, and ask which one the visitor means."
}

unknown

{
  "draft": true,
  "status": "unknown",
  "objectId": null,
  "contentVersion": 1,
  "approvedFacts": [],
  "alternatives": [],
  "message": "This does not appear to be part of the published venue catalogue.",
  "assistantInstruction": "Say that this is not in the venue catalogue. Do not invent an object."
}

error

{
  "draft": true,
  "status": "error",
  "objectId": null,
  "contentVersion": 1,
  "approvedFacts": [],
  "alternatives": [],
  "message": "The request could not be processed.",
  "assistantInstruction": "Say that the lookup failed. Do not guess a record."
}

Semantics

• matched: a particular catalogue record is identified. Use only published facts.
• ambiguous: more than one record remains plausible. Name the alternatives; do not pick silently.
• unknown: the look is not in the published catalogue. Do not invent an object id.
• error: the request cannot be processed. Do not guess a record.

What a connector would register

One REST operation, lookupVenueContext, at POST /api/demo/lookup. The same shapes are available as GET /api/demo/lookup?scenario=matched|ambiguous|unknown|error. The demo has no API key. Account linking would use the connector OAuth flow once access is granted. Visitors would only ever receive a published snapshot.

Integrations

Ready to test: the lookup above, against a fictional catalogue.
Not verified: Meta AI Connectors, Muse, and any claim of device-wide support.
Last reviewed 1 October 2026.

Technical enquiries: contact. Venue pilots: founding venues.