IPLocate for AI agents
IPLocate provides current geolocation, network, privacy, hosting, and abuse intelligence for IP addresses, helping teams screen traffic and localize experiences based on where a request comes from. 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 IPLocate.
Look up an IP address
Look up the location and hosting details for a visitor's IP address as part of a fraud check.
Check if an IP is a known proxy
Check whether an IP is flagged for privacy or proxy use before allowing an account action.
Review abuse contact info
Pull the abuse contact for an IP's network, read-only, before reporting malicious traffic.
1 IPLocate actions, graded by risk.
Every IPLocate action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
1Look things up. Allowed by default.
- iplocate.lookup_ipLook Up IP Address
write
0Create and change things. Allow, or ask the user first.
- No write actions.
destructive
0Delete, cancel or archive. Ask first, or deny outright.
- No destructive actions.
IPLocate in three steps.
- 01Your users connect IPLocateThey add their IPLocate api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, and writes like “updates” can wait for the user to approve.
- 03Any agent can actYour agent calls IPLocate through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('iplocate', { read: 'allow', write: 'ask', destructive: 'deny', }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How IPLocate connects.
Users add their IPLocate 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 IPLocate 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 IPLocate from any agent.
ClaudeChatGPTCursor
Codex
VS CodeOpenAI Agents SDKClaude Agent SDK
Vercel AI SDK
Mastra
LangGraph
IPLocate and Arc0, answered.
Can I use IPLocate with Claude, ChatGPT or Cursor?
Yes. Connect IPLocate 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 IPLocate actions you allow.
How do users connect IPLocate?
Users add their IPLocate 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 IPLocate actions can my agent take?
1 in total: 1 read, 0 write and 0 destructive. Your policies decide which of them each agent may call.
Can I make my agent read-only in IPLocate?
Yes. Allow read actions and deny writes in the IPLocate policy. Your agent can still look things up, and any write it attempts is blocked and logged.
Can my own backend call IPLocate too?
Yes. The same IPLocate connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug IPLocate into your agent.
Your users connect IPLocate once, under your brand. Your agent gets 1 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan