Parse, validate and format phone numbers worldwide from bundled libphonenumber metadata, with no dependency.
payments ON MAINNET (real money) · 8 live endpoints
| Endpoint | Price | What it answers |
|---|---|---|
GET /country-calling-codes | $0.02 | Look up which regions use a country calling code (+44, +1) or a region's code, dialing prefixes and national prefix. |
GET /phone-compare | $0.02 | Compare two phone number strings: exact match, same national number, short match or different, with an optional region. |
GET /phone-example | $0.02 | Example phone numbers per region and type (fixed line, mobile, toll free, premium) taken from libphonenumber metadata. |
GET /phone-format | $0.02 | Format a phone number as E.164, international, national and RFC3966 tel: URI using the region's numbering-plan rules. |
GET /phone-parse | $0.02 | Parse a phone number (E.164 or national) into country code, national number, region, number type and validity. |
GET /phone-possible-lengths | $0.02 | Possible national phone number lengths for a region overall and per type, with local-only lengths and the E.164 total. |
GET /phone-region-guess | $0.02 | Guess the region from an international +prefix or partial number: calling code, candidate regions and how certain it is. |
GET /phone-validate | $0.02 | Validate a phone number against the numbering plan: possible length, valid pattern, optionally for one region. Syntax only. |
GET /catalog returns this list as JSON. Activity hub · uptime.
Syntax and numbering-plan checks from a bundled libphonenumber metadata snapshot. A valid-looking number is not proof that it is assigned, reachable or belongs to anyone. Not a carrier lookup. Every paid response carries a disclaimer field.