# Foursquare — API Agent Score

> Score: 71/100 (Grade: B) | Domain: foursquare.com | Rubric: 1.0.0 | Checked: July 24, 2026

Foursquare scored 71/100 (B), classified "partially-ready".

[View full report](https://www.postman.com/ai/ai-ready-apis/company/foursquare)
[All organizations](https://www.postman.com/ai/ai-ready-apis/llms.txt)

## Summary

- Overall: 71/100 (B)
- Classification: partially-ready

## Category Scores

- API Design: 61/100 (C)
- Developer Experience: 74/100 (B)
- Agent Discovery: 73/100 (B)
- Agent Understanding: 77/100 (B)
- Agent Usability: 72/100 (B)

## Check Results

### API Design

- [warn] Schema coverage & depth — 0/141 (0%) public params are fully typed (no any/**kwargs). Analyzer reports not all methods have a derivable input schema. Investigated: sdk 60%.
- [pass] Example coverage — README is present and includes a runnable quickstart. Investigated: sdk 100%.
- [fail] Security & governance hygiene — No security.txt at /.well-known/security.txt or /security.txt. Investigated: wellknown 0%.
- [skip] Machine-readable, versioned contract — No surface produced evidence for this capability in this run.
- [skip] Auth declared & discoverable — No surface produced evidence for this capability in this run.

### Developer Experience

- [pass] Self-service developer portal — Self-service signup at https://app.foursquare.com/signup; no free tier or sandbox language detected. Investigated: docs 100%.
- [pass] Description completeness — 69/69 operations carry a description. Investigated: sdk 100%.
- [warn] Quickstart present — Quickstart page reachable (2 variants scanned starting at https://docs.foursquare.com/) but no runnable code sample detected in HTML or .md variant. Investigated: docs 50%.
- [fail] Changelog published — Official SDKs stale: newest activity 548 days ago. Investigated: sdk 0%.
- [skip] Code samples in docs — No surface produced evidence for this capability in this run.

### Agent Discovery

- [pass] Registry & SDK presence — Indexed on Context7 (websites/foursquare, 8737 snippets). Investigated: docs 100%, sdk 50%, cli 0%.
- [warn] llms.txt present, valid & comprehensive — Could not test any pages; 1 failed to fetch. Investigated: docs 60%, sdk 0%.
- [warn] Docs reachable, not hard auth-gated — 1 JavaScript redirect(s) detected across 1 pages. Investigated: docs 50%.
- [warn] Crawlable / AEO — No sitemap discoverable via robots.txt or /sitemap.xml on the docs host. Investigated: wellknown 50%.

### Agent Understanding

- [pass] Machine-readable errors (RFC 9457) — Single base error "FoursquareException" with 11 subclasses. Investigated: sdk 100%.
- [warn] Agent-navigable, token-efficient docs — No pages support .md URLs (0/1 tested). Investigated: docs 69%.
- [fail] Agent instructions file (AGENTS.md) — No AGENTS.md at the site root or /.well-known/. Investigated: wellknown 0%.
- [skip] Operation purpose clarity — No surface produced evidence for this capability in this run.
- [skip] Docs structured data — No surface produced evidence for this capability in this run.
- [skip] Description consistency across surfaces — Only 1 surface description(s) with ≥6 tokens available; need at least 2 to compare.

### Agent Usability

- [pass] Idempotency documented — Built-in retry machinery is present (grep-derived). Investigated: sdk 100%.
- [warn] Sandbox separation — No test-mode flag or sandbox environment is exposed. Investigated: sdk 50%.
- [fail] Runnable collection with test scripts — No public Postman workspace discovered for the org. Investigated: platform 0%.
- [skip] Rate-limit signaling — No surface produced evidence for this capability in this run.
- [skip] Pagination documented & consistent — No surface produced evidence for this capability in this run.

## Executive Summary

Foursquare's API program shows solid fundamentals in onboarding and documentation reachability, but two areas demand immediate attention to protect partner and agent outcomes. Security governance gaps in the API design create trust and compliance risks that can block enterprise partner deals before they start, while the absence of a changelog, agent instruction file, and runnable collection leaves partners — and the AI agents they increasingly rely on — without the context needed to integrate confidently and keep pace with API changes. Closing these gaps should be the top priority before expanding the partner program.