# ContextGuide.ai integration map

Version: partner preview, August 2026

| Integration area | Example foundation | Data entering ContextGuide | ContextGuide output |
| --- | --- | --- | --- |
| AI glasses | Android XR and compatible adapters | Camera, microphone, device state | Audio guidance, optional display cue |
| Multimodal AI | Gemini through Firebase AI Logic | Approved image, voice and text context | Structured scene understanding |
| Live conversation | Gemini Live API | Voice turn and active scenario | Low-latency spoken response |
| Outdoor navigation | Google Maps Platform and Places API | Location, destination, route state | Contextual route guidance |
| Spatial understanding | ARCore and partner maps | Pose, anchors, mapped building data | Indoor waypoint and hazard context |
| Public transport | City and operator APIs | Route, stop and vehicle arrival data | Vehicle identification and arrival cue |
| Health awareness | Wear OS and approved device APIs | User-selected wearable signals | Routine prompt or configured escalation |
| Personal services | Android calendar, contacts and approved apps | Explicitly permitted event or contact data | Contextual reminder or contact action |

## Partner interface principles

- Every integration declares its purpose, data fields, update frequency and retention rule.
- A scenario can run in a reduced mode when a partner service is unavailable.
- Transport and building data must include freshness and coverage metadata.
- Health and emergency integrations require separate legal, clinical and regional review.
- Third-party modules cannot bypass ContextGuide safety and accessibility rules.

## Early partner input

We welcome conversations with transport providers, hospitals, shopping centres, accessibility organisations, wearable-device teams and AI-glasses manufacturers. Contact hello@contextguide.net to request a technical workshop.