Plans and limits
Two plans. Watch tells you; Guard does something about it. Every cap in one place, so nothing surprises you at two in the morning.
Watch and Guard
| Watch | Guard | Enterprise | |
|---|---|---|---|
| Price | Free | $29 a month, or $20 a month paid yearly | Talk to us |
| Protected numbers | 3 | Unlimited | Unlimited |
| Calls scored per day | 100 | 100,000 | Unlimited |
| Scores, reasons, history | Yes | Yes | Yes |
| Network reputation | Yes | Yes | Yes |
| Alerts by webhook and email | Yes | Yes | Yes |
| Alerts by text and phone call | No | Yes | Yes |
| Live monitor | No | Yes | Yes |
| Ends the call through your platform | No | Yes | Yes |
| The gate on carrier numbers | Scores and hands on; no challenge | Yes | Yes |
| Team, API, CSV export | Yes | Yes | Yes |
The line that matters: on Watch, nothing stops a bad call. You see it, you are told, and it costs what it costs. Guard is where the meter stops running.
The daily allowance
Calls scored per day resets at midnight UTC. Past it, a call is still recorded and allowed. It appears in your log with reasons: ["daily_cap"] and no score, and raises no alert. It is an allowance, not a rate limit: nothing is refused and nothing errors. On Guard the allowance is a hundred thousand a day, which is a flood in itself.
If a payment fails
- You get an email the moment it fails, with a link to update the card.
- Twenty-four hours later, if the account is still past due, it moves to Watch. Nothing is deleted; the numbers, history and settings stay.
- You get a second email saying it moved, and why.
Updating the card and paying the open invoice puts Guard back. Between the failure and the move, Guard keeps working: a card that expired on the wrong night should not be what lets an attack through.
Every limit
| What | Limit | Then |
|---|---|---|
| Events ingested per account | 1,200 a minute | Accepted and dropped; never an error a platform would retry. |
| Turns recorded per call | 3,000 | Further turns dropped with ignored: true. |
| Reads per key | 600 a minute | 429 with retry-after. Each key has its own. |
| Calls listed per request | 200 | Page with before and before_id. |
| Activity events per request | 300 | |
| Alerts per request | 200 | Page with before. |
| Alert cooldown | 15 minutes per type per subject | One alert, with the count in it. |
| Phone calls per day | 3 by default, up to 20 | Texts and email continue. |
| Email addresses for alerts | 20 | |
| Phones for texts or calls | 10 each | Proved with a code, North America. |
| Call ceiling | 1 to 600 minutes | Default 20; call.long_running past it. |
| Spend ceiling per number | $1 to $100,000 an hour | Or derived from a week of history. |
| Manual block | 15 minutes to start | Longer with each further violation, up to a day. |
| A session in the dashboard | 30 days, or 14 unused | |
| Sign-in attempts | 10 wrong per email per 15 minutes | Then a wait. A right password never locks you out. |