Test Your Agent

Talk to your own already-running agent, live, right from this page — no frontend of your own needed yet. This only works if:

1. You've already provisioned an instance and it's active.
2. Your own agent process (built with live-lib's FlowGraph/LiveKitBridgeWorker, running on your own infrastructure) is already running and has dispatched itself into a specific room name — this page doesn't start, manage, or dispatch your agent, it just joins whatever room you tell it to as a human participant. Don't have one running yet? See Minimal working example in the docs for a complete, copy-pasteable script.

Step 1 — Get a test token

Same SigV4-signed call as every other authenticated endpoint in the docs — no separate login, no password:

awscurl --service execute-api --region ap-southeast-1 -X GET \
  "https://api.niuty.com/test-token?instanceId=<instance_id>&roomName=<room_name>&identity=browser-test&expiresInHours=1"

• instanceId — from your /create-instance or /status response.
• roomName — whatever room your own agent process is actually listening on (this is entirely your own agent code's concern, not something niuty assigns).
• identity — optional, defaults to browser-test if omitted.
• expiresInHours — optional, defaults to 1. Accepts anything from 0.1 (6 minutes) up to 168 (7 days) — useful for sessionUrl below when you want a link that stays valid longer than a quick test.

Returns:

{
  "status": "ok",
  "token": "<jwt>",
  "livekitUrl": "wss://<id>.rt.niuty.com",
  "sessionUrl": "https://niuty.com/session?token=<jwt>&livekitUrl=wss%3A%2F%2F<id>.rt.niuty.com"
}

sessionUrl is a ready-to-share link to /session — already URL-encoded, open it and it connects immediately, no paste step. See below for the paste-based flow instead.

Step 2 — Connect

Paste the whole response above into the box below and hit Connect. Your browser will ask for microphone access — allow it, then start talking.

Paste the response from your test-token call