AI AGENT STORE / SERVICES

WEB DATA & EXTRACTION · FOR AI AGENTS

Foursquare Places API

Find and resolve real-world places using maintained location data.

Foursquare Places API supplies place search, details, autocomplete and matching for location-aware agents. It can turn a business name and location into candidate places and stable identifiers for later retrieval.

Your integration checklist

What you need from your owner
Create a developer account and service key, review the data-use terms and select fields and billing appropriate to the application. Confirm the current API version before adapting an older example.
Authentication
The new Places API uses Authorization: Bearer with a service key and X-Places-Api-Version. The documented current request uses places-api.foursquare.com and version 2025-06-17; legacy v3 examples use different conventions.
Your first task
Search for a known business in a specified area, compare candidate coordinates and address, and retrieve only the details needed for the task.
Billing & payment
Pricing depends on endpoint and requested fields. The current table includes 500 monthly free Pro calls; premium fields can change the request tier. Ask endpoints have separate rates. Check the actual request tier before scaling.
Agent payment support
Not verified. Programmatic usage does not establish autonomous checkout support.
Operational limits
Place records can be incomplete or stale, and similarly named branches can be confused. Legacy V3 endpoints have a published deprecation date. Search ranking does not establish that a venue is currently open or suitable.

ORIGINAL AI AGENT STORE INTEGRATION PLAYBOOK

Resolve the exact venue before using its details in a plan

Editorial recommendation · Reviewed 2026-11-08

When to choose this service

Choose Foursquare when an agent needs a maintained place index and matching service. A known venue’s own website may be enough for a one-off factual check.

A maintained place corpus and search infrastructure provide external observations that reasoning cannot reconstruct reliably. The underlying open dataset is an alternative for teams able to operate their own index.

Suggested workflow

  1. Specify the business name, geographic area and required fields. Keep the search radius narrow enough to distinguish branches.
  2. Compare candidate address, coordinates and category before selecting an identifier. Preserve alternatives when the evidence is ambiguous.
  3. Retrieve minimal details and confirm time-sensitive facts with the venue before relying on them. Track whether selected fields trigger premium billing.

Acceptance checks before real work

  • A matching name alone is insufficient for venue identity.
  • Absent hours or contact details are unknown rather than negative facts.
  • Changing requested fields can change the billing tier.

If the workflow fails

For an ambiguous match, widen the evidence rather than silently choosing the first result. For authentication failures, check the endpoint generation, bearer header and version together.

Provider documentation

Explore services for adjacent needs

Continue building your toolkit