Pre-registered benchmark — phone validation APIs
Every phone-validation API claims ~99% accuracy. No one has ever published a test.
We're running 1,000 phone numbers with known ground truth through 1Lookup, Trestle, Twilio Lookup, and NumVerify — methodology frozen before results, dataset and scoring scripts public. Then we're launching the API we wished existed: phone, email, and IP validation with published accuracy and billing terms you can hold us to.
Benchmark results + early API access. One email when results drop — nothing else.
| Vendor | Published benchmark | Measured accuracy |
|---|---|---|
| 1Lookup | none found | pending |
| Trestle | none found | pending |
| Twilio Lookup | none found | pending |
| NumVerify | none found | pending |
| Boundstone | will publish — win or lose | |
methodology frozen before any vendor is queried — read it
vendors invited to dispute before publication
What we're building
One credit system across the three checks every outbound and signup flow needs. Bulk CSV, REST API, and a dashboard — not just an endpoint for your dev team.
Phone
Line type, carrier, and ported status from licensed carrier data — plus live liveness checks where they actually work. The coverage page is generated from our routing table: the countries list is the actual list.
Syntax, MX, and SMTP verification with disposable and catch-all detection, run on our own probe infrastructure.
IP
Geolocation, proxy / VPN / Tor detection, and a risk score from licensed databases — catch fake signups before they hit your CRM.
Billing promises that live in the Terms
Everyone says "no hidden fees." We put the promises where they're enforceable.
- Credits never expire.
- Cancel is a button, not a support ticket.
- 30-day money-back guarantee, no questions.
- Free tier: 250 credits a month, forever.
- Public status page and published support response times.
These are clauses in our Terms of Service — not decoration in a footer. If we break one, you have the receipt.