IP2Proxy Proxy Detection

Name: IP2Proxy Proxy Detection API
Brand: IP2Proxy Proxy Detection
Availability: InStock

★ Only Publicly Available OpenAPI DocumentSecurityThreat DetectionapiKey1 EndpointsREST

For Agents

Flag whether an IP belongs to a proxy, VPN, TOR exit node, or hosting range so an agent can apply trust, fraud, and abuse rules.

Install Jentic One Beta

Connect the IP2Proxy Proxy Detection to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the IP2Proxy Proxy Detection, 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.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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 IP2Proxy Proxy Detection API.

Detect anonymous proxies, public VPNs, and TOR exit nodes from a single IP lookup

Identify search engine robot IPs (SES) so abuse rules can ignore legitimate crawlers

Flag data center ranges and residential proxies through the PX2-PX10 detection levels

GET STARTED

Start building with IP2Proxy Proxy Detection API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use IP2Proxy Proxy Detection API for, with concrete tasks.

★ Login Risk Scoring

Trust and safety teams can call IP2Proxy on every login attempt, raise the risk score when the IP is a public VPN, TOR exit node, or named commercial VPN provider, and gate sensitive actions behind step-up authentication. The named-provider tier (PX11) is useful for spotting BYO-VPN account takeover patterns.

Look up a login IP and return a risk verdict if proxy_type is VPN, TOR, or PUB and the named provider is on the deny list.

Bot and Abuse Filtering

Public APIs and signup forms can call IP2Proxy to filter out anonymous and data-center traffic before allowing free-tier signups, which blunts the most common forms of credential stuffing and signup abuse. The PX2-PX10 levels give a tunable knob for how aggressive the filter should be.

On a signup attempt, look up the source IP and reject the request if proxy_type is DCH (data center) or PUB (public proxy).

Crawler-Aware Abuse Rules

Sites that need to allow legitimate search engine crawlers but block proxies can use the SES classification to whitelist verified bot IPs, then apply stricter rules to non-SES proxy traffic. This avoids accidentally blocking Googlebot or Bingbot when tightening a proxy filter.

Look up an incoming IP and short-circuit the abuse pipeline if proxy_type is SES.

Agent-Driven Proxy Audit

An AI agent connected via Jentic can audit a list of suspect IPs from a security alert, classify each one as proxy, VPN, TOR, or clean, and return a structured summary. The agent searches Jentic by intent and does not need to keep the PX detection levels in context.

Take a list of 25 IPs from a fraud alert, classify each one through IP2Proxy, and return a summary grouped by proxy_type.

Key Endpoints

1 endpoints — ip2proxy proxy detection is a hosted lookup service that flags whether an ip address belongs to an anonymous proxy, vpn, tor exit node, search engine robot, data center range, residential proxy, or known commercial vpn provider.

METHOD

PATH

DESCRIPTION

GET

Detect proxy, VPN, or TOR status for an IP

GET

Detect proxy, VPN, or TOR status for an IP

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Your IP2Proxy API key is stored once, encrypted, by your own Jentic One instance and injected as the 'key' query parameter 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 'flag TOR exit nodes', and Jentic returns the IP2Proxy operation with its input schema, including the package parameter for detection depth, so the agent calls the right endpoint without browsing the docs.

Time to first call

FAQs

Specific to using IP2Proxy Proxy Detection API through Jentic.

What authentication does the IP2Proxy API use?

The endpoint accepts an API key as a query parameter named 'key'. Through Jentic the key is held in the encrypted vault and injected at execution time so the raw key does not reach the agent context.

Can IP2Proxy tell me which VPN provider an IP belongs to?

Yes, on the PX11 detection level the response includes the named commercial VPN provider behind an IP. Lower tiers (PX1-PX10) return progressively narrower classifications: anonymous proxy, public proxy, web proxy, TOR, search engine bot, data center, residential proxy.

Does the IP2Proxy API support IPv6?

Yes. The same endpoint accepts IPv4 and IPv6 addresses; the response shape is identical for both so an agent can pass either family without branching.

What are the rate limits for the IP2Proxy API?

Throughput is governed by the credit balance on the API key rather than a per-minute rate limit; each lookup consumes credits scaled by the chosen detection level. Remaining credits are visible in the IP2Proxy account dashboard.

How do I check an IP for proxy status through Jentic?

Search Jentic for 'check whether an IP is a proxy', load the schema for GET /, and execute with the ip and package parameters. Run pip install jentic, then await client.search, await client.load, await client.execute.

What is the difference between IP2Proxy and IP2Location?

IP2Proxy is purpose-built for proxy and VPN detection with the PX1-PX11 levels; IP2Location is the geolocation surface that returns country, city, ISP, and ASN. Use them together when both location and trust signals are needed.

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

Yes. IP2Proxy exposes a single read-only classification lookup that takes an IP as a query parameter, and because you run Jentic One yourself, your own rules decide which operations and credentials the agent may use. You can scope the agent to just the checks it needs, such as flagging whether an IP is an anonymous proxy, VPN, or TOR exit node, and it stays a lookup client that cannot reach anything beyond the operations you allow.