canonical: https://jentic.com/apis/neutrinoapi.com/neutrinoapi-com # Neutrino API Neutrino API is a general-purpose developer toolbox API exposing a curated subset of validation and lookup endpoints. This specification covers four core tools - phone validation, email validation, IP info, and URL info - used to clean contact data, geolocate IPs, and inspect URLs before delivery or persistence. Authentication uses an API-Key header that may optionally combine the user ID and API key in a single value. ## For AI agents Validate phone numbers and email addresses, look up IP geolocation, and parse URL metadata to clean contact records and inspect inputs. ## Scope Does not handle SMS sending, image processing, or BIN lookup - use this slim spec for phone, email, IP, and URL validation only. ## Capabilities - Validate a phone number's format, country, and carrier through the phone-validate endpoint - Verify whether an email address is well-formed and deliverable through the email-validate endpoint - Look up geolocation, ASN, and ISP information for a given IP address through ip-info - Extract structured metadata for a URL including hostname, path, and query through url-info - Authenticate every request with an API-Key header that may optionally embed the user ID alongside the key ## Use cases ### Sign-Up Form Hardening SaaS sign-up flows call POST /email-validate and POST /phone-validate before account creation to reject disposable addresses, mistyped numbers, and non-existent carriers. Catching these at the point of capture cuts bounce rates on welcome emails and reduces fraud-prone accounts without adding user friction beyond the round trip. Example prompt: Call POST /email-validate with the submitted address and POST /phone-validate with the submitted phone number; reject the form submission if either response indicates an invalid input. ### Contact List Cleaning Sales operations teams batch-clean imported contact lists by iterating each record and calling /email-validate and /phone-validate to mark invalid entries before pushing them into the CRM. The Neutrino response includes country, line type, and carrier signals that drive downstream segmentation in addition to the simple valid or invalid flag. Example prompt: For each row in the import file, call POST /phone-validate and POST /email-validate, write the valid flag and carrier into the CRM, and quarantine rows where either check fails. ### Geo-Targeted Compliance Applications restricted by jurisdiction call POST /ip-info on the visitor's IP at session start to determine country and region, then enforce geo-blocking, GDPR consent variants, or sales tax behaviour accordingly. The combined country, ASN, and ISP signals also help flag traffic from VPNs and hosting ranges. Example prompt: Call POST /ip-info with the request's source IP, branch the workflow on the country field, and serve the EU consent banner when country is in the EEA list. ### AI Agent Data Quality An AI agent processing inbound leads uses Jentic to discover Neutrino validation operations and runs each new lead through email, phone, and IP checks before deciding whether to push the record into the CRM. This keeps the agent's downstream actions trustworthy without hand-coding four separate validation integrations. Example prompt: Use Jentic to search 'validate phone number', 'validate email address', and 'lookup ip info', then chain the three validations against each lead and write a quality score before any CRM write. ## Key endpoints | Method | Path | Description | | --- | --- | --- | | POST | `/phone-validate` | Validate a phone number | | POST | `/email-validate` | Validate an email address | | POST | `/ip-info` | Look up IP geolocation and ASN | | POST | `/url-info` | Parse URL metadata | ## Key resources - **Email** — Validate email address format and deliverability - **Phone** — Validate phone number format, country, and carrier - **Geolocation** — Look up country, region, ASN, and ISP for an IP address - **Web Tools** — Parse URL metadata into structured components ## Why Jentic - **Setup:** Wiring this slim Neutrino API by hand means setting its API-Key header, targeting the neutrinoapi.net host, and shaping phone, email, IP, and URL validation payloads yourself. Through Jentic you install once, import Neutrino from the API Directory, store the key once, and your agent calls it. - **Permission scoping:** Neutrino takes each value to validate in the request body, so limit the agent to the operations it needs, such as validating an email or looking up IP info, and leave out the ones it should not run. - **Credential handling:** Your Neutrino API key and optional user id are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'validate an email address' or 'look up IP info', and Jentic returns the matching Neutrino operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **Neutrino API (full)** — Same vendor specification covering 28 additional Neutrino tools - **AbstractAPI IP Geolocation** — Dedicated IP geolocation API as an alternative to Neutrino's ip-info - **Numverify API** — Phone number validation specialist as an alternative to Neutrino's phone-validate ## FAQ ### What authentication does the Neutrino API use? Neutrino API uses an API-Key header. The value may be either the API key alone or 'your-user-id:your-api-key' to combine both credentials in one header. Through Jentic, the API key is stored in your Jentic One instance and injected at request time so it never reaches the agent's context. ### Can I validate phone numbers with the Neutrino API? Yes. POST /phone-validate accepts a phone number and an optional country hint, and returns format validity, country code, region, line type, and carrier information you can use to clean CRM data or harden sign-up forms. ### How do I geolocate an IP address through Jentic? Search Jentic for 'lookup ip info', load the POST /ip-info schema, and execute it with the IP. The response includes country, region, city, ASN, and ISP, which you can branch on for compliance or fraud workflows. ### What are the rate limits for the Neutrino API? Rate limits are tied to your Neutrino plan rather than published in the spec. Free plans throttle aggressively while paid plans scale into thousands of calls per minute - check the Neutrino dashboard for your current quota. ### Does the Neutrino API verify if an email is deliverable? POST /email-validate checks syntax, MX records, and disposable-domain heuristics. It returns deliverability hints but does not perform a full SMTP probe - for stricter inbox-level verification combine it with a dedicated email verification provider. ### Is the Neutrino API free? Neutrino offers a free plan with limited monthly calls and paid tiers from there. API access is enabled on every plan including the free tier. ### Can I limit what my agent is allowed to do with the Neutrino API? Yes. Because Jentic One is self-hosted, you decide which Neutrino operations your agent may call, so you can grant only the ones it needs, such as POST /email-validate and POST /phone-validate, and leave out /ip-info or /url-info. Your Neutrino API key and optional user ID are stored by your own instance and injected at request time, so the agent never handles the raw credential. Your rules govern both which endpoints run and which credentials back them, keeping the agent inside the scope you set.