Quickstart
An empty account to a scored call, in the order the dashboard walks you through it. Ten minutes if your agent is on a platform; about the same if it is not.
- Create an account
app.murusai.com/signup. Watch is free for three numbers, no card. Your API key is shown once at the end; put it somewhere safe. If you lose it, the dashboard will make you a new one, not find the old one.
- Get calls to us
One of three, depending on where your agent lives.
Your agent is on a platform
Connections → pick Vapi, Retell, ElevenLabs or Synthflow → paste an API key from that platform. We find your numbers and start importing calls within a minute. The connection page has the exact clicks for each platform, and the optional live path, a webhook URL you paste into the platform so calls are scored while they run rather than after.
Your agent is your own code
Post two events per call. The first is scored on the spot and answers with the score.
When a call arrivesShell curl -X POST https://api.murusai.com/v1/events \ -H "Authorization: Bearer $MURUSAI_KEY" \ -H "Content-Type: application/json" \ -d '{ "type": "call.started", "call_id": "CA7f3e2a91c04b", "to": "+14155550100", "from": "+15125550142" }'When it endsShell curl -X POST https://api.murusai.com/v1/events \ -H "Authorization: Bearer $MURUSAI_KEY" \ -H "Content-Type: application/json" \ -d '{ "type": "call.ended", "call_id": "CA7f3e2a91c04b", "cost": 0.41 }'The first start for a number adds it as a protected number. Everything you can send is on events; if you would rather ask before you answer, that is score.
Your number is on a carrier
Numbers → add it → point the carrier's voice webhook at the URL shown. Every call is scored before your agent hears it, and on Guard a caller who looks wrong is challenged. Walkthroughs for Twilio and Vonage.
- Say where alerts go
Settings → Alerts. Email is on already, to the address you signed up with. Add a webhook URL if you want alerts in your own systems; the payload and signature are on webhooks. Texts and phone calls are part of Guard and go only to a phone you have proved with a code.
- Read the first score
The Activity page shows calls as they land. Each one has a score, our recommended action, and reasons; how scoring works says what they mean. Or ask the API:
The last few callsShell curl "https://api.murusai.com/v1/calls?limit=5" \ -H "Authorization: Bearer $MURUSAI_KEY"The first few days are quiet on purpose. Volume baselines need two weeks of a number's own history before they fire; the caller and network checks work from the first call. - When you want us to act
Watch tells you. Guard does something about it: ends a call through the platform it came from, refuses a caller at the gate before your agent answers, and pages you by text or phone at three in the morning. Billing → Turn on Guard;
$29a month, or$20a month paid yearly. Plans and limits has the whole table.
Where to go from here
- Your own stack: which of score, events and the gate to use, and when.
- The API reference: every endpoint, every field.
- Alerts: what fires, how bad it has to be, and where it goes.