Ipdata.co for AI agents

ipdata.co is a simple HTTP API for looking up the location, ownership, and threat profile of any IP address. 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.

Developer toolsAPI keyMCP + RESTipdata.co
AUDIT LOG · IPDATA.COPOLICY: acme-support
09:41:09 · claude · u_8f2write
ipdata_co.field_ip
IPData: IP✓ approved · approved by user
EVERY IPDATA.CO CALL, ON THE RECORD
01 · USE CASES

What agents do in Ipdata.co.

01

Look up a city from an IP

Look up the city behind a visitor's IP address to localize a welcome message.

02

Check a threat score for an IP

Check an IP's threat score before allowing a high-risk action like a password reset.

03

Bulk lookup a list of IPs

Run a bulk lookup on a list of IPs pulled from server logs for a traffic report.

02 · ACTIONS

28 Ipdata.co actions, graded by risk.

Every Ipdata.co action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.

read

0

Look things up. Allowed by default.

  • No read actions.

write

28

Create and change things. Allow, or ask the user first.

  • ipdata_co.field_ip
    IPData: IP
  • ipdata_co.field_city
    Get City from IP
  • ipdata_co.field_count
    IPDATA Field Count
  • ipdata_co.field_is_eu
    IPData: Is EU
  • ipdata_co.field_postal
    IPData: Postal Code
  • ipdata_co.field_region
    Get Region from IP
  • ipdata_co.field_threat
    Get Threat for IP
  • ipdata_co.field_carrier
    IPDATA Field Carrier
  • ipdata_co.field_currency
    IPDATA Field Currency
  • ipdata_co.field_latitude
    IPData: Latitude
  • ipdata_co.field_languages
    IPData: Languages
  • ipdata_co.field_longitude
    Get Longitude from IP
  • ipdata_co.field_time_zone
    IPData: Time Zone
  • ipdata_co.field_emoji_flag
    Get Emoji Flag from IP
  • ipdata_co.field_region_code
    IPData: Region Code
  • ipdata_co.field_calling_code
    IPData: Calling Code
+ 12 MORE

destructive

0

Delete, cancel or archive. Ask first, or deny outright.

  • No destructive actions.
03 · HOW IT WORKS

Ipdata.co in three steps.

  1. 01Your users connect Ipdata.coThey add their Ipdata.co api key on Arc0 Connect, under your brand. It goes straight into the vault.
  2. 02You set the rulesReads run, and writes like “iPData: IP” can wait for the user to approve.
  3. 03Any agent can actYour agent calls Ipdata.co through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
POLICY.TS
await arc0.policies.set('ipdata_co', {
  read: 'allow',
  write: 'ask',        // field_ip
  destructive: 'deny',  
})

# Claude Code: the same connection, one URL
$ claude mcp add --transport http arc0 \
    https://mcp.arc0.ai/u/u_8f2
04 · AUTH AND DATA

How Ipdata.co connects.

Users add their Ipdata.co 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 Ipdata.co 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
05 · WORKS WITH

Use Ipdata.co from any agent.

Claude
ChatGPT
Cursor
Codex
VS Code
OpenAI Agents SDK
Claude Agent SDK
Vercel AI SDK
Mastra
LangGraph
07 · FAQ

Ipdata.co and Arc0, answered.

Q01

Can I use Ipdata.co with Claude, ChatGPT or Cursor?

Yes. Connect Ipdata.co 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 Ipdata.co actions you allow.

Q02

How do users connect Ipdata.co?

Users add their Ipdata.co 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.

Q03

Which Ipdata.co actions can my agent take?

28 in total: 0 read, 28 write and 0 destructive, such as “iPData: IP”. Your policies decide which of them each agent may call.

Q04

Can I make my agent read-only in Ipdata.co?

Yes. Allow read actions and deny writes in the Ipdata.co policy. Your agent can still look things up, and any write it attempts is blocked and logged.

Q05

Can my own backend call Ipdata.co too?

Yes. The same Ipdata.co connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.

Get started

Plug Ipdata.co into your agent.

Your users connect Ipdata.co once, under your brand. Your agent gets 28 actions behind your policies, with every call on the record.

Free to build · MCP + REST · Audit log on every plan