Foursquare provides location-based search and discovery, offering detailed venue information, place recommendations, and geospatial data for businesses and points of interest worldwide
Foursquare provides location-based search and discovery, offering detailed venue information, place recommendations, and geospatial data for businesses and points of interest worldwide On Nagent, Foursquare is exposed as a fully-configurable analytics integration that any agent can call — 5 actions, and API key authentication. No code is required to wire Foursquare into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Foursquare to automate the kinds of tasks analytics teams previously handled manually. Concrete examples — each one is a single agent step in Nagent — include:
Every action and trigger is paired with a structured input/output schema (visible in the sections below), so when you wire Foursquare into Helix — our agentic agent builder — the editor knows exactly what each step expects and produces. Configure once, deploy anywhere across your Nagent agents.
Every operation an agent can call against Foursquare, with input parameters and output schema. Drop these into any step of an agent built in Helix.
FOURSQUARE_RETRIEVE_NEARBY_PLACES_V3The GetNearbyPlaces endpoint retrieves a list of places near a specified location, primarily supporting check-in use cases and local discovery. It returns points of interest (POIs) including lower quality results not found in the standard Place Search, enhancing location-based experiences with additional data like photos, reviews, and tips. This endpoint is ideal for applications seeking to provide users with a comprehensive view of their surroundings, including less prominent or newer locations. While it offers a broader range of results, it may sacrifice some precision compared to more focused search endpoints. Use this when you want to offer users a diverse array of nearby options, particularly for social check-in features or exploratory local recommendations.
Input parameters
The latitude/longitude around which to retrieve place information. This must be specified as latitude,longitude (e.g., ll=41.8781,-87.6298). If you do not specify ll, the server will attempt to retrieve the IP address from the request, and geolocate that IP address.
The estimated horizontal accuracy radius in meters of the user's location at the 68th percentile confidence level as returned by the user's cell phone OS.
The number of results to return, up to 50. Defaults to 10.
Indicate which fields to return in the response, separated by commas. Core fields include: fsq_id, name, geocodes (main and other lat/lng coordinates for place), location, categories, chains, timezone, distance, and link (to place detail). Rich data fields include: description, tel (phone), fax, email, website, social_media, hours, hours_popular, rating, stats, popularity, price, menu, date_closed, photos, tips (mini reviews), tastes, and features (e.g., wifi, reservations). If no fields are specified, all Core Fields are returned by default.
The altitude of the user's location in meters above the World Geodetic System 1984 (WGS84) reference ellipsoid as returned by the user's cell phone OS.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FOURSQUARE_RETRIEVE_PLACE_PHOTOS_BY_IDRetrieves photos associated with a specific place in Foursquare's database. This endpoint allows you to access user-generated images for a particular point of interest (POI) using its unique Foursquare ID (fsq_id). It's useful for enhancing your application with visual content related to locations, such as restaurants, landmarks, or businesses. The endpoint returns photo data that can be used to construct image URLs for display. Keep in mind that the number and quality of photos may vary depending on the popularity and user engagement of the place. This tool should be used when you need to display or analyze visual information about a specific location in your application.
Input parameters
Specifies the order in which results are listed. Possible values are:<ul><li>popular (default) - sorts results based on their popularity among Foursquare users, newest - sorts results from most recently added to least recently added
The specified number of photos per page. Returns 10 photos by default, up to a maximum number of 50.
A unique string identifier for a FSQ Place (formerly known as Venue ID). E.g., Foursquare HQ"s fsq_id = 5a187743ccad6b307315e6fe
Restricts the results to photos matching the specified classifications, separated by a comma. Possible values are: food - photos of food, indoor - photos of indoors, menu - photos of menus, outdoor - photos of storefronts, outdoors, and exteriors
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FOURSQUARE_RETRIEVE_PLACES_BY_IDRetrieves detailed information about a specific place using its unique Foursquare ID (FSQ ID). This endpoint provides comprehensive data about a venue, including its name, address, category, ratings, tips, photos, and other relevant information. It's particularly useful when you need in-depth details about a known location, such as for displaying venue profiles or gathering specific place attributes. The endpoint should be used when you have a valid FSQ ID and require the most up-to-date and complete information about that place. Note that this endpoint focuses on individual place details and does not provide search functionality or lists of multiple venues.
Input parameters
Indicate which fields to return in the response, separated by commas. Core fields include: fsq_id, name, geocodes (main and other lat/lng coordinates for place), location, categories, chains, timezone, distance, and link (to place detail). Rich data fields include: description, tel (phone), fax, email, website, social_media, hours, hours_popular, rating, stats, popularity, price, menu, date_closed, photos, tips (mini reviews), tastes, and features (e.g., wifi, reservations). If no fields are specified, all Core Fields are returned by default.
A unique string identifier for a FSQ Place (formerly known as Venue ID). E.g., Foursquare HQ"s fsq_id = 5a187743ccad6b307315e6fe
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FOURSQUARE_RETRIEVE_PLACE_TIPS_USING_FSQ_IDRetrieves user-generated tips for a specific place in the Foursquare database. This endpoint allows you to fetch valuable insights and experiences shared by Foursquare users about a particular venue. It's useful for enhancing location-based applications with real user feedback, helping users make informed decisions about places they might visit. The endpoint returns a list of tips, which may include information such as the tip text, the user who created it, and potentially a timestamp or rating.
Input parameters
Specifies the order in which results are listed. Possible values are: popular (default) - sorts results based on their popularity among Foursquare users, newest - sorts results from most recently added to least recently added
The specified number of tips per page. Returns 10 tips by default, up to a maximum number of 50.
Indicate which fields to return in the response, separated by commas. Supported fields are: id - The ID of the tip to be returned, created_at - The timestamp indicating when the tip was created; UNIX timestamp in seconds since Epoch, text - The text of the returned tip, lang - The language of the returned tip, url - The URL associated with the returned tip, agree_count - The count of users who have agreed with the returned tip, disagree_count - The count of users who have disagreed with the returned tip, photo - The ID of the photo asociated with the returned tip. Default fields if this param is omitted are "id", "created_at", and "text".
A unique string identifier for a FSQ Place (formerly known as Venue ID). E.g., Foursquare HQ"s fsq_id = 5a187743ccad6b307315e6fe
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FOURSQUARE_SEARCH_PLACES_API_REQUESTThe GetPlacesSearch endpoint allows you to search for places in the Foursquare database based on various criteria such as location, keywords, and categories. This tool is ideal for discovering nearby points of interest or finding specific venues. It returns a list of places matching the specified parameters, providing essential information about each location. Use this endpoint for location-based features or gathering venue information in a specific area.
Input parameters
The latitude/longitude around which to retrieve place information. This must be specified as latitude,longitude (e.g., ll=41.8781,-87.6298).
The latitude/longitude representing the north/east points of a rectangle. Must be used with sw parameter to specify a rectangular search box. Global search results will be omitted.
The latitude/longitude representing the south/west points of a rectangle. Must be used with ne parameter to specify a rectangular search box. Global search results will be omitted.
A string naming a locality in the world (e.g., "Chicago, IL"). If the value is not geocodable, returns an error. Global search results will be omitted.
The number of results to return, up to 50. Defaults to 10.
A string to be matched against all content for this place, including but not limited to venue name, category, telephone number, taste, and tips.
Indicate which fields to return in the response, separated by commas. Core fields include: fsq_id, name, geocodes (main and other lat/lng coordinates for place), location, categories, chains, timezone, distance, and link (to place detail). Rich data fields include: description, tel (phone), fax, email, website, social_media, hours, hours_popular, rating, stats, popularity, price, menu, date_closed, photos, tips (mini reviews), tastes, and features (e.g., wifi, reservations). If no fields are specified, all Core Fields are returned by default.
Sets a radius distance (in meters) used to define an area to bias search results. The maximum allowed radius is 100,000 meters. Radius can be used in combination with ll or ip biased geolocation only. By using radius, global search results will be omitted. If not provided, default radius applied is 22000 meters.
Support local day and local time requests through this parameter. To be specified as DOWTHHMM (e.g., 1T2130), where DOW is the day number 1-7 (Monday = 1, Sunday = 7) and time is in 24 hour format. Places that do not have opening hours will not be returned if this parameter is specified. Cannot be specified in conjunction with `open_now`.
Restricts results to only those places that are open now. Places that do not have opening hours will not be returned if this parameter is specified. Cannot be specified in conjunction with `open_at`.
Restricts results to only those places within the specified price range. Valid values range between 1 (most affordable) to 4 (most expensive), inclusive.
Restricts results to only those places within the specified price range. Valid values range between 1 (most affordable) to 4 (most expensive), inclusive.
A Foursquare Venue ID to use as search bounds so only places within that venue are returned
Filters the response by only returning FSQ Places that are not known to be part of any chain.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
No publicly available marketplace agent is found using this tool yet. There are 43 agents privately built on Nagent that already use Foursquare.
Build on Nagent
Connect Foursquare to any Nagent agent in minutes — no API key management, no boilerplate. Just configure and deploy.
The five questions agent builders ask before adopting a new integration.
Open the External Integrations panel inside Nagent (app.nagent.ai/externalIntegration), find Foursquare, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Foursquare is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Foursquare is connected, you configure its 5 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Foursquare steps into any workflow visually. Pick an action (e.g., one of those listed above), fill in the inputs (Helix knows the required vs. optional schema for each parameter), and connect it to upstream/downstream steps. Triggers run as the entry point of an agent, so when a Foursquare event fires, the agent kicks off automatically.
Every Foursquare action and trigger ships with a fully-typed schema — input parameters with name, type, required flag, and description, plus the output payload shape. The schemas are documented in the sections above. Helix uses these schemas to validate your configuration at build time and to type-check the data flowing between steps.
Yes. While Foursquare ships with 5 pre-built analytics actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Foursquare together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Foursquare-based workflows tailored to your business.