risk data for machine payments
Endpoint
netintel.dev/phone-intel/analyze
Parse and validate any phone number in any format, identify its country and line type (mobile/landline/VOIP/toll-free/premium for NANP + UK numbers; other countries return line_type unknown), and return all standard format variants (E.164, international, national) — catches fictional/unassigned NANP numbers (555 area code, 555-01XX range) so agents can validate contacts and normalize phone data without a paid telecom API.
Score
The score is built from observations we collect ourselves: how the endpoint responds, what the envelope contains, how stable the price and the recipient are, who pays and how often. It is deterministic — the same input always produces the same result.
We do not publish the exact methodology yet. If you own this endpoint, write to us and we will show you, item by item, what drags the score down.
Recent probes
| When | Code | Latency | Scheme and network | Recipient | Price | Findings |
|---|---|---|---|---|---|---|
| 5h ago | 402 | 159 ms | exact eip155:8453 |
0xdaDc…b9Df | 0.050000 | clean |
| 4d ago | 402 | 294 ms | exact eip155:8453 |
0xdaDc…b9Df | 0.050000 | clean |
| 4d ago | 402 | 248 ms | exact eip155:8453 |
0xdaDc…b9Df | 0.050000 | clean |
Reference
| URL | https://netintel.dev/phone-intel/analyze |
| Sources | well-known |
| Recipient per catalogue | 0xdaDc335482AD545296Fd7b28518A251fFCbEb9Df |
| Machine access | /v1/endpoint · /full · badge |
Is this your endpoint?
The score is built only from public observations. If something we recorded is wrong — say our prober hit you during maintenance — write to us. We will recheck and publish your reply next to the score.
We do not delete accurate observations. The prober makes at most one request per second per host and only asks for the payment challenge — it never pays and never takes content.