Opencage for AI agents
OpenCage Geocoder converts addresses into coordinates and coordinates back into addresses using open geographic data. Developers use it to add location lookup to applications. 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 Opencage.
Geocode an address to coordinates
Convert a customer's street address into latitude and longitude for mapping.
Reverse geocode a location
Look up the nearest address for a set of coordinates captured from a device.
Check API health read-only
Confirm the geocoding service is responsive before relying on it in a live workflow.
7 Opencage actions, graded by risk.
Every Opencage 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.
- opencage.ping_opencageCheck API Health
write
6Create and change things. Allow, or ask the user first.
- opencage.geocode_xmlGeocode XML
- opencage.geocode_forwardForward Geocode Address
- opencage.geocode_geojsonGeocode to GeoJSON
- opencage.geocode_reverseReverse Geocode Coordinates
- opencage.geocode_geojsonpGeocode with JSONP
- opencage.geocode_google_v3_jsonGeocode Google v3 JSON
destructive
0Delete, cancel or archive. Ask first, or deny outright.
- No destructive actions.
Opencage in three steps.
- 01Your users connect OpencageThey add their Opencage api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, and writes like “geocode XML” can wait for the user to approve.
- 03Any agent can actYour agent calls Opencage through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('opencage', { read: 'allow', write: 'ask', // geocode_xml destructive: 'deny', }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Opencage connects.
Users add their Opencage 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 Opencage 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 Opencage from any agent.
Opencage and Arc0, answered.
Can I use Opencage with Claude, ChatGPT or Cursor?
Yes. Connect Opencage 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 Opencage actions you allow.
How do users connect Opencage?
Users add their Opencage 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 Opencage actions can my agent take?
7 in total: 1 read, 6 write and 0 destructive, such as “geocode XML”. Your policies decide which of them each agent may call.
Can I make my agent read-only in Opencage?
Yes. Allow read actions and deny writes in the Opencage policy. Your agent can still look things up, and any write it attempts is blocked and logged.
Can my own backend call Opencage too?
Yes. The same Opencage connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Opencage into your agent.
Your users connect Opencage once, under your brand. Your agent gets 7 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan