Skip to main content
Honest status: the interactive capability family this page once advertised is partially available in 0.12. Chat read works. Speak, chat write, screen share and avatar are contract-sealed but not reachable through the API today. The API shape for interactive capabilities is under active design — it is not a straight restoration of the pre-0.12 endpoints.

​
Per-surface status (0.12, verified against the tree)

“Sealed” means the endpoint shape is frozen in the public API contract; it does not mean served. A call to an unmounted surface returns 404 on every deployment.

​
What you can do today

  • Read the meeting chat while a bot is in the room: GET /bots/{platform}/{native_meeting_id}/chat with a bot-scoped API key.
  • Capture and transcribe as usual — the interactive gaps do not affect transcription, recordings, or the transcript API.
Don’t have a key yet? Hosted: sign in at vexa.ai/signin with a Google account and copy your key from your account page — free credit, no card required. Self-hosted: make all prints a key when the stack comes up.

​
Where this is going

The pre-0.12 shape was REST-per-surface (POST /bots/.../speak, /chat, /screen). That design predates the 0.12 agent layer, and the open question is where interactive capabilities belong — bot-level REST, or the Agent API driving the bot’s proven acts layer (cf. the external request to attach an external agent by URL, #333). That design decision is tracked openly; demand for this family is measured and sustained, and comments on the design issue are exactly the evidence the decision consumes.