Phone Validation & Routing Intelligence
Pricing
from $1.00 / 1,000 phone routing decisions
Phone Validation & Routing Intelligence
Validate and normalize phone numbers, identify country and line type, and apply deterministic routing policy with ACCEPT, REVIEW, or REJECT decisions.
Pricing
from $1.00 / 1,000 phone routing decisions
Rating
0.0
(0)
Developer
smile flow
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
a day ago
Last modified
Categories
Share
Turn raw phone numbers into deterministic routing decisions using libphonenumber.
Output
Each supplied phone number returns a dataset row containing:
ACCEPT / REVIEW / REJECT;- reason codes;
- E.164 normalization;
- validity and possibility;
- ISO country and calling code;
- line type;
- carrier metadata when available;
- location and timezone metadata;
- explicit
deliverable: nullandported: nullboundaries.
No LLM is used. This Actor does not claim live reachability, current carrier after portability, or porting status.
Inputs
Use exactly one of:
phonefor one number;phonesfor a JSON batch;csvfor CSV text containing a phone column.
Optional policy fields:
default_region;expected_country;allowed_line_types;phone_columnfor CSV.
Decision contract
- REJECT — unparsable, impossible/invalid, or excluded line type.
- REVIEW — valid but inconsistent with
expected_country. - ACCEPT — valid and all supplied routing policies pass.
Pricing
Pay per event: $0.001 per phone routing decision.
The decision itself is the product, so valid and rejected numbers are both billable when processed.
Integrity boundary
deliverable and ported intentionally remain null. Carrier metadata comes from numbering-plan metadata and is not guaranteed to represent the current carrier after number portability.
