One API call that says whether to contact this number, right now
Carrier, spam reputation, SMS capability, and the calling-window check in a single live read, before anyone dials.
4:40pm, the dial report is a mess again
An agent dials a number your list called clean this morning and gets a disconnect tone. Another agent's caller ID is already flagged 'Spam Likely' before the call connects. Somewhere in the stack, a text hit a landline. Nobody scrubbing four different vendors caught any of it before the touch.
How it works
Send the number
One API or MCP call from your dialer, CRM, or agent step. A number in, nothing else to wire up.
The check runs
Every component runs in one dip against the live network, not a cached table someone scrubbed last quarter.
The verdict comes back
Component by component, each with its own evidence: carrier, spam, SMS-capability, calling window, and where applicable, the compliance checks.
Act before the call connects
Route, hold, or skip the touch on the verdict. The deliverability half runs live today on the MCP server.
What the check returns
Line type & SMS-capability
Know if a number can take a text before you send one.
Live todaySpam reputation
See if a number is already flagged before your caller ID takes the hit.
Live todayCalling-window flag
Recipient-local time checked against the 8am–9pm window before you dial.
Live todayLitigator flag
Numbers tied to serial TCPA litigation flagged before a human ever calls. Founding customers first.
Reassigned-number check
An FCC-based check returning an evidence bundle — query id, database version, timestamp. Founding customers first.
DNC scrubbing on your SAN
Federal DNC scrubbing runs against your own FTC subscription — your SAN, your subscription — we do the work.
One call, not four vendors
Carrier, messaging, spam, and compliance checks in a single live read instead of a vendor scramble.
MCP-native
A live MCP server your agent can call directly. Built for Claude Code, Cursor, and n8n.
Evidence with every verdict
Each component returns its own proof, logged, so you can show your work later.
Check at the moment of contact, not on a quarterly cleanse
Fresh or nothing — a phone-data answer is only worth the moment it was read. A number cleaned in January and dialed in April is an uncleaned number. Litigator status changes, numbers get reassigned, spam flags appear, and DNC status shifts between cleanses, not on your schedule. So the check runs at the moment you are about to dial or text. It is not stored and hoped.
Who it is for
Dialer & lead-gen ops
The team watching connect rates sag every cycle between list cleanses now checks at the moment of the dial instead.
AI-outreach platforms
An agent that calls or texts on your behalf checks safe-to-contact itself, mid-flow, before it acts.
Fraud & risk teams
A team that already distrusts every list they're handed gets a live read they can verify themselves.
Compliance-adjacent ops leads
The person who dreads the quarterly TCPA review gets an evidence bundle behind every touch instead of a shrug.
What this replaces
Most teams stitch together a routing-data API, a daily-batch carrier database, and a compliance suite, and still ship bad touches. This is what changes when one call replaces four.
| The four-vendor scramble | VeriRoute Intel | |
|---|---|---|
| Data freshness | Daily-batch database, refreshed on a schedule | Live read of the network on every query |
| What it answers | How does this number route | Should I contact this number, right now |
| Spam reputation | Most routing-data vendors carry none | Returned on every check |
| Calling-window check | Not offered | Recipient-local time against the 8am–9pm window |
| Reassigned-number evidence | A bare registry ping, no evidence bundle | Query id, database version, and timestamp returned |
| Vendors required | Four separate tools to stitch together | One call |
Compliance components go to founding customers first; the deliverability checks above run live today.
Get founding access before this opens to everyone
The founding list gets you the compliance half first and helps shape the tiers around real volume.
- Founding-customer access to the litigator flag and reassigned-number check
- DNC scrubbing set up against your own SAN
- The deliverability checks — carrier, spam, calling window — available on the live MCP server now
- An evidence bundle behind every verdict
- First look when the founding offer opens
The founding list gets you in today. Sign up, and you hear first when it opens. The founding offer is announced to the list first, at launch.
The founding list is a signup form, not a commitment. A reply to any email we send reaches a person.
Frequently Asked Questions
Why does DNC scrubbing need my own SAN?
The law requires the DNC subscription to belong to the calling party, not to us. Your SAN, your subscription — we do the work of running the check against it.
What's in the evidence bundle?
Each reassigned-number check returns a query id, database version, and timestamp — a record you can point to. It supports your own 47 CFR 64.1200(m) safe-harbor defense. The burden of proof stays yours, our audit trail carries it.
Is this legal advice, or does it make me compliant?
No. This is not legal advice and it does not make you compliant on its own. It gives you an evidence trail to support your own compliance process.
What can I actually run today?
The deliverability half: carrier, spam reputation, SMS-capability, and the recipient-local calling-window flag, live on the MCP server right now.
Can my AI agent call this directly?
Yes. VRI runs a live MCP server with agent-callable tools, built for Claude Code, Cursor, and n8n. Your agent checks safe-to-contact mid-flow.
How do I get this today?
Sign up for the founding list on this page. That's the only way in right now, and you hear first when the founding offer opens.
What does it cost?
The founding offer is announced to the list first, at launch. There's nothing to quote before that.
Why check at the moment of contact instead of a quarterly cleanse?
A number cleaned in January and dialed in April is an uncleaned number. Ports, reassignments, and spam flags happen between cleanses, so the check has to happen at the moment of contact.
What happens to my signup information?
It's used only to size founding tiers to real volume — calls and texts in a typical month, your use case, and whether you hold a SAN. It's never sold, and shared only with the processors that run the service.
Who is this for?
Ops and dev leads at lead-gen shops, dialers, and AI-outreach platforms running calls and texts at volume who today scrub lists across multiple vendors and still ship bad touches.
Do I need to already hold an FTC SAN?
No. The signup form asks whether you hold one — yes, no, or not sure — so founding access can be set up correctly either way.
What if this doesn't fit how my stack is set up?
The founding list is a signup form, not a commitment. A reply to any email we send reaches a person.
Know before you dial. Sign up for founding access.
The founding list gets the compliance checks first and hears first when the offer opens.
Sign UpA reply to any email we send reaches a person.
This page describes the product as it works today; individual results depend on your own use case and volume. The deliverability checks (line type, spam reputation, calling window) run live today; the compliance checks (litigator flag, reassigned-number evidence bundle, DNC scrubbing through your own FTC SAN) go to founding customers first. This is not legal advice; the evidence bundle supports your own 47 CFR 64.1200(m) safe-harbor defense — the burden of proof remains yours.