Rachio (BYOK)

Rachio (BYOK) — connector documentation

• MCP endpoint: https://byok-rachio-control.connectorbay.com/mcp
• REST API: POST https://byok-rachio-control.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-rachio-control.connectorbay.com/openapi.json
• Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
• Authentication: your own Rachio API token (Rachio app: Profile, API key, Copy), sent in the X-Upstream-Key header of every request (never stored, logged or cached)
• Health: https://byok-rachio-control.connectorbay.com/health · Tool schemas: https://byok-rachio-control.connectorbay.com/tools.json
• Publisher: Unify Dynamics LLC · connectorbay.com/byok-rachio-control · agent@connectorbay.com

What Rachio (BYOK) is for

Rachio (BYOK) lets an AI assistant read your own Rachio devices and, with your approval of each change, change their state through the Rachio API with a key you supply (API token (Rachio app: Profile, API key, Copy)). Read tools plus 3 device-changing tools (start_zone, stop_watering, set_rain_delay); each change runs only when confirm is yes, after you approved it in chat. 9 tools in all (get_person_id, get_person, get_device, get_current_schedule, list_upcoming_runs, get_zone, start_zone, stop_watering, set_rain_delay). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to api.rach.io. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Rachio. Rachio and its logos are trademarks of their owners and are used only to say which service the connector works with.

Ask your assistant things like:

• "What is my Rachio account id?"
• "Which Rachio controllers are on my account?"
• "Is my Rachio controller online and which zones does it have?"
• "Is my Rachio watering right now?"
• "When will my Rachio sprinklers run next?"
• "How is zone 4 configured in Rachio?"

What it does

• get_person_id: Get the Rachio person id that belongs to the token; needed for get_person.
• get_person: Get a Rachio person's username, creation date and their controllers (devices). Email and full name are not returned.
• get_device: Get one controller: name, online status, model, serial number, schedule mode, on/off and its zones and schedule rules.
• get_current_schedule: Get the schedule currently running on a controller, if any.
• list_upcoming_runs: List the scheduled watering runs for the next 14 days in start order, with schedule name, zones, durations and predicted skips.
• get_zone: Get one watering zone: number, name, enabled flag, runtime and last watered date.
• start_zone: Start watering one zone now for a number of seconds (capped here at 30 minutes). This changes the physical sprinkler controller and uses water.
• stop_watering: Stop all watering on a controller immediately. This changes the physical sprinkler controller and uses water.
• set_rain_delay: Set a rain delay on a controller so scheduled watering is skipped for a number of seconds; 0 clears the delay. This changes the physical sprinkler controller and uses water.

BYOK key

You bring your own Rachio API token (Rachio app: Profile, API key, Copy) (https://rachio.readme.io/reference/authentication). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to api.rach.io over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.

Data sources

• https://rachio.readme.io/reference/getting-started (the API this connector calls, with a BYOK key)

Live from the Rachio API (api.rach.io) with a BYOK key; documentation: https://rachio.readme.io/reference/getting-started. Endpoints checked against that documentation on 2026-10-16.

What it is not

Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Rachio. Rachio and its logos are trademarks of their owners and are used only to say which service the connector works with. It reads your Rachio data and can change device state only when a specific action is approved and confirmed (confirm = yes); it never deletes, resets, sends messages or creates paid resources.

Built for: Worldwide. Languages: English.

Rachio (BYOK) — Privacy Policy

Effective 24 October 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.

What Rachio (BYOK) is. Rachio (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Rachio data: Read your Rachio sprinkler controllers, zones and upcoming runs and start a zone, stop watering or set a rain delay with your own API token. You bring your own Rachio API token (Rachio app: Profile, API key, Copy); the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one Rachio call you asked for. Our application does not store it, write it to a log, put it in a cache, or share it. It is sent only to api.rach.io, over https, and is removed from any text we return to you or your assistant. We do not follow redirects with your key. If Rachio rejects it, we say so without repeating it.

What we receive. The arguments of each tool call, the BYOK key (for that call only), the technical headers needed to serve the request (an IP address or a client identifier supplied by the assistant) and standard server logs. What Rachio receives. The request we make on your behalf, including the key and the arguments, under Rachio's own terms and privacy policy. Rachio acts at your direction and is the only recipient of the data of your request besides our hosting provider.

What we return. The answer Rachio gives for your request, trimmed to the fields the tool documents. We do not keep it: it is returned to your assistant and not stored, cached or used to train anything.

What we do not do. We do not build a profile, sell or share personal information, or keep your Rachio data. Rate-limit counters (a client identifier and timestamps) are held in memory for at most 24 hours. Hosting access logs (IP addresses, request paths and status codes) are kept for up to 30 days for security and abuse prevention; our application adds no request headers or bodies to them.

Sub-processors. Rachio (the API you call with a BYOK key, at your direction). Hosting: Vercel (United States regions).

Your rights. Because we store no personal data beyond short-lived logs, requests to access, correct or delete data are usually satisfied automatically; you can still contact agent@connectorbay.com and we will respond within 30 days. Revoke your key at Rachio at any time to end all access.

Children. Rachio (BYOK) is a general-audience service operated by the adult using the assistant, under Rachio's own age rules.

Changes. We will post changes here with a new effective date.

Rachio (BYOK) — Terms of Service

Effective 24 October 2026. These terms govern use of the Rachio (BYOK) connector ("the Service") operated by Unify Dynamics LLC ("we", "us").

1. The Service. Rachio (BYOK) provides: Read your Rachio sprinkler controllers, zones and upcoming runs and start a zone, stop watering or set a rain delay with your own API token. It is accessed through an AI assistant or directly over MCP or HTTP, and can read the device data and change device state, but only through actions you approve in chat and confirm.
2. Your own key, your own account. You must use your own Rachio credentials and only access data you are allowed to access. Rachio's terms apply to your use of Rachio; you are responsible for complying with them, including any rate limits and permitted uses. Do not share a key you do not own.
3. Independent. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Rachio. Rachio and its logos are trademarks of their owners and are used only to say which service the connector works with.
4. No advice, no guarantees. Output is the data Rachio returns, lightly trimmed; it may be incomplete, delayed or changed by Rachio. Check important facts at the source.
5. Device changes. The Service changes the state of a Rachio device only through an action you approve in chat and pass with confirm = yes. It does not delete, reset, wipe, send messages or create paid resources.
6. Acceptable use. Automated use within the published rate limits is welcome. Do not use the Service to access data you are not entitled to, to circumvent Rachio's controls, or to attack any system.
7. Availability. The Service is provided "as is" without warranty. We may change, limit or discontinue it at any time; Rachio may change or end its API at any time.
8. Data. Our Privacy Policy describes what we process. In short: the BYOK key is used for the one call and not stored or logged.
9. Pro keys. Optional ConnectorBay Pro API keys are issued at our discretion and are separate from your Rachio key.
10. Liability. To the fullest extent permitted by law, Unify Dynamics LLC is not liable for any loss arising from use of or reliance on the Service, including any action Rachio takes on your account. Our total liability is limited to US $100.
11. Governing law. California law; venue in San Mateo County, California.
12. Contact. Unify Dynamics LLC · agent@connectorbay.com · https://connectorbay.com/byok-rachio-control

Rachio (BYOK) support

Email agent@connectorbay.com. We answer within two business days.

• MCP endpoint: https://byok-rachio-control.connectorbay.com/mcp
• REST API: https://byok-rachio-control.connectorbay.com/openapi.json
• Live status: https://byok-rachio-control.connectorbay.com/health

When you report a problem, include the question you asked your agent, roughly when, and which agent you used (for example Claude, ChatGPT or Gemini). Never send us passwords, account numbers or ID numbers. Rachio (BYOK) never asks for them.