Logz.io (BYOK)

Logz.io (BYOK) — connector documentation

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

What Logz.io (BYOK) is for

Logz.io (BYOK) lets an AI assistant read your own Logz.io data through the Logz.io API with a key you supply (Logz.io API token (Tools > Manage tokens > API tokens)). Read-only: 7 tools (whoami, list_associated_accounts, list_alerts, list_log_types, list_notification_endpoints, list_users, search_logs). 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.logz.io, api-eu.logz.io, api-au.logz.io, api-ca.logz.io, api-uk.logz.io. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Logz.io. Logz.io 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 Logz.io account is my API token for?"
• "Which sub-accounts does my Logz.io account have?"
• "Which Logz.io alerts are enabled?"
• "What log types does my Logz.io account receive?"
• "Where do my Logz.io alerts send notifications?"
• "Who has access to my Logz.io account?"

What it does

• whoami: Show the Logz.io account the token belongs to: account name and id. The answer shape is not documented, so it is returned as the API sends it, trimmed.
• list_associated_accounts: List the accounts derived from the token's account: all sub-accounts and the owner account for an owner token, otherwise just the one account. The answer shape is not documented, so it is returned as the API sends it, trimmed.
• list_alerts: List the log alerts with title, description, tags, enabled flag, search window in minutes, schedule and last update.
• list_log_types: List the log types known to the account.
• list_notification_endpoints: List the alert notification endpoints (Slack, PagerDuty, email hooks and others) configured in the account. The answer shape is not documented, so it is returned as the API sends it, trimmed.
• list_users: List the users of the Logz.io account, optionally for one sub-account. The answer shape is not documented, so it is returned as the API sends it, trimmed.
• search_logs: Search the account's logs with a Lucene query string. By default only today's and yesterday's data (UTC) is searched; shift the window with day_offset or add a timestamp range to the query. Wildcards must not start with * or ?. Returns the raw search response, trimmed.

BYOK key

You bring your own Logz.io Logz.io API token (Tools > Manage tokens > API tokens) (https://app.logz.io/#/dashboard/settings/manage-tokens/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 api.logz.io, api-eu.logz.io, api-au.logz.io, api-ca.logz.io, api-uk.logz.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://api-docs.logz.io/docs/logz/logz-io-api/ (the API this connector calls, with a BYOK key)

Live from the Logz.io API (api.logz.io, api-eu.logz.io, api-au.logz.io, api-ca.logz.io, api-uk.logz.io) with a BYOK key; documentation: https://api-docs.logz.io/docs/logz/logz-io-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 Logz.io. Logz.io 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 Logz.io account.

Built for: Worldwide. Languages: English.

Logz.io (BYOK) — Privacy Policy

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

What Logz.io (BYOK) is. Logz.io (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Logz.io data: Read your Logz.io account info, alerts, notification endpoints, users, log types and search your logs with your own API token (US, EU, AU, CA and UK regions). You bring your own Logz.io Logz.io API token (Tools > Manage tokens > API tokens); the assistant sends it to us with each request.

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

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

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

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

Logz.io (BYOK) — Terms of Service

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

1. The Service. Logz.io (BYOK) provides: Read your Logz.io account info, alerts, notification endpoints, users, log types and search your logs with your own API token (US, EU, AU, CA and UK regions). 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 Logz.io credentials and only access data you are allowed to access. Logz.io's terms apply to your use of Logz.io; 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 Logz.io. Logz.io 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 Logz.io returns, lightly trimmed; it may be incomplete, delayed or changed by Logz.io. Check important facts at the source.
5. Read-only. The Service does not create, change, send or delete anything in your Logz.io 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 Logz.io'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; Logz.io 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 Logz.io 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 Logz.io 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-logzio

Logz.io (BYOK) support

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

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