Neutrino API
DATA · DATA & ANALYTICS
Phone validation, email cleaning, IP geolocation, and blocklist checks on their key.
Connecting Neutrino API in practice
Neutrino API meters each endpoint separately rather than the account as a whole, so the free plan is roughly 10 to 25 requests a day for each individual API and even a paid tier gives Browser Bot 100 calls a day where Email Validate gets 10,000 on the same $10 plan. Authentication is a pair — a static user-id plus an api-key — and in header form the two are concatenated as `API-Key: your-user-id:your-api-key`.
Scopes that draw scrutiny
user-id + api-keyBoth are required on every call and neither carries scopes. The user ID is static and cannot be changed, so rotating a compromised credential means rotating the key and leaving the account identifier in place.
Rate limits
- Free plan: around 10 to 25 requests per day, varying by which API, and it does not expire.
- Daily quotas are per API and per tier: Email Validate 10K / 100K / 1M and IP Info 10K / 100K / 1M across the $10, $50 and $250 tiers, while Browser Bot is 100 / 1K / 10K.
- Daily limits reset every 24 hours at midnight in the account’s configured timezone.
- Accounts without overage enabled get some temporary bursting above a percentage of the plan limit before requests start erroring.
Worth knowing
- Quota is per endpoint, so a plan sized for address validation says nothing about how many Browser Bot calls the same plan allows.
- Credentials may be sent as POST fields, GET query parameters or HTTP headers, and the GET form puts both the user ID and the key in the URL.
- On-demand billing from $0.000080 per request exists alongside the plans, and telephony calls are priced separately again (HLR $0.0070, SMS from $0.0150, voice from $0.0200), so cost per agent action depends on which API it picked.
- Responses can be reshaped with output-format (JSON or XML) and output-case (kebab, camel or snake); kebab-case is the default, which breaks naive struct mapping.
Checked against API basics (2026-09-29), Plans and daily limits (2026-09-29)
What an agent can do
Each action is granted on its own. An agent allowed to read is not thereby allowed to write, and the scope beside each row is what the acting user must have connected for it to run at all.
Often connected alongside
Put Neutrino API behind one governed endpoint.
Same permissions, same audit trail, whatever else you connect next.