Spam and call-flood protectionfor Vapi assistants.
Connect with an API key. Every call your assistant takes is scored against traffic from every protected number, with what it cost by part, and you're told to hang up before the meter runs.
Three numbers free. About two minutes to connect.
Why Vapi assistants get flooded.
Anyone can dial it
Your assistant answers every call. A script can place a thousand.
The bill climbs while it rings
Every minute is billed to you, whoever was on the line.
Three ways in.
Start with the first. Each adds to the last.
An API key
Scores, alerts and cost on every call. No code, two minutes.
- Settings
- API keys
- Copy the private key
- Connections
- Vapi
- Paste it
A server URL
The same, scored while the call is happening.
- Settings
- Live events
- Copy your URL
- Your assistant
- Advanced
- Server URL
- Paste it
- Your assistant
- Server messages
- Turn on status, speech, transcript and end-of-call report
The gate
Suspicious callers stopped before your assistant answers.
- Numbers
- Your number
- Pick the carrier. Destination:api.vapi.ai/twilio/inbound_call
- Your number
- Voice settings
- Paste the two URLs shown
Numbers imported from Twilio, Telnyx, SignalWire or Vonage. Part of Guard.
What you see for every call.
Inputs are phone numbers, timestamps and the turn events Vapi already emits. Never audio, never words.
Cost by part
Model, speech, transcription, carrier and Vapi's own fee, per call, as Vapi reports them.
Tokens
Input and output per call. The number that runs away when a caller keeps the assistant talking.
Who spoke when
Each turn's length in time and words, and whether it was cut off. Never the words themselves.
The caller's history
Whether this number has hit other protected agents, and how recently.
A score and a verdict
Every call, inbound or outbound, with the reasons. Alerts by webhook, email, SMS or a phone call.
An export
Your calls as CSV whenever you want them, on any plan.
Questions people ask first.
- Do I need to change my Vapi assistant?
- No. The API key path reads calls from Vapi's API and touches nothing. The server URL is optional, and if you already have one you forward to ours from it. Your assistant answers exactly as before.
- Does Murusai hear the calls?
- No. It never receives audio. On the API key path it reads Vapi's record of the call: numbers, timing, cost, tokens and the length of each turn. On the server URL path, transcripts are measured and dropped as they arrive.
- What happens if Murusai goes down?
- Nothing, to your calls. Vapi's server messages are fire-and-forget, imports resume where they left off, and the gate's carrier fallback sends calls straight to Vapi. Murusai is behind the number, never in the call path.
- Does it work with numbers bought inside Vapi?
- Yes: scoring, alerts, cost, tokens and the live monitor all work on any Vapi number. Only the gate needs a number imported from a carrier, because it answers the carrier's webhook before Vapi does.
- Does it cover outbound calls?
- Yes. Turn on Watch outbound on a number and the calls your assistant places are scored too. A form that dials people back is abused the same way a public number is.
- What does it cost?
- Watch is free for three numbers, for as long as you like, with alerts on every channel. Guard is $29 a month for unlimited numbers and calls, the gate, and incident reports. There are no per-call charges on either plan.
- Is Murusai affiliated with Vapi?
- No. Vapi is an independent company and its name belongs to it. Murusai works with Vapi's public API and server messages, the same ones available to any customer.
Three numbers, free, for as long as you like.
An API key and two minutes. Nothing changes about how your assistant answers.