voice agents

start a web call

start a voice-agent call and return the credentials a browser joins it with over webrtc. media flows browser ↔ agent directly. two ways in: agentId with an api key that has the agent scope starts the call in one hop — the call id is minted inside this request, so the agent’s before-call tools receive it as {call_id} before you see it in the response. accessToken from /v1/register-call starts the call under the call_id that response already gave you, needs no api key, and is what to use when a before-call tool has to recognise the id, or when the page starts the call itself. either way the agent must be deployed and the returned callId identifies the call in conversations and usage.

POST

webcall

curl --request POST \
  --url https://silk-api.rumik.ai/v1/webcall \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "agentId": "ua_fe3277d8"
}
'

{
  "token": "<string>",
  "host": "wss://livekit.rumik.ai",
  "roomName": "call-891e23fe503944c28dbf5e5a2a105190",
  "callId": "3c90c3cc-0d44-4b50-8888-8dd25736052a"
}

{
  "error": "<string>",
  "code": "<string>"
}

{
  "error": "<string>",
  "code": "<string>"
}

{
  "error": "<string>",
  "code": "<string>"
}

{
  "error": "<string>",
  "code": "<string>"
}

{
  "error": "<string>",
  "code": "<string>"
}

{
  "error": "<string>",
  "code": "<string>"
}

{
  "error": "<string>",
  "code": "<string>"
}

{
  "error": "<string>",
  "code": "<string>"
}

{
  "error": "<string>",
  "code": "<string>"
}

Authorizations

Authorization

string

header

required

your rumik api key, e.g. rk_live_.... create one in the rumik dashboard.

Body

application/json

Option 1
Option 2

exactly one of agentId or accessToken.

agentId

string

required

the agent to run — its uuid or its ua_… handle. agent_id is accepted too. needs your api key in Authorization.

Example:

"ua_fe3277d8"

accessToken

string

the single-use wct_ token from /v1/register-call. it is the credential on its own — no api key — and the call starts under that response's call_id. access_token is accepted too.

Example:

"wct_9f8c2b1e4d5a4e6fa7b8c9d0e1f2a3b4"

Response

the call started; join with these credentials.

token

string

short-lived livekit access token for the browser to join with.

host

string

livekit websocket url to connect to.

Example:

"wss://livekit.rumik.ai"

roomName

string

the room created for this call.

Example:

"call-891e23fe503944c28dbf5e5a2a105190"

callId

string<uuid>

the call id, as shown in conversations and usage, and what your tools receive as {call_id}. for a registered call it is the call_id register-call already gave you.

curl --request POST \
  --url https://silk-api.rumik.ai/v1/webcall \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "agentId": "ua_fe3277d8"
}
'

{
  "token": "<string>",
  "host": "wss://livekit.rumik.ai",
  "roomName": "call-891e23fe503944c28dbf5e5a2a105190",
  "callId": "3c90c3cc-0d44-4b50-8888-8dd25736052a"
}

{
  "error": "<string>",
  "code": "<string>"
}

{
  "error": "<string>",
  "code": "<string>"
}

{
  "error": "<string>",
  "code": "<string>"
}

{
  "error": "<string>",
  "code": "<string>"
}

{
  "error": "<string>",
  "code": "<string>"
}

{
  "error": "<string>",
  "code": "<string>"
}

{
  "error": "<string>",
  "code": "<string>"
}

{
  "error": "<string>",
  "code": "<string>"
}

{
  "error": "<string>",
  "code": "<string>"
}

documentation

sdk

integrations

cookbook

api reference

start a web call

Authorizations

Body

Response