IP2Proxy is a proxy detection web service that identifies anonymous proxies, VPNs, TOR exit nodes, search engine robots, and residential proxies by IP address.
IP2Proxy is a proxy detection web service that identifies anonymous proxies, VPNs, TOR exit nodes, search engine robots, and residential proxies by IP address. On Nagent, Ip2Proxy is exposed as a fully-configurable security & identity tools integration that any agent can call — 1 action, and API key authentication. No code is required to wire Ip2Proxy into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Ip2Proxy to automate the kinds of tasks security & identity tools teams previously handled manually. Concrete examples — each one is a single agent step in Nagent — include:
Every action and trigger is paired with a structured input/output schema (visible in the sections below), so when you wire Ip2Proxy into Helix — our agentic agent builder — the editor knows exactly what each step expects and produces. Configure once, deploy anywhere across your Nagent agents.
Every operation an agent can call against Ip2Proxy, with input parameters and output schema. Drop these into any step of an agent built in Helix.
IP2PROXY_CHECK_PROXYTool to check if an IP address is a proxy. Use after obtaining an IP to detect proxy, VPN, or Tor status.
Input parameters
IPv4 or IPv6 address to look up. If omitted, the server IP is used.
Response format; defaults to json. Valid values: json or xml.
Data package level; defaults to PX1. Valid values: PX1–PX11.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
No publicly available marketplace agent is found using this tool yet. There are 59 agents privately built on Nagent that already use Ip2Proxy.
Build on Nagent
Connect Ip2Proxy to any Nagent agent in minutes — no API key management, no boilerplate. Just configure and deploy.
The five questions agent builders ask before adopting a new integration.
Open the External Integrations panel inside Nagent (app.nagent.ai/externalIntegration), find Ip2Proxy, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Ip2Proxy is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Ip2Proxy is connected, you configure its 1 action directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Ip2Proxy steps into any workflow visually. Pick an action (e.g., one of those listed above), fill in the inputs (Helix knows the required vs. optional schema for each parameter), and connect it to upstream/downstream steps. Triggers run as the entry point of an agent, so when a Ip2Proxy event fires, the agent kicks off automatically.
Every Ip2Proxy action and trigger ships with a fully-typed schema — input parameters with name, type, required flag, and description, plus the output payload shape. The schemas are documented in the sections above. Helix uses these schemas to validate your configuration at build time and to type-check the data flowing between steps.
Yes. While Ip2Proxy ships with 1 pre-built security & identity tools action, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Ip2Proxy together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Ip2Proxy-based workflows tailored to your business.