IPScanner API
70
AI ReadinessAI-Aware (B+)70/100
Official vendor OpenAPI document · agent-readySecurityThreat Detectionbearer16 EndpointsREST
For Agents
Check whether an IP is a VPN, proxy, Tor exit, or datacenter, verify crawler and AI-agent traffic, geolocate addresses, read ASN and WHOIS data, and screen signup emails.
Use for: Check whether this IP address is a VPN or Tor exit, Verify that a request claiming to be Googlebot really is, Find the network owner and ASN for an IP address, Get the WHOIS record for a domain
Not supported: Does not block traffic, run a firewall, or probe email mailboxes. Use for IP, crawler, and signup risk checks only.
The IPScanner API classifies the network behind an IP address as VPN, residential proxy, Tor, hosting, mobile, or residential, and returns a purity score, geolocation, ASN ownership, and WHOIS in one combined lookup. It also verifies whether an address is really the crawler its user agent claims to be, classifies an inbound request as human, AI agent, verified crawler, or impostor, and writes hash-chained location attestation records against a claimed jurisdiction. A signup email check covers syntax, throwaway domains, MX records, and role mailboxes, and a keyless demo endpoint returns the same body as the keyed lookup.
Install Jentic One Beta
Connect the IPScanner API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the IPScanner API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fipscanner.io%2Fipscanner" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fipscanner.io%2Fipscanner" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with IPScanner API.
Run a combined lookup on an IP, CIDR range, hostname, or URL for network class, purity score, VPN, proxy and Tor flags, geolocation, and ASN
Detect whether an address is an anonymising VPN, residential proxy, or Tor exit through the isVpn and isProxy verdicts
Verify a crawler claim against forward-confirmed reverse DNS, the operator's published egress ranges, and its ASN
Classify one inbound request as human, AI agent, verified crawler, or impostor from its ip, user_agent, and headers
Write a hash-chained location attestation for an ip against a claimed_jurisdiction
Screen a signup email for syntax, throwaway domains, MX records, webmail typos, and role mailboxes
Use Cases
Patterns agents use IPScanner API for, with concrete tasks.
★ Agent-run signup fraud screening
An AI agent reviewing new signups needs to flag anonymised traffic and disposable email before an account is approved. Through Jentic the agent searches for 'check if an IP is a VPN', loads the IPScanner combined lookup, and reads networkClass and the purity score, then runs the email check on the address. The bearer key is attached at call time, so the agent works from the verdicts without handling the credential.
Call POST /v1/ip/lookup with target 203.0.113.7 and POST /v1/email/check with email new.user@example.com, then flag the signup if networkClass is vpn, residential_proxy, or tor or the email domain is throwaway
Crawler and AI-agent traffic verification
A site operator wants to let real search crawlers through while blocking scrapers that spoof their user agents. The crawler verification read checks reverse DNS, the operator's published ranges, and the ASN for a claimed bot, and the Agentscan check classifies a request as human, AI agent, verified crawler, or impostor with a recommended action.
Call POST /v1/crawlers/verify with ip 66.249.66.1 and bot googlebot, then call POST /v1/agentscan/check with the same ip and the request's user_agent and report both verdicts
Location attestation for compliance
A service that must prove where a connection came from records a verdict at the time of access. The provenance check takes an ip and a claimed_jurisdiction such as DE, applies the jurisdiction policy, and returns an attestation id backed by a hash-chained record for later export.
Call POST /v1/provenance/check with ip 8.8.8.8 and claimed_jurisdiction DE and store the returned attestation id
Network ownership research
A security analyst investigating an address wants its owner and the size of its network. The ASN directory searches autonomous systems by organisation name or number, and the directory entry returns prefix counts, network type, and how many prefixes sit inside known VPN and datacenter range lists.
Call GET /v1/asn/directory with q comcast, then GET /v1/asn/directory/{asn} for the top match and summarise its prefixes and network type
Key Endpoints
16 endpoints — the ipscanner api classifies the network behind an ip address as vpn, residential proxy, tor, hosting, mobile, or residential, and returns a purity score, geolocation, asn ownership, and whois in one combined lookup.
METHOD
PATH
DESCRIPTION
POST
/v1/ip/lookup
Combined IP, hostname, or URL lookup
GET
/v1/vpn/{ip}
VPN detection
GET
/v1/geo/{ip}
Geolocation
GET
/v1/whois/{domain}
WHOIS lookup
POST
/v1/crawlers/verify
Verify a crawler claim
POST
/v1/agentscan/check
Classify a request as human or agent
POST
/v1/provenance/check
Location attestation
POST
/v1/email/check
Email check
POST
/v1/ip/lookup
Combined IP, hostname, or URL lookup
GET
/v1/vpn/{ip}
VPN detection
GET
/v1/geo/{ip}
Geolocation
GET
/v1/whois/{domain}
WHOIS lookup
POST
/v1/crawlers/verify
Verify a crawler claim
POST
/v1/agentscan/check
Classify a request as human or agent
POST
/v1/provenance/check
Location attestation
POST
/v1/email/check
Email check
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
I
IPScanner API
- AI-Aware (B+)70/100
100
Foundational Compliance82
Developer Experience & Jentic Compatibility48
AI-Readiness & Agent Experience94
Agent Usability60
Security73
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.2
Show dimension breakdown
100
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A+Signals: 4
98%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
100%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
100%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
82
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: ASignals: 4
58%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
72%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
48
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: D+Signals: 4
40%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
52%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
60
Security
Trust, risk posture, and security compliance.
Grade: B-Signals: 1
60%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
73
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: A-Signals: 1
73%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring IPScanner by hand means sending the bearer key on keyed routes, knowing which five routes are keyless with their own per-IP limits, and handling camelCase and snake_case bodies on different surfaces. Through Jentic you install once, import IPScanner from the API Directory, store the key once, and your agent calls it.
Permission scoping
IPScanner carries lookup targets in the path or request body, so rules bound which operations your agent may call, such as the combined lookup and email check, not which address. You choose the operations it may call, so attestation writes like POST /v1/provenance/check are not included unless you add them.
Credential isolation
Your IPScanner API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'check if an IP is a VPN' or 'verify a crawler', and Jentic returns the matching IPScanner operation with its input schema so the agent calls the right endpoint.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using IPScanner API through Jentic.
What authentication does the IPScanner API use?
Per its OpenAPI spec, keyed routes take a bearer token: Authorization: Bearer with your API key. Five operations need no key: the demo lookup, GET /v1/myip, crawler verification, and the two ASN directory reads. Through Jentic the key is stored by your own instance and attached at call time, so the agent never sees it.
What are the rate limits for the IPScanner API?
The spec states the free tier is 30,000 requests a month, up to 1,000 a day and 100 an hour, and that paid plans have no daily cap. Keyless routes have their own per-IP limits, such as 100 requests per 24 hours on the demo lookup. GET /v1/user/limits returns your current usage and reset date.
Can the IPScanner API tell a cloud server from a VPN?
Yes. GET /v1/vpn/{ip} returns a networkClass and risk score, and isVpn is true only for the anonymising classes vpn, residential_proxy, and tor. A cloud or hosting address reports networkClass hosting with isVpn false.
Is there an IPScanner MCP server?
You don't need an MCP server to give your agent IPScanner. Jentic connects it directly from the API Directory: import it, store your key once, and your agent calls the lookup, crawler, and email operations it needs without loading another server's tool definitions into its context.
Can I limit what my agent is allowed to do with the IPScanner API?
Yes. Write a rule that allows only POST /v1/ip/lookup and the email check, for example, and the agent can screen signups but cannot write provenance attestations or run Agentscan checks against your allowance. Every call it makes is logged.
How do I check an IP address through Jentic?
Search Jentic for 'check if an IP is a VPN', load the POST /v1/ip/lookup operation, and execute it with a target such as an IP, CIDR range, hostname, or URL. Failed sub-lookups are named in degraded instead of failing the call. To run it on your own infrastructure, install Jentic One from its GitHub repo.
GET STARTED