# auth.md: PlayaBueno API access

**No authentication is required, and none is offered.**

Every PlayaBueno API endpoint is public, read-only JSON over HTTPS. There is
no sign-up, no API key, no OAuth client registration and no token endpoint.
Call the endpoints directly.

This page used to describe an OAuth flow, and the site published
`/.well-known/openid-configuration` and `/.well-known/oauth-authorization-server`
alongside it. Those documents advertised an authorization endpoint, a token
endpoint, a JWKS URI and three grant types — all of which returned HTTP 501.
An agent that followed the discovery chain did real work to reach a dead end.
The documents have been removed rather than left to mislead.

## Endpoints

| Endpoint | Returns |
| --- | --- |
| `GET /api/search?q=` | Cross-entity search (beaches, hotels, cities, states, guides) |
| `GET /api/beaches?q=&city=&state=&region=&ratingMin=&limit=&offset=` | Beach directory listings |
| `GET /api/beaches/{slug}` | A single beach |
| `GET /api/resorts`, `GET /api/resorts/{slug}` | Hotel listings |
| `GET /api/cities`, `GET /api/cities/{slug}` | Cities |
| `GET /api/states`, `GET /api/states/{slug}` | States |
| `GET /api/map/places?scope=&slug=` | GeoJSON for the map |
| `GET /api/status` | Health check |

Machine-readable description: [`/openapi.json`](https://www.playabueno.com/openapi.json).

## Discovery entry points

- Model Context Protocol (MCP): `/.well-known/mcp/server-card.json` (endpoint: `/api/mcp`)
- API catalog: `/.well-known/api-catalog`
- ARD manifest: `/.well-known/ai-catalog.json`
- Agent skills index: `/.well-known/agent-skills/index.json`
- Markdown rendering of any page: send `Accept: text/markdown`
- LLM summary index: `/llms.txt`
- Full LLM directory context: `/llms-full.txt`

## Fair use

Please keep to roughly one request per second and identify your agent in the
`User-Agent` header. Ratings and review counts originate from Google Places;
attribute them accordingly.
