# How to connect Beach Day API to OpenClaw (paste one key, 8 tools) > Connect Beach Day API to OpenClaw with ClawLink: paste your Beach Day API key once and 8 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/beach-day-api The usual route to Beach Day API access for OpenClaw is an MCP server you configure and keep running, plus your own OAuth app or API keys. ClawLink gives OpenClaw a more practical Beach Day API setup: install one ClawHub skill, connect Beach Day API in the browser, and OpenClaw can call real Beach Day API actions from any chat surface with no auth, token refresh, or tool wiring to build yourself. ## Setup It takes three steps to connect OpenClaw to Beach Day API. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Beach Day API** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask OpenClaw in plain English. **Paste this into OpenClaw to set up ClawLink:** > I want to connect my apps to OpenClaw through ClawLink. > Please install the ClawLink plugin from ClawHub and enable it: `openclaw plugins install clawhub:clawlink-plugin` > When it is installed, tell me and stop. After I reply, give me the ClawLink pairing link. Setup notes, if you need them: https://claw-link.dev/skill.md **Alternative for any agent (no plugin needed):** if the OpenClaw plugin route isn't available or doesn't work, any AI agent with shell access can use the ClawLink CLI instead: ```bash npx -y @useclawlink/cli login # sign in via browser — no API key to paste npx -y @useclawlink/cli connect beach-day-api # connect Beach Day API (browser OAuth) npx -y @useclawlink/cli actions beach-day-api # list available actions npx -y @useclawlink/cli run beach-day-api --input '' # execute (add --confirm for writes) ``` ### Install by command The setup prompt above does all of this in one paste. By hand, it is one install command plus a browser approval: ```bash openclaw plugins install clawhub:clawlink-plugin ``` Then ask OpenClaw to set up ClawLink. It starts browser pairing and prints an approval link — open it, approve the device, return to the chat, and say `done`. Finally, connect Beach Day API in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Beach Day API API key once. Verify the connection by asking OpenClaw: > Pull the relevant data from Beach Day API, summarize it in plain English, and point out anything that needs attention. ### Using a different agent? The OpenClaw plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI: ```bash npx -y @useclawlink/cli login ``` `login` opens the same browser approval and stores a credential locally. Once Beach Day API is connected in the dashboard, that agent calls the same 8 Beach Day API tools over MCP. Full setup for MCP clients and shell agents: [connect apps to any AI agent](https://claw-link.dev/learn/connect-apps-to-any-ai-agent). ## Beach Day API MCP for OpenClaw Looking for a Beach Day API MCP server for OpenClaw? ClawLink connects Beach Day API to OpenClaw and exposes 8 Beach Day API tools your agent can call over [MCP](https://claw-link.dev/learn/what-is-an-mcp-server), with [hosted auth](https://claw-link.dev/learn/oauth-for-ai-agents) and nothing to run or maintain yourself. Using Hermes instead? The [Hermes Beach Day API integration](https://claw-link.dev/hermes/beach-day-api) works the same way. ## What the OpenClaw Beach Day API integration can do 8 Beach Day API tools are ready for OpenClaw once the account is connected. ### All 8 Beach Day API tools for OpenClaw | Tool | What it does | |---|---| | **Get beach amenities** `beach_day_api_get_beach_amenities` | Get facilities and accessibility amenities for a beach without paying for the full beach profile | | **Get beach details** `beach_day_api_get_beach_details` | Get a full beach profile, including current score, water quality, weather, ocean conditions | | **Get beach rules** `beach_day_api_get_beach_rules` | Get activity rules for a beach without paying for the full beach profile | | **Get tide predictions** `beach_day_api_get_tide_predictions` | Get up to seven days of stored tide-prediction groups for a beach | | **List beach conditions** `beach_day_api_list_beach_conditions` | Return current and recent condition snapshots for a beach, including score, water quality | | **List beaches by score** `beach_day_api_list_beaches_by_score` | Return beaches ranked by current Beach Day Score from highest to lowest | | **List countries** `beach_day_api_list_countries` | List countries covered by Beach Day API with beach counts, ordered from highest to lowest count | | **Search beaches** `beach_day_api_search_beaches` | Find beaches by name, country, or state/province code and return IDs for detail, conditions | ## Example prompts **Get Beach Amenities** > Pull the relevant data from Beach Day API, summarize it in plain English, and point out anything that needs attention. **Get Beach Details** > Pull the relevant data from Beach Day API, summarize it in plain English, and point out anything that needs attention. **Get Beach Rules** > Pull the relevant data from Beach Day API, summarize it in plain English, and point out anything that needs attention. **Get Tide Predictions** > Pull the relevant data from Beach Day API, summarize it in plain English, and point out anything that needs attention. ## ClawLink vs. building it yourself The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Beach Day API working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Beach Day API API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Beach Day API account becomes available to the agent without you building credential management. | | **Ongoing maintenance** | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Beach Day API. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. | | **Agent usability** | You still need to expose the right Beach Day API actions to the runtime in a format your agent can reliably use. | 8 tools for Beach Day API are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Beach Day API to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for OpenClaw users instead. You install the plugin once, connect Beach Day API in the browser, and the 8 tools above work from chat. There is no SDK and no config file, and the Beach Day API key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full [Composio alternatives](https://claw-link.dev/hub/composio-alternatives) comparison. ### OpenClaw installed the Beach Day API skill but can't call the tools The ClawHub skill teaches OpenClaw about Beach Day API, but the calls run through the ClawLink plugin and your connected account. Make sure Beach Day API is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register. ### Connection succeeds but no tools appear Reconnect Beach Day API from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded. ### "Tool schema not loaded yet" error when calling Beach Day API tools Beach Day API tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every Beach Day API call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again. ### Beach Day API returns 403 or "permission denied" on one action while others work Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs. ### API key setup works but results look incomplete Double-check that the API key for Beach Day API has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Beach Day API integration? Yes. ClawLink is the fastest way to connect OpenClaw to Beach Day API: link your Beach Day API account once in the browser and OpenClaw can call the Beach Day API API through 8 ready-made tools — no custom code or token handling. ### How do I add Beach Day API to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Beach Day API skill from ClawHub, then you click Connect in the dashboard to authorize Beach Day API. OpenClaw calls the tools from the next message — no config files, and the Beach Day API key you paste is stored server-side instead of in your environment. ### How long does it take to connect Beach Day API to OpenClaw? About two minutes. Sign in, click Connect next to Beach Day API in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Beach Day API up myself? The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Beach Day API working from chat. ### OpenClaw installed the Beach Day API skill but can't call the tools The ClawHub skill teaches OpenClaw about Beach Day API, but the calls run through the ClawLink plugin and your connected account. Make sure Beach Day API is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register. ## Related - [GitHub tools](https://claw-link.dev/openclaw/github) — Manage repositories, issues, pull requests, and workflows - [PagerDuty tools](https://claw-link.dev/openclaw/pagerduty) — Manage incidents, on-call schedules, and services - [SafetyCulture](https://claw-link.dev/openclaw/safetyculture) — SafetyCulture (formerly iAuditor) is a workplace operations platform that enables teams to conduct digital inspections, manage audits, track issues, schedule tasks, and maintain compliance through mobile and web applications.