Events are the structured action stream. Every event is anchored to a frame and to aDocumentation Index
Fetch the complete documentation index at: https://docs.nusomi.com/llms.txt
Use this file to discover all available pages before exploring further.
t_ms offset in its session.
Query events
Query
| Param | Notes |
|---|---|
type | One or more event types. Repeat for multiple. |
t_ms.gte / t_ms.lte | Time-range filter. |
frame_id | Restrict to events on a specific frame. |
confidence.gte | Drop low-confidence events (e.g. 0.7). |
include | frame to embed each event’s frame inline. |
order | asc (default) | desc. |
limit | 1–1000. Default 200. |
cursor | From the previous response’s next_cursor. |
Response
Event types
See frames & events for the full type table. Thepayload shape is type-discriminated.
Emit an event
t_ms is optional. If omitted, the server uses the current wall clock relative to started_at.
Batch
Stream events
event: <name> + data: <json>. See streaming for details.
Event ordering
Events within a session are totally ordered by(t_ms, evt_id). Two events sharing t_ms are ordered by id. The SDK preserves this order automatically.
Confidence
Events extracted from accessibility trees haveconfidence: 0.99+. Vision-only events (Citrix, RDP, canvas-based UIs) typically land between 0.7 and 0.95. Filter with confidence.gte=0.9 if you want to drop the noisier tail.