Geokeo for AI agents
Geokeo is a lightweight geocoding API that turns addresses into coordinates and coordinates into addresses. Small teams use it for quick location lookups without heavier mapping platforms. 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 Geokeo.
Geocode a new lead address
Convert a lead's mailing address into latitude and longitude to plot it on a territory map.
Reverse geocode a GPS ping
Resolve a device's coordinates into a human-readable address for a location log entry.
Verify a location before saving
Do a read-only lookup to confirm an address resolves to a real place before it is stored on a record.
2 Geokeo actions, graded by risk.
Every Geokeo action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
0Look things up. Allowed by default.
- No read actions.
write
2Create and change things. Allow, or ask the user first.
- geokeo.forward_geocodingForward Geocoding
- geokeo.reverse_geocodingReverse Geocoding Lookup
destructive
0Delete, cancel or archive. Ask first, or deny outright.
- No destructive actions.
Geokeo in three steps.
- 01Your users connect GeokeoThey add their Geokeo api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, and writes like “forward Geocoding” can wait for the user to approve.
- 03Any agent can actYour agent calls Geokeo through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('geokeo', { read: 'allow', write: 'ask', // forward_geocoding destructive: 'deny', }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Geokeo connects.
Users add their Geokeo 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 Geokeo 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 Geokeo from any agent.
ClaudeChatGPTCursor
Codex
VS CodeOpenAI Agents SDKClaude Agent SDK
Vercel AI SDK
Mastra
LangGraph
Geokeo and Arc0, answered.
Can I use Geokeo with Claude, ChatGPT or Cursor?
Yes. Connect Geokeo 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 Geokeo actions you allow.
How do users connect Geokeo?
Users add their Geokeo 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 Geokeo actions can my agent take?
2 in total: 0 read, 2 write and 0 destructive, such as “forward Geocoding”. Your policies decide which of them each agent may call.
Can I make my agent read-only in Geokeo?
Yes. Allow read actions and deny writes in the Geokeo policy. Your agent can still look things up, and any write it attempts is blocked and logged.
Can my own backend call Geokeo too?
Yes. The same Geokeo connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Geokeo into your agent.
Your users connect Geokeo once, under your brand. Your agent gets 2 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan