canonical: https://jentic.com/apis/neutrinoapi.net/neutrinoapi-net

# Neutrino API

The full Neutrino API specification exposes 28 endpoints covering email and phone validation, IP and host reputation lookups, geocoding, image processing, HTML rendering, BIN lookup, currency conversion, and a browser bot. It is positioned as a general-purpose toolbox for backend developers who need many small data and validation utilities behind a single vendor credential. Authentication uses an api-key header alongside a separate user-id header.

## For AI agents

Run 28 backend utilities - including phone and email validation, IP info, geocoding, BIN lookup, image resize, and HTML render - through a single Neutrino credential.

## Scope

Does not handle outbound SMS or email delivery, payment processing, or persistent storage - use for one-shot validation, lookup, geocoding, image, and rendering utilities only.

## Capabilities

- Validate phone numbers and email addresses across format, deliverability, carrier, and HLR signals
- Look up IP geolocation, blocklist status, host reputation, and probe IP characteristics in real time
- Geocode addresses to coordinates and reverse-geocode coordinates to addresses
- Render HTML or URLs to PDF and PNG and resize or watermark images
- Look up payment card BIN data to detect card type, brand, and issuer country
- Convert currencies and run a scriptable browser bot for scraping or interaction tasks
- Authenticate every request with paired api-key and user-id headers

## Use cases

### Multi-Tool Backend Utilities Belt

Engineering teams that would otherwise integrate four or five separate vendors for validation, geocoding, image processing, and HTML rendering instead consolidate on Neutrino with one credential. The 28-endpoint surface covers most micro-utility needs without per-vendor onboarding overhead.

Example prompt: Replace separate phone, email, IP, and geocoding vendor calls with the matching Neutrino endpoints - for example switch the email validator integration to GET /email-validate with the same api-key header.

### Fraud and Risk Pre-Checks

Risk pipelines call GET /ip-blocklist, GET /host-reputation, and GET /bin-lookup at signup or checkout to score the likelihood of fraud before authorising a transaction. Combining IP, host, and card-issuer signals through one vendor accelerates rule iteration compared with stitching specialist tools together.

Example prompt: On checkout, call GET /ip-blocklist with the customer IP, GET /bin-lookup with the BIN of the card, and GET /host-reputation with the email domain; refuse the order if any of the three return a high-risk verdict.

### Programmatic Document Rendering

SaaS products generate PDFs of invoices and reports by sending HTML to POST /html-render and storing the resulting binary. The same endpoint handles screenshots and PNG export, which means the engineering team can consolidate browser-based rendering on a single vendor instead of running headless Chrome in production.

Example prompt: POST /html-render with the invoice HTML body and format 'pdf', save the returned binary to the customer's S3 prefix, and email the link to the recipient.

### AI Agent Integration Toolbox

An AI agent uses Jentic to discover whichever Neutrino tool matches the task at hand - email validation, IP geolocation, geocoding, BIN lookup - without the developer wiring each one separately. The agent picks the right operation by intent and Jentic returns the schema and credential binding ready to execute.

Example prompt: Use Jentic to search 'geocode a postal address', load GET /geocode-address, and execute it with the user-supplied address; route the returned coordinates into the next step of the agent's workflow.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/email-validate` | Validate an email address |
| GET | `/ip-info` | Look up IP geolocation and network info |
| GET | `/geocode-address` | Geocode a postal address to coordinates |
| POST | `/html-render` | Render HTML or a URL to PDF or PNG |
| GET | `/bin-lookup` | Look up payment card BIN data |
| POST | `/image-resize` | Resize an image |
| GET | `/ip-blocklist` | Check whether an IP is on a blocklist |
| GET | `/hlr-lookup` | Run an HLR lookup on a phone number |

## Key resources

- **Telephony** — Phone validation, HLR lookup, and SMS-related utilities
- **Geolocation** — IP info, IP probe, geocoding, and reverse geocoding
- **Security and Networking** — IP blocklists, host reputation, and bad word filtering
- **Imaging** — Image resize, watermarking, HTML render, and QR generation
- **Data Tools** — Email validation, currency convert, BIN lookup, and URL info
- **WWW** — Browser bot and domain lookup utilities

## Why Jentic

- **Setup:** Wiring the full Neutrino API by hand means setting its api-key and user-id headers, targeting the neutrinoapi.net host, and shaping validation, geocoding, image, and rendering calls across many utilities yourself. Through Jentic you install once, import Neutrino from the API Directory, store the credentials once, and your agent calls it.
- **Permission scoping:** Neutrino takes its inputs in the request rather than as path resources, so limit the agent to the operations it needs, such as rendering HTML or looking up IP info, and leave out the ones it should not run.
- **Credential handling:** Your Neutrino api-key and 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 'render HTML to PDF' 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 (slim)** — Slim Neutrino spec covering only email, phone, IP, and URL endpoints
- **AbstractAPI IP Geolocation** — Dedicated IP geolocation provider
- **MaxMind GeoIP** — Industry-standard IP geolocation and risk database

## FAQ

### What authentication does the Neutrino API use?

Neutrino uses two paired headers: api-key carrying one of your API keys and user-id carrying your Neutrino user identifier. Through Jentic, both values are stored in your Jentic One instance and injected at request time so they never appear in the agent's context.

### Can I render HTML to PDF with the Neutrino API?

Yes. POST /html-render accepts HTML or a URL plus format and page-size parameters and returns PDF or PNG output. This removes the need to run a headless browser in production for invoice and report generation.

### How do I geocode an address through Jentic?

Search Jentic for 'geocode a postal address', load GET /geocode-address, and execute it with the address. The endpoint returns latitude, longitude, country, and locality data which can be branched on directly.

### What are the rate limits for the Neutrino API?

Rate limits depend on the Neutrino plan rather than being published in the spec. Free plans throttle hard while paid plans scale into thousands of calls per minute - verify the current quota in the Neutrino dashboard.

### Does the Neutrino API include image processing?

Yes. POST /image-resize and POST /image-watermark cover resizing and overlaying watermarks on images, giving teams a single vendor for both validation and lightweight media processing.

### Is the Neutrino API free?

Neutrino offers a free plan with capped monthly calls plus paid plans for higher volumes. API access is included on every tier including the free plan.

### Can I limit what my agent is allowed to do with the Neutrino API?

Yes. Because you self-host Jentic One, your own rules decide which of Neutrino's 28 operations the agent may call and which stored credentials it may use. Since Neutrino takes its inputs in the request body or query rather than as path resources, you scope by operation: allow only the utilities the task needs, such as GET /email-validate, GET /ip-info, or POST /html-render, and leave out the rest. Your api-key and user-id stay held by your Jentic One instance and are injected at execution, so the agent can run only the operations you have permitted.