Protocol overview
The Extentos V1 wire format that decouples the SDK from vendor-specific glasses APIs.
Coming soon. High-level overview of the protocol. Full spec ships once the protocol is stable enough for third parties to implement.
What this page will cover
- What the protocol is and what it solves
- Capability negotiation
- Versioning policy
- Why most users never need to read this
Architecture
How Extentos fits together — the AI agent, the MCP server with 18 deterministic tools, the Android and iOS native libraries, the three transport implementations (real Meta DAT, browser simulator, local Mock Device Kit), the Extentos backend, and the AppSpec contract that ties them all together. One diagram and the data flow of a typical development loop, end to end.
Capabilities
The Extentos capability vocabulary — vendor-agnostic primitives (capture_photo, capture_video, record_audio, speak_text, voice_command, tap, double_tap, sensor reads, hardware events) that an AppSpec composes from. How abstract capabilities translate to platform-specific calls on iOS and Android, how permissions derive automatically, how validation negotiates against per-vendor manifests, and why a shared vocabulary plus a standard transport interface is what makes the same code run across Meta Ray-Ban, Mentra G1, Android XR, and future smart-glasses vendors.