akenza (BYOK)

akenza (BYOK) — connector documentation

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

What akenza (BYOK) is for

akenza (BYOK) lets an AI assistant read your own akenza data through the akenza API with a key you supply (akenza API key). Read-only: 10 tools (get_organization, list_workspaces, list_devices, get_device, get_latest_sample, query_device_data, list_data_flows, list_device_connectors, list_tags, list_rules). 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.akenza.io. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by akenza. akenza 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:

• "Show my akenza organization details"
• "Which akenza workspaces do I have?"
• "Which devices are online in my akenza organization?"
• "Show the details of akenza device 02d2327fedce2128"
• "What was the latest reading from akenza device 02d2327fedce2128?"
• "Show the last 20 readings of akenza device 02d2327fedce2128"

What it does

• get_organization: Get one akenza organization by id: name and settings.
• list_workspaces: List the workspaces of an akenza organization with name, description and creation time.
• list_devices: List the devices (assets) of an akenza organization with connectivity, online state, tags and data flow. Optional text search.
• get_device: Get the details of one akenza device by its akenza id: name, connectivity, online timeout, tags and data flow.
• get_latest_sample: Get the most recent data sample a device sent: topic, timestamp and decoded data.
• query_device_data: Query the raw stored data of a device, newest first, optionally for one topic and a time range.
• list_data_flows: List the data flows of a workspace (device connector to output connector pipelines) with their names.
• list_device_connectors: List the device connectors of a workspace with connectivity type, carrier and provider. Secrets are not returned.
• list_tags: List the device tags of a workspace.
• list_rules: List the rules of a workspace with their name, description and inputs.

BYOK key

You bring your own akenza akenza API key (https://docs.akenza.io/device-management/managing-an-organization/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.akenza.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.api.akenza.io (the API this connector calls, with a BYOK key)

Live from the akenza API (api.akenza.io) with a BYOK key; documentation: https://docs.api.akenza.io. 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 akenza. akenza 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 akenza account.

Built for: Worldwide. Languages: English.

akenza (BYOK) — Privacy Policy

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

What akenza (BYOK) is. akenza (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own akenza data: Read your akenza IoT platform: workspaces, devices, latest sensor samples, raw device data, data flows, connectors, tags and rules with your own API key. You bring your own akenza akenza API key; the assistant sends it to us with each request.

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

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

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

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

akenza (BYOK) — Terms of Service

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

1. The Service. akenza (BYOK) provides: Read your akenza IoT platform: workspaces, devices, latest sensor samples, raw device data, data flows, connectors, tags and rules 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 akenza credentials and only access data you are allowed to access. akenza's terms apply to your use of akenza; 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 akenza. akenza 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 akenza returns, lightly trimmed; it may be incomplete, delayed or changed by akenza. Check important facts at the source.
5. Read-only. The Service does not create, change, send or delete anything in your akenza 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 akenza'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; akenza 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 akenza 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 akenza 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-akenza

akenza (BYOK) support

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

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