Ip2Location for AI agents
IP2Location provides IP geolocation, WHOIS, and proxy detection data for identifying where and what an IP address is. Developers wire it into their own apps and internal tools instead of building the underlying capability from scratch. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.
What agents do in Ip2Location.
Look up an IP's location
Look up the country and city associated with a visitor's IP address for fraud checks.
Check a domain's WHOIS record
Pull WHOIS registration details for a domain during a vendor due-diligence check.
Detect a proxy connection
Check whether an incoming IP is a known proxy or VPN before allowing a sensitive action.
8 Ip2Location actions, graded by risk.
Every Ip2Location action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
5Look things up. Allowed by default.
- ip2location.list_ipsIP2Location List IPs
- ip2location.get_hosted_domainsIP2WHOIS Hosted Domains Lookup
- ip2location.get_ip_geolocationIP2Location Get IP Geolocation
- ip2location.get_proxy_detectionIP2Proxy: Get Proxy Detection
- ip2location.check_creditsCheck IP2Location API Credits
write
3Create and change things. Allow, or ask the user first.
- ip2location.distanceIP2Location Distance Calculator
- ip2location.bulk_ip_geolocationBulk IP Geolocation
- ip2location.ip2_whois_domain_whoisIP2WHOIS Domain WHOIS Lookup
destructive
0Delete, cancel or archive. Ask first, or deny outright.
- No destructive actions.
Ip2Location in three steps.
- 01Your users connect Ip2LocationThey add their Ip2Location api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, and writes like “iP2Location Distance Calculator” can wait for the user to approve.
- 03Any agent can actYour agent calls Ip2Location through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('ip2location', { read: 'allow', write: 'ask', // distance destructive: 'deny', }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Ip2Location connects.
Users add their Ip2Location api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
The same Ip2Location connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →
- AUTH
- API key
- CREDENTIALS
- Per-tenant encrypted vault
- MODEL SEES
- Results only, never credentials
- AUDIT LOG
- Every call, on every plan
Use Ip2Location from any agent.
Ip2Location and Arc0, answered.
Can I use Ip2Location with Claude, ChatGPT or Cursor?
Yes. Connect Ip2Location to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the Ip2Location actions you allow.
How do users connect Ip2Location?
Users add their Ip2Location api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
Which Ip2Location actions can my agent take?
8 in total: 5 read, 3 write and 0 destructive, such as “iP2Location Distance Calculator”. Your policies decide which of them each agent may call.
Can I make my agent read-only in Ip2Location?
Yes. Allow read actions and deny writes in the Ip2Location policy. Your agent can still look things up, and any write it attempts is blocked and logged.
Can my own backend call Ip2Location too?
Yes. The same Ip2Location connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Ip2Location into your agent.
Your users connect Ip2Location once, under your brand. Your agent gets 8 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan