Zero Runtime Cloud

Zero Runtime Cloud hosts and runs your worker on our compute, so you never operate a server. You need an agent project that runs locally.

Run every zeroruntime command from inside your project folder. The CLI keeps your agent, image, and version IDs in zeroruntime.yaml there, so most commands need no flags. See how the CLI tracks state.

Remove the local test invoke

For local testing, use the on_ready callback in serve() to start a playground session when the worker is ready. Remove it in production to avoid automatically creating a new room for every worker. In production, start sessions via zeroruntime invoke CLI, the dispatch API, or telephony routing rules.

def invoke_agent():  
    zeroruntime.invoke(room=Room(playground=True))  

if __name__ == "__main__":
    zeroruntime.serve(MyVoiceAgent, on_ready=invoke_agent)  
    zeroruntime.serve(MyVoiceAgent)  

await zeroruntime.serve(MyVoiceAgent, { 
  on_ready: () => zeroruntime.invoke({ room: Room({ playground: true }) }), 
}); 
await zeroruntime.serve(MyVoiceAgent, {}); 

Initialize the deployment

Register the agent with Zero Runtime Cloud. This writes agent.id and deploy.id to zeroruntime.yaml and generates a Dockerfile if your project doesn’t have one:

zeroruntime init --name my-agent

Please make sure the entry-point file name matches the file specified in the Dockerfile’s CMD.

Deploy

Build the image and deploy it. --env .env also uploads your provider keys as secrets:

zeroruntime up --env .env

Expected output

✓ Agent is up!
  Version ID: v_1o4eux
  Agent ID: ag_53wdl1

The first deploy builds image <agent-id>:v0.0, and each later up builds the next one. See Version Management.

Confirm it's live

zeroruntime version describe

Talk to your agent

Start the agent in a room. The CLI prints a playground link you can open to talk to it:

zeroruntime invoke

Expected output

✓ Agent invoked successfully
  Room ID: <room-id>

Interact with your agent here:
  https://playground.zeroruntime.ai?token=...&meetingId=<room-id>

Ship an update

Changed your code? Run the same command. It builds the next image and creates a new version:

zeroruntime up --env .env

Connect telephony

Deployed a telephony agent but skipped gateway setup? Configure it now so calls reach your deployed agent. Use the Agent ID printed by zeroruntime up (also stored as agent.id in zeroruntime.yaml) wherever an agent ID is required.

Set up inbound calls

1. Create an inbound gateway: the entry point for incoming calls.

Dashboard
API

Copy the Inbound URL from the Zero Runtime dashboard.
Go to Twilio and create a new SIP Trunk.
Go to the Origination section, paste the Inbound URL there, and save it.

Using a different SIP provider? Follow its inbound setup: Telnyx, Vonage, or Plivo.

curl --request POST \
  --url https://api.videosdk.live/v2/sip/inbound-gateways \
  --header 'Authorization: YOUR_ZERORUNTIME_AUTH_TOKEN' \
  --header 'Content-Type: application/json' \
  --data '{ "name": "My Inbound Gateway", "numbers": ["+1234567890"] }'

Then set the origination URI of your Twilio SIP trunk to the inbound gateway hostname (shown in the dashboard), e.g. sip:9WXXXXXXX.sip.videosdk.live.

2. Create a routing rule: connects the inbound gateway to your deployed agent.

Dashboard
API

From your inbound gateway, click Configure rule, then Create new routing rule.
Enter a Routing Rule Name and select API Key authentication.
Choose the Call Direction (Inbound).
Enter the Phone Number and select a Room Type.
Enter your Agent ID and click Save.

curl --request POST \
  --url https://api.videosdk.live/v2/sip/routing-rule \
  --header 'Authorization: YOUR_ZERORUNTIME_AUTH_TOKEN' \
  --header 'Content-Type: application/json' \
  --data '{
    "gatewayId": "gateway_in_123456789",
    "name": "Support Line Rule",
    "numbers": ["+1234567890"],
    "agentId": "ag_53wdl1"
  }'

3. Test it: dial your provider’s phone number from any phone. The agent greets you as soon as the call connects.

Set up outbound calls

1. Create an outbound gateway: lets the agent dial out to the PSTN.

Dashboard
API

In Twilio, open your SIP Trunk and go to the Termination section. Create a Termination URI and add username/password credentials.
Back in the Zero Runtime Dashboard, open the outbound gateway configuration.
Paste the Twilio Termination URI as the address, add the same username/password credentials, and save.

Using a different SIP provider? Follow its outbound setup: Telnyx, Vonage, or Plivo.

curl --request POST \
  --url https://api.videosdk.live/v2/sip/outbound-gateways \
  --header 'Authorization: YOUR_ZERORUNTIME_AUTH_TOKEN' \
  --header 'Content-Type: application/json' \
  --data '{
    "name": "My Outbound Gateway",
    "numbers": ["+12065551234"],
    "address": "sip.myprovider.com",
    "transport": "udp",
    "auth": { "username": "your-username", "password": "your-password" }
  }'

Set address and auth to match your Twilio Termination URI and credentials so outbound calls reach the PSTN.

2. Place a call: trigger a call from the agent. Replace YOUR_ZERORUNTIME_AUTH_TOKEN and routingRuleId with your own.

curl --request POST \
  --url https://api.videosdk.live/v2/sip/call \
  --header 'Authorization: YOUR_ZERORUNTIME_AUTH_TOKEN' \
  --header 'Content-Type: application/json' \
  --data '{
    "sipCallFrom": "+14155550100",
    "sipCallTo": "+14155550199",
    "routingRuleId": "rr_2554md"
  }'

Operate your agent

Versions, secrets, sessions, logs, and scaling down.

CLI Reference

Every command and flag.

Overview

Build

Plugins

Deploy

Ship an update

Connect telephony

Next

Operate your agent

CLI Reference

​Ship an update

​Connect telephony

​Next

Operate your agent

CLI Reference

Ship an update

Connect telephony

Next