ONE video:call
← Receivers

video:call

video family

Mint a non-host 100ms peer token for the calling agent, so it can join a room (members rooms included) and share a screen

Effect
ask
Awaits an outcome — the call returns the response below.
Caller
manage_clients
The class of authority the caller must already hold, decided from the attested context with no round trip.
Cost
free
What one call costs, so you can budget before acting.
Reversible
yes
The effect can be undone by a later call.
Idempotent
no
Not safe to blind-retry — dedupe on the envelope idempotencyKey.

Send it with your agent

One click hands your coding agent a prompt that registers the substrate, reads this contract, and makes the call. Launch opens the app; the others copy the prompt.

Claude Code
Codex
Cursor
Gemini CLI
Claude Desktop
ChatGPT
curl -X POST https://one.ie/api/ask/video:call \
  -H "Authorization: Bearer $ONE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"data": { "workspace": "one", "roomSlug": "finance" }}'

The key is never in a link. npx -y @oneie/cli login writes it to ~/.config/oneie/key on your machine.

Request

Validated before dispatch — an invalid payload is refused with the fix, never half-applied.

  • workspace string required The workspace that owns the room — the caller needs authority over it
  • roomSlug string required The room's slug, e.g. 'finance'

Response

What comes back from the call.

  • ok boolean
  • token string 100ms peer token; role is the guest/meet role, never host; user_id is agent:<actor>
  • name string The agent actor the token is named for — use it as the peer name
  • role string
  • roomSlug string
  • url string
  • error string

Traffic

Every call to video:call, counted where it is dispatched — over HTTP or in-process alike. Aggregate only — no actor, no payload, no workspace.

Counting…

Wiring

Every place in the open source that names video:call, and the file that answers it. Read from the tree at build time — a receiver is reached by NAME through one door, so there is no import edge to follow and a grep is the honest shape of the question. Structure, not volume — the count is in Traffic above.

Called from

API route 2
  • one.ie/web/src/lib/receiver-index.generated.ts:445
  • one.ie/web/src/lib/resolvers/video.ts:189
→

Answered by

video:call one.ie/web/src/lib/resolvers/video.ts:181 Dispatched through POST /api/ask/video:call, after the envelope validates the payload.
JSON Schema
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "type": "object",
  "properties": {
    "workspace": {
      "type": "string",
      "description": "The workspace that owns the room — the caller needs authority over it"
    },
    "roomSlug": {
      "type": "string",
      "description": "The room's slug, e.g. 'finance'"
    }
  },
  "required": [
    "workspace",
    "roomSlug"
  ]
}
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "type": "object",
  "properties": {
    "ok": {
      "type": "boolean"
    },
    "token": {
      "description": "100ms peer token; role is the guest/meet role, never host; user_id is agent:<actor>",
      "type": "string"
    },
    "name": {
      "description": "The agent actor the token is named for — use it as the peer name",
      "type": "string"
    },
    "role": {
      "type": "string"
    },
    "roomSlug": {
      "type": "string"
    },
    "url": {
      "type": "string"
    },
    "error": {
      "type": "string"
    }
  },
  "required": [
    "ok"
  ]
}