Qubitro (BYOK)

Qubitro (BYOK) — connector documentation

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

What Qubitro (BYOK) is for

Qubitro (BYOK) lets an AI assistant read your own Qubitro data through the Qubitro API with a key you supply (Qubitro API key). Read-only: 10 tools (list_projects, get_project, list_devices, get_device, get_device_data, list_device_data_keys, list_aggregated_views, get_aggregated_data, list_dashboards, list_groups). 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.qubitro.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Qubitro. Qubitro 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:

• "Which Qubitro projects do I have?"
• "Show my Qubitro project details"
• "Which devices are in my Qubitro project, and when were they last seen?"
• "When did Qubitro device 7a1c2d3e last report?"
• "Show the latest temperature readings of Qubitro device 7a1c2d3e"
• "Which data fields does Qubitro device 7a1c2d3e report?"

What it does

• list_projects: List the Qubitro projects the API key can see, newest first, with name, description and tags.
• get_project: Get one Qubitro project by id.
• list_devices: List the devices of a project with brand, model, source, tags, metadata and last-seen time. Device credentials are not returned.
• get_device: Get one device of a project: brand, model, description, source, tags, metadata and last-seen time.
• get_device_data: Get stored telemetry records of a device, paged. Fields depend on the device (for example temperature, humidity, battery) plus a time field.
• list_device_data_keys: List the telemetry field names a device has stored (for example temperature, humidity).
• list_aggregated_views: List the continuous aggregations (aggregated views) defined for a device, with name and interval.
• get_aggregated_data: Get aggregated telemetry of a device from one continuous aggregation, paged, optionally for a time range or selected keys.
• list_dashboards: List the Qubitro dashboards with name, refresh period, tags and public flag.
• list_groups: List the organization groups of the Qubitro account.

BYOK key

You bring your own Qubitro Qubitro API key (https://docs.qubitro.com/platform/credentials/api-keys). 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.qubitro.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.

Data sources

• https://docs.qubitro.com/developers/qubitro-rest-api (the API this connector calls, with a BYOK key)

Live from the Qubitro API (api.qubitro.com) with a BYOK key; documentation: https://docs.qubitro.com/developers/qubitro-rest-api. 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 Qubitro. Qubitro 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 Qubitro account.

Built for: Worldwide. Languages: English.

Qubitro (BYOK) — Privacy Policy

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

What Qubitro (BYOK) is. Qubitro (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Qubitro data: Read your Qubitro IoT platform: projects, devices, last-seen times, stored telemetry, data keys, aggregated views and dashboards with your own API key. You bring your own Qubitro Qubitro API key; the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one Qubitro 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.qubitro.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 Qubitro 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 Qubitro receives. The request we make on your behalf, including the key and the arguments, under Qubitro's own terms and privacy policy. Qubitro acts at your direction and is the only recipient of the data of your request besides our hosting provider.

What we return. The answer Qubitro 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 Qubitro 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. Qubitro (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 Qubitro at any time to end all access.

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

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

Qubitro (BYOK) — Terms of Service

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

1. The Service. Qubitro (BYOK) provides: Read your Qubitro IoT platform: projects, devices, last-seen times, stored telemetry, data keys, aggregated views and dashboards with your own API key. It is accessed through an AI assistant or directly over MCP or HTTP, and is read-only.
2. Your own key, your own account. You must use your own Qubitro credentials and only access data you are allowed to access. Qubitro's terms apply to your use of Qubitro; 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 Qubitro. Qubitro 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 Qubitro returns, lightly trimmed; it may be incomplete, delayed or changed by Qubitro. Check important facts at the source.
5. Read-only. The Service does not create, change, send or delete anything in your Qubitro account.
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 Qubitro'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; Qubitro 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 Qubitro 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 Qubitro 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-qubitro

Qubitro (BYOK) support

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

• MCP endpoint: https://byok-qubitro.connectorbay.com/mcp
• REST API: https://byok-qubitro.connectorbay.com/openapi.json
• Live status: https://byok-qubitro.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. Qubitro (BYOK) never asks for them.