canonical: https://jentic.com/apis/beachdayapi.com/beachdayapi

# Beach Day API

The Beach Day API aggregates beach data, returning beaches, their conditions, rules, and amenities along with tide predictions. It lists beaches, retrieves a single beach by id, reports current conditions such as water quality and weather, and returns a scored ranking of beaches for the day. Tide predictions are available per beach, and a countries endpoint lists where coverage exists.

## For AI agents

Look up beaches and their data: list beaches, read conditions and water quality, fetch rules and amenities, get tide predictions by beach, and retrieve today's scored beaches.

## Scope

Does not handle bookings, reservations, or payments. Use for reading beach data, conditions, and tide predictions only.

## Capabilities

- List beaches and retrieve a single beach by its id
- Read current beach conditions, including water quality and weather
- Get tide predictions for a beach by its beach_id
- Fetch a beach's posted rules and amenities
- Retrieve a scored ranking of beaches for the day

## Use cases

### AI Agent Beach Planning

An AI agent recommends where to go on a given day without a developer stitching together beach, tide, and weather sources. Through Jentic the agent lists beaches, reads their conditions, and checks tide predictions, while the bearer token stays on the developer's own machine.

Example prompt: List beaches in a country, read the conditions for each, and return the beach with the best scored conditions for today

### Beach Conditions Check

Apps that help people plan a trip to the coast need current conditions. The Beach Day API reports a beach's conditions, including water quality and weather, so an agent can tell a user whether a specific beach is worth the trip right now.

Example prompt: Get the current conditions for a beach by its id and summarize the water quality and weather

### Tide-Aware Scheduling

Some beach activities depend on the tide. The Beach Day API returns tide predictions for a beach by its beach_id, so an agent can schedule an outing around low or high tide and surface the posted rules and amenities for the chosen spot.

Example prompt: Fetch tide predictions for a beach by its beach_id and return the next low-tide window along with the beach's amenities

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/beaches/` | List beaches |
| GET | `/beaches/{id}/` | Get beach detail |
| GET | `/beaches/{id}/conditions/` | List beach conditions |
| GET | `/beaches/scored/` | Get scored beaches |
| GET | `/beaches/{id}/rules/` | Get beach rules |
| GET | `/beaches/{id}/amenities/` | Get beach amenities |
| GET | `/tides/{beach_id}/` | Get tide predictions |
| GET | `/countries/` | List available countries |

## Key resources

- **Beaches** — List beaches, retrieve a single beach, and read its conditions, rules, and amenities
- **Conditions** — Report current water quality and weather for a beach
- **Tides** — Return tide predictions for a beach by its beach_id
- **Countries** — List the countries where beach coverage exists

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 62 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 73 / 100
  - Developer Experience & Jentic Compatibility: 56 / 100
  - AI-Readiness & Agent Experience: 45 / 100
  - Agent Usability: 94 / 100
  - Security: 60 / 100
  - AI Discoverability: 79 / 100
- **View full report:** https://jentic.com/apis/beachdayapi.com/beachdayapi/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring the Beach Day API by hand means supplying its bearer token and stitching beach, condition, and tide lookups together yourself. Through Jentic you install once, import Beach Day from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** The Beach Day API is read-only, so a rule limits the agent to the lookups you choose, such as listing beaches and reading conditions. You pick which operations it may call, and nothing beyond those is reachable.
- **Credential handling:** Your Beach Day token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'find beach conditions' or 'get tide predictions', and Jentic returns the matching Beach Day operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **OpenTripMap** — OpenTripMap returns points of interest and place details across broad categories, not beach-specific conditions.
- **Foursquare Places** — Foursquare searches places and venues with rich attributes but no tide or water-quality data.
- **OpenWeatherMap** — OpenWeatherMap supplies forecasts that complement Beach Day's conditions and tide data.

## FAQ

### Is there a Beach Day API MCP server?

You don't need an MCP server to give your agent the Beach Day API. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent calls it. Operations are discovered on demand, so nothing extra loads into the agent's context.

### Can I limit what my agent is allowed to do with the Beach Day API?

Yes. Because the API only reads data, a rule can allow just the beach and condition lookups the agent needs, keeping it from calling the tide or country endpoints unless you add them, and every call is logged.

### What authentication does the Beach Day API use?

The Beach Day API authenticates with a bearer token, as declared in its OpenAPI spec. The health-check endpoint is public and needs no credential, while the data endpoints expect the token. Through Jentic the token is stored encrypted by your own Jentic One instance and injected at call time.

### Can I get tide predictions with the Beach Day API?

Yes. The tides operation returns tide predictions for a beach identified by its beach_id, which you can pair with the beach's conditions and amenities to plan an outing around the tide.

### How do I find beach conditions through Jentic?

Install Jentic One with `curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh`, then import the Beach Day API from the Jentic API Directory and store your token. Your agent searches for 'find beach conditions' and Jentic returns the conditions operation with its input schema. To run it on your own infrastructure, install Jentic One from its GitHub repo.

### What are the rate limits for the Beach Day API?

The Beach Day OpenAPI spec does not define rate limits. It is a read-only data API, so check the Beach Day developer documentation for the quota that applies to your key.