IP2Proxy
Identity & SecurityConnect AI agents to IP2Proxy, a proxy and VPN detection service from IP2Location. Agents check whether an IP belongs to a proxy, VPN, or Tor exit before a flow trusts the request behind it.
What This Integration Enables
Two actions. That is not a thin connector, it is a precise one. IP2Proxy answers a single question, is this address an anonymizer, and it answers it with a level of detail you choose and pay for per call. Lookup Proxy takes one IPv4 or IPv6 address and reports whether it belongs to a proxy, VPN, Tor exit node, data center, or residential proxy, along with the country. The Package field controls how much comes back and is cumulative: PX1 returns country code, country name, and the is-proxy flag for one credit, and each step up adds a field and a credit, through proxy type at PX2, region and city at PX3, ISP at PX4, domain at PX5, usage type at PX6, ASN and AS name at PX7, last seen at PX8, threat classification at PX9, the residential proxy flag at PX10, and the VPN provider name at PX11. Response Format selects JSON or XML. Check Credit Balance returns remaining credits without consuming any and without performing a lookup.
Two behaviors are worth building around rather than discovering. First, leaving the IP Address parameter empty does not fail. It resolves the calling server's own address, which means a null variable in a flow returns a clean, plausible looking result about FlowRunner's infrastructure instead of an error, and a policy that reads is-proxy will happily approve it. Validate that the variable is populated before the call. Second, the reported balance can lag real usage by up to ten minutes, so a check that says you have room is a recent statement rather than a current one. The connector exposes no triggers: nothing in IP2Proxy starts a flow, and there is no event stream to subscribe to. Every lookup is something your flow performs at the moment a request arrives. This service targets the dedicated proxy detection endpoint, so for general geolocation without the anonymizer focus, use the separate IP2Location.io IP Geolocation connector instead.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Anonymizer Check at Signup
A signup form submits and the flow captures the originating IP. The agent validates the value is present, then runs Lookup Proxy at PX10 so the response includes proxy type, usage type, threat classification, and the residential proxy flag. A data center address on a consumer product is a different signal from a residential proxy, and a residential proxy is a different signal again from a commercial VPN that half the account's paying customers use at work. The agent applies the policy the risk owner set for each type, and records which type was returned so the policy can be argued about later with evidence rather than impressions.
Enriching an Existing Fraud Case
An account has already been flagged by another system and an analyst is deciding what to do. Rather than blocking on a bare IP, the agent runs Lookup Proxy at PX11 on the addresses in the account's login history, which returns the VPN provider name where one applies. A case where every login came through the same named commercial VPN reads very differently from one where logins hop between Tor exits and residential proxies in four countries. The agent attaches the enriched history to the case. The paid detail earns its credits precisely here, on cases that are already worth a person's time.
Quota Aware Batch Screening
A retention job needs to screen a backlog of stored IPs from the last quarter. The agent runs Check Credit Balance first and multiplies the queue length by the credits the chosen package costs. If the balance covers the run, the batch proceeds. If it does not, the agent does not start and quietly stop halfway, and it does not silently drop to a cheaper package. It reports the shortfall with the numbers and waits. A partial screening that looks complete is worse than no screening, because the gap is invisible in the result set.
Human-in-Loop Highlight
The moment worth stopping on here is not any individual address. It is the moment the quota runs short, because that is when an anonymizer control degrades without appearing to. The Package field is cumulative and priced per level, so dropping from PX11 to PX1 to make the credits stretch does not return less confident data, it returns different data: proxy type, usage type, threat classification, the residential proxy flag, and the VPN provider name simply stop being in the response. A block rule written against proxy type reads an absent field, finds nothing disqualifying, and approves. The screening still runs, the log still fills, and the control is off. Compounding it, Check Credit Balance can lag real usage by up to ten minutes, so the flow cannot fully trust its own headroom. When the agent projects that the balance will not cover the queue at the required package, it stops and posts to the risk owner: "Queue of [n] addresses needs [n] credits at PX11. Balance reads [n], and the figure can lag by ten minutes. Reduce to PX[n], which drops [named fields] from the response and disables [named rules], top up the key, or pause screening until it is topped up?" The owner chooses. Nothing about this decision should be made by whichever step happens to hit the empty balance first. That is a digital andon cord on a control that would otherwise fail quietly.
Agent Capabilities
2 actionsProxy Detection
1- Lookup Proxy Queries a single IPv4 or IPv6 address against the IP2Proxy web service to determine whether it belongs to a proxy, VPN, Tor exit node, data center, residential proxy or other anonymizer, and returns the country of the address. Detail is controlled by the cumulative Package field from PX1 to PX11, which progressively adds proxy type, region and city, ISP, domain, usage type, ASN and AS name, last seen, threat classification, the residential proxy flag, and the VPN provider name. Each query consumes credits equal to the package number. Response Format selects JSON or XML. Leaving the IP Address empty looks up the calling server's own address rather than returning an error, so validate the value before the call.
Account
1- Check Credit Balance Returns the number of query credits remaining on the API key without consuming any credits and without performing a lookup. Used before a batch to confirm the run can finish at the required package. The balance figure can be delayed by up to ten minutes from real time usage.
Frequently Asked Questions
What can FlowRunner do with IP2Proxy?
FlowRunner agents can run Lookup Proxy and Check Credit Balance in IP2Proxy.
Does connecting IP2Proxy to FlowRunner require OAuth?
No. IP2Proxy connects to FlowRunner with an API key, no OAuth flow required.
Can IP2Proxy trigger a FlowRunner workflow automatically?
IP2Proxy doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with IP2Proxy
$100 in credits. No card required. Connect in minutes.