Foursquare for AI agents
Foursquare provides location search and venue data, offering place details, recommendations, and geospatial information worldwide, used by apps that need local business and place data. 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 Foursquare.
Find nearby places
Search for venues near a location to answer a user's question about nearby options.
Pull a venue's details
Retrieve a place by its ID to get its address, hours, and tips before recommending it.
Read-only venue lookups
Keep every place lookup read-only, since Foursquare data here is for search and discovery only.
8 Foursquare actions, graded by risk.
Every Foursquare action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
7Look things up. Allowed by default.
- foursquare.get_trending_venuesGet trending venues
- foursquare.search_places_api_requestSearch places api request
- foursquare.validate_credentialValidate API credentials
- foursquare.retrieve_places_by_idRetrieve places by id
- foursquare.retrieve_nearby_places_v3Retrieve nearby places v3
- foursquare.retrieve_place_photos_by_idRetrieve place photos by id
- foursquare.retrieve_place_tips_using_fsq_idRetrieve place tips using fsq id
write
1Create and change things. Allow, or ask the user first.
- foursquare.autocomplete_placesAutocomplete places
destructive
0Delete, cancel or archive. Ask first, or deny outright.
- No destructive actions.
Foursquare in three steps.
- 01Your users connect FoursquareThey add their Foursquare api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, and writes like “autocomplete places” can wait for the user to approve.
- 03Any agent can actYour agent calls Foursquare through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('foursquare', { read: 'allow', write: 'ask', // autocomplete_places destructive: 'deny', }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Foursquare connects.
Users add their Foursquare 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 Foursquare 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 Foursquare from any agent.
Foursquare and Arc0, answered.
Can I use Foursquare with Claude, ChatGPT or Cursor?
Yes. Connect Foursquare 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 Foursquare actions you allow.
How do users connect Foursquare?
Users add their Foursquare 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 Foursquare actions can my agent take?
8 in total: 7 read, 1 write and 0 destructive, such as “autocomplete places”. Your policies decide which of them each agent may call.
Can I make my agent read-only in Foursquare?
Yes. Allow read actions and deny writes in the Foursquare policy. Your agent can still look things up, and any write it attempts is blocked and logged.
Can my own backend call Foursquare too?
Yes. The same Foursquare connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Foursquare into your agent.
Your users connect Foursquare once, under your brand. Your agent gets 8 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan