Placekey for AI agents
Placekey assigns unique identifiers to physical addresses, making it easier to match location data across different data sources. Analysts use it to join disparate location datasets reliably. 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 Placekey.
Get a Placekey for an address
Generate a standard Placekey ID for an address so it can be matched across datasets.
Bulk generate Placekeys
Convert a batch of addresses into Placekeys for a large location dataset in one pass.
Geocode an address read-only
Look up coordinates for an address without modifying any stored location records.
4 Placekey actions, graded by risk.
Every Placekey action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
4Look things up. Allowed by default.
- placekey.get_placekeyGet Placekey
- placekey.get_placekeys_bulkGet Placekeys Bulk
- placekey.get_geocode_from_addressGet Geocode From Address
- placekey.get_placekey_from_addressGet placekey from 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.
Placekey in three steps.
- 01Your users connect PlacekeyThey add their Placekey 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 Placekey through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('placekey', { 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 Placekey connects.
Users add their Placekey 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 Placekey 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 Placekey from any agent.
ClaudeChatGPTCursor
Codex
VS CodeOpenAI Agents SDKClaude Agent SDK
Vercel AI SDK
Mastra
LangGraph
Placekey and Arc0, answered.
Can I use Placekey with Claude, ChatGPT or Cursor?
Yes. Connect Placekey 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 Placekey actions you allow.
How do users connect Placekey?
Users add their Placekey 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 Placekey actions can my agent take?
4 in total: 4 read, 0 write and 0 destructive. Your policies decide which of them each agent may call.
Can I make my agent read-only in Placekey?
Yes. Allow read actions and deny writes in the Placekey policy. Your agent can still look things up, and any write it attempts is blocked and logged.
Can my own backend call Placekey too?
Yes. The same Placekey connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Placekey into your agent.
Your users connect Placekey once, under your brand. Your agent gets 4 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan