Install Jentic One Beta

Connect the Beach Day API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Beach Day API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fbeachdayapi.com%2Fbeachdayapi" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fbeachdayapi.com%2Fbeachdayapi" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Beach Day API.

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

GET STARTED

Start building with Beach Day API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Beach Day API for, with concrete tasks.

★ 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.

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.

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.

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

9 endpoints — the beach day api aggregates beach data, returning beaches, their conditions, rules, and amenities along with tide predictions.

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

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

Why Jentic?

What agents get from Jentic-routed access to this vendor.

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 isolation

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.

Intent-based discovery

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.

FAQs

Specific to using Beach Day API through Jentic.

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.

Beach Day API

AI ReadinessAI-Aware (B-)62/100

See full scorecard

Official vendor OpenAPI document · agent-readyMaps GeolocationPlaces Searchbearer9 EndpointsREST

For 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.

Use for: Find all beaches in a country, Get the conditions at a specific beach, Check the tide predictions for a beach, List the amenities at a beach

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

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.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A-Signals: 4

90%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

100%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: CSignals: 4

Example Density

How richly the API is illustrated with examples.

70%

Example Validity

Percentage of examples that conform to their schemas.

47%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: DSignals: 4

30%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

50%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: B-Signals: 1

60%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A-Signals: 1

79%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Beach Day API to your agent

Capabilities

Start building with Beach Day API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Beach Day API

Jentic AI Readiness Score

Beach Day API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness