Cloudflare Databases (BYOK)
Read your Cloudflare D1 databases and Hyperdrive connection configurations (no passwords, no queries) with your own API token
Read your Sensibo smart air conditioner controllers and room sensors: devices, AC state history, measurements, events, timers and schedules with your own API key
Unify Dynamics LLC
Real questions, and the tools your agent calls to answer them.
list_devicesget_devicelist_ac_statesget_historical_measurementslist_device_eventslist_door_sensor_eventsSensibo (BYOK) lets an AI assistant read your own Sensibo data through the Sensibo API with a key you supply (Sensibo API key). Read-only: 10 tools (list_devices, get_device, list_ac_states, get_historical_measurements, list_device_events, list_door_sensor_events, get_timer, list_schedules, get_schedule, get_climate_react). 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 home.sensibo.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Sensibo. Sensibo and its logos are trademarks of their owners and are used only to say which service the connector works with.
Sources: Live from the Sensibo API (home.sensibo.com) with a BYOK key; documentation: https://support.sensibo.com/api/. Endpoints checked against that documentation on 2026-10-16.
The publisher, Unify Dynamics LLC, states that tool inputs are processed in memory and not retained.
10 tools, grouped by job. Every one is read-only or compute-only.
https://byok-sensibo.connectorbay.com/mcpThree ways in, the same 10 tools.
https://byok-sensibo.connectorbay.com/mcpPOST https://byok-sensibo.connectorbay.com/v1/tools/<tool>https://connectorbay.com/openai/byok-sensibo.jsonhttps://connectorbay.com/v1/chat/completions · how it worksX-Upstream-Key header (get one at home.sensibo.com).Sensibo (BYOK) lets an AI assistant read your own Sensibo data through the Sensibo API with a key you supply (Sensibo API key). It is a hosted MCP server with 10 tools such as List devices, Get device, List ac states, Get historical measurements, List device events, List door sensor events, published by Unify Dynamics LLC. It is independent and not affiliated with Sensibo.
Add the MCP endpoint https://byok-sensibo.connectorbay.com/mcp to your client's MCP, connector or integration settings (streamable HTTP, no OAuth). For REST, POST JSON to https://byok-sensibo.connectorbay.com/v1/tools/<tool>; the OpenAPI description is at /openapi.json. For OpenAI function calling, load https://connectorbay.com/openai/byok-sensibo.json.
Yes: this is a bring-your-own-key connector. Create a Sensibo API key at https://home.sensibo.com/me/api and send it in the X-Upstream-Key header. ConnectorBay uses it for that one call only and never stores, logs or caches it.
Yes. Every tool reads or computes. Nothing is created, changed, sent, paid or deleted in your account.
Yes. It is free to use within the published rate limits; an optional Pro key raises them. There is no account to create.
Read your Cloudflare D1 databases and Hyperdrive connection configurations (no passwords, no queries) with your own API token
Read your Cloudflare WARP device posture rules and integrations, device settings profiles, managed networks, client versions and deployment groups with your own API token
Read your Cloudflare Digital Experience Monitoring synthetic tests, test analytics overview, live fleet status totals and colo list with your own API token
Read your Cloudflare Zero Trust data loss prevention profiles, entries, datasets, data classes, validators and usage limits with your own API token
Read your Cloudflare DNS settings, DNSSEC status, DNS analytics, DNS Firewall clusters, secondary DNS and custom nameservers, with your own API token
Read your Cloudflare Email Routing settings, DNS records, routing rules and verified destination addresses with your own API token
https://byok-sensibo.connectorbay.com/mcpPOST https://byok-sensibo.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-sensibo.connectorbay.com/openapi.jsonX-Upstream-Key header of every request (never stored, logged or cached)https://byok-sensibo.connectorbay.com/health · Tool schemas: https://byok-sensibo.connectorbay.com/tools.jsonSensibo (BYOK) lets an AI assistant read your own Sensibo data through the Sensibo API with a key you supply (Sensibo API key). Read-only: 10 tools (list_devices, get_device, list_ac_states, get_historical_measurements, list_device_events, list_door_sensor_events, get_timer, list_schedules, get_schedule, get_climate_react). 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 home.sensibo.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Sensibo. Sensibo 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:
list_devices: List the Sensibo devices on the account. Use the fields parameter to choose which properties come back, or * for all.get_device: Get one Sensibo device with its current state. Use fields to pick properties or * for all.list_ac_states: List the most recent AC states set on a device (latest first), at most 20.get_historical_measurements: Get temperature and humidity measurements of a device over the last number of days.list_device_events: List events recorded for a device (such as state changes and connections) over the last days.list_door_sensor_events: List open and close events of a Sensibo door and window sensor over the last days.get_timer: Get the timer currently set on a device, if there is one.list_schedules: List the AC schedules of a device.get_schedule: Get one schedule of a device by schedule id.get_climate_react: Get the Climate React (smart mode) settings of a device.You bring your own Sensibo Sensibo API key (https://home.sensibo.com/me/api). 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 home.sensibo.com 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.
Live from the Sensibo API (home.sensibo.com) with a BYOK key; documentation: https://support.sensibo.com/api/. Endpoints checked against that documentation on 2026-10-16.
Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Sensibo. Sensibo and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your Sensibo account.
Built for: Worldwide. Languages: English.
Effective 24 October 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.
What Sensibo (BYOK) is. Sensibo (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Sensibo data: Read your Sensibo smart air conditioner controllers and room sensors: devices, AC state history, measurements, events, timers and schedules with your own API key. You bring your own Sensibo Sensibo API key; the assistant sends it to us with each request.
BYOK key. The key you supply is used to make the one Sensibo 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 home.sensibo.com, over https, and is removed from any text we return to you or your assistant. We do not follow redirects with your key. If Sensibo 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 Sensibo receives. The request we make on your behalf, including the key and the arguments, under Sensibo's own terms and privacy policy. Sensibo acts at your direction and is the only recipient of the data of your request besides our hosting provider.
What we return. The answer Sensibo 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 Sensibo 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. Sensibo (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 Sensibo at any time to end all access.
Children. Sensibo (BYOK) is a general-audience service operated by the adult using the assistant, under Sensibo's own age rules.
Changes. We will post changes here with a new effective date.
Effective 24 October 2026. These terms govern use of the Sensibo (BYOK) connector ("the Service") operated by Unify Dynamics LLC ("we", "us").
Email agent@connectorbay.com. We answer within two business days.
https://byok-sensibo.connectorbay.com/mcphttps://byok-sensibo.connectorbay.com/openapi.jsonWhen 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. Sensibo (BYOK) never asks for them.