IP2Location.io for AI agents
IP2Location.io provides a fast IP geolocation API for determining a user's location for personalization or fraud checks. Engineering teams pull it into internal tools and scripts rather than building the same capability themselves. 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.io.
Look up a visitor's location
Look up the geographic location behind an IP address to localize content for a visitor.
Bulk geolocate a list of IPs
Run a batch of IP addresses through geolocation to enrich a log analysis report.
Check a domain's hosted status
Look up whether a domain is hosted at a given IP as part of a security review.
5 IP2Location.io actions, graded by risk.
Every IP2Location.io action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
2Look things up. Allowed by default.
- ip2location_io.get_api_keyGet API Key
- ip2location_io.get_ip_geolocationGet IP Geolocation
write
3Create and change things. Allow, or ask the user first.
- ip2location_io.domain_whoisDomain WHOIS Lookup
- ip2location_io.bulk_ip_geolocationBulk IP Geolocation
- ip2location_io.ip2_whois_hosted_domainIP2WHOIS Hosted Domain
destructive
0Delete, cancel or archive. Ask first, or deny outright.
- No destructive actions.
IP2Location.io in three steps.
- 01Your users connect IP2Location.ioThey add their IP2Location.io api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, and writes like “domain WHOIS Lookup” can wait for the user to approve.
- 03Any agent can actYour agent calls IP2Location.io 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_io', { read: 'allow', write: 'ask', // domain_whois destructive: 'deny', }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How IP2Location.io connects.
Users add their IP2Location.io 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.io 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.io from any agent.
ClaudeChatGPTCursor
Codex
VS CodeOpenAI Agents SDKClaude Agent SDK
Vercel AI SDK
Mastra
LangGraph
IP2Location.io and Arc0, answered.
Can I use IP2Location.io with Claude, ChatGPT or Cursor?
Yes. Connect IP2Location.io 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.io actions you allow.
How do users connect IP2Location.io?
Users add their IP2Location.io 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.io actions can my agent take?
5 in total: 2 read, 3 write and 0 destructive, such as “domain WHOIS Lookup”. Your policies decide which of them each agent may call.
Can I make my agent read-only in IP2Location.io?
Yes. Allow read actions and deny writes in the IP2Location.io policy. Your agent can still look things up, and any write it attempts is blocked and logged.
Can my own backend call IP2Location.io too?
Yes. The same IP2Location.io connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug IP2Location.io into your agent.
Your users connect IP2Location.io once, under your brand. Your agent gets 5 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan