Particle (BYOK)

Particle (BYOK) — connector documentation

• MCP endpoint: https://byok-particle-control.connectorbay.com/mcp
• REST API: POST https://byok-particle-control.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-particle-control.connectorbay.com/openapi.json
• Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
• Authentication: your own Particle access token (a scoped token with devices:list, devices:get, devices.variable:get and devices.function:call), sent in the X-Upstream-Key header of every request (never stored, logged or cached)
• Health: https://byok-particle-control.connectorbay.com/health · Tool schemas: https://byok-particle-control.connectorbay.com/tools.json
• Publisher: Unify Dynamics LLC · connectorbay.com/byok-particle-control · agent@connectorbay.com

What Particle (BYOK) is for

Particle (BYOK) lets an AI assistant read your own Particle devices and, with your approval of each change, change their state through the Particle API with a key you supply (access token (a scoped token with devices:list, devices:get, devices.variable:get and devices.function:call)). Read tools plus 1 device-changing tools (signal_device); each change runs only when confirm is yes, after you approved it in chat. 4 tools in all (list_devices, get_device, read_variable, signal_device). 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.particle.io. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Particle. Particle 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 of my Particle devices are online?"
• "Which functions does Particle device 0123456789abcdef01234567 expose?"
• "What is the temperature variable of Particle device 0123456789abcdef01234567?"
• "Make my Particle device 0123456789abcdef01234567 flash its LED"

What it does

• list_devices: List the devices claimed to the account, most recently connected first, with online flag, platform, firmware and last contact time.
• get_device: Get one device by ID: online flag, platform, firmware version, last contact, and the names of the functions and variables it exposes.
• read_variable: Read the current value of one cloud variable a device exposes (for example a temperature or counter). The device must be online.
• signal_device: Start or stop the rainbow LED pattern on a device so it can be found physically. This changes the LED state of the device.

BYOK key

You bring your own Particle access token (a scoped token with devices:list, devices:get, devices.variable:get and devices.function:call) (https://docs.particle.io/reference/cloud-apis/access-tokens/). 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.particle.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://docs.particle.io/reference/cloud-apis/api/ (the API this connector calls, with a BYOK key)

Live from the Particle API (api.particle.io) with a BYOK key; documentation: https://docs.particle.io/reference/cloud-apis/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 Particle. Particle and its logos are trademarks of their owners and are used only to say which service the connector works with. It reads your Particle 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.

Particle (BYOK) — Privacy Policy

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

What Particle (BYOK) is. Particle (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Particle data: Read your Particle IoT devices and cloud variables, call a device function and flash a device LED to find it, with your own access token. You bring your own Particle access token (a scoped token with devices:list, devices:get, devices.variable:get and devices.function:call); the assistant sends it to us with each request.

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

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

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

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

Particle (BYOK) — Terms of Service

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

1. The Service. Particle (BYOK) provides: Read your Particle IoT devices and cloud variables, call a device function and flash a device LED to find it, with your own access 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 Particle credentials and only access data you are allowed to access. Particle's terms apply to your use of Particle; 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 Particle. Particle 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 Particle returns, lightly trimmed; it may be incomplete, delayed or changed by Particle. Check important facts at the source.
5. Device changes. The Service changes the state of a Particle 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 Particle'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; Particle 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 Particle 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 Particle 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-particle-control

Particle (BYOK) support

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

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