Luciq (BYOK)

Luciq (BYOK) — connector documentation

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

What Luciq (BYOK) is for

Luciq (BYOK) lets an AI assistant read your own Luciq data through the Luciq API with a key you supply (Luciq Query API key (starts with lq_)). Read-only: 7 tools (list_entities, get_rate_limit, query_crash_free_sessions, query_sessions_by_os_version, query_top_failing_endpoints, query_top_crash_groups, query_entity_metric). 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.luciq.ai. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Luciq. Luciq 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 Luciq data and metrics can my key query?"
• "How many Luciq API requests do I have left this minute?"
• "What was our crash-free session rate each day last week?"
• "Which OS versions run our newest app release?"
• "Which API endpoints fail most in our mobile app?"
• "Which crashes happened most in the last 30 days?"

What it does

• list_entities: List the entities your key can query (crashes, sessions, bugs, networks, launches, screen loading, screen rendering, flows) with their columns, operators, metrics and plan limits. Use it to find valid metric and column names.
• get_rate_limit: Show how many Luciq Query API requests remain in the current per-minute and per-hour windows. Reads the counters without using them.
• query_crash_free_sessions: Crash-free session rate (or session count) per time bucket for one app and environment. Returns columns and rows, where the first column is the bucket start in epoch milliseconds. Each call counts against the plan's monthly query quota.
• query_sessions_by_os_version: Session counts for the top N app versions (as ranked by Luciq), split by operating system version, for one app and environment. Each call counts against the plan's monthly query quota.
• query_top_failing_endpoints: Network endpoints with the highest request counts or failure rates per time bucket, with failure rate and request count, for one app and environment. Each call counts against the plan's monthly query quota.
• query_top_crash_groups: Crash groups ranked by number of occurrences in a time window, one row per crash number, for one app and environment. Each call counts against the plan's monthly query quota.
• query_entity_metric: Run one aggregated metric of any entity per time bucket (for example launches, screen_loading, bugs). Metric names per entity come from list_entities; count works for the entities shown in the docs. Each call counts against the plan's monthly query quota.

BYOK key

You bring your own Luciq Luciq Query API key (starts with lq_) (https://dashboard.luciq.ai/). 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.luciq.ai 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.luciq.ai/references/api-access (the API this connector calls, with a BYOK key)

Live from the Luciq API (api.luciq.ai) with a BYOK key; documentation: https://docs.luciq.ai/references/api-access. 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 Luciq. Luciq 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 Luciq account.

Built for: Worldwide. Languages: English.

Luciq (BYOK) — Privacy Policy

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

What Luciq (BYOK) is. Luciq (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Luciq data: Query your Luciq mobile app health data (crash-free sessions, crashes, network failures, launches) with your own Query API key. You bring your own Luciq Luciq Query API key (starts with lq_); the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one Luciq 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.luciq.ai, over https, and is removed from any text we return to you or your assistant. We do not follow redirects with your key. If Luciq 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 Luciq receives. The request we make on your behalf, including the key and the arguments, under Luciq's own terms and privacy policy (https://www.luciq.ai/terms). Luciq acts at your direction and is the only recipient of the data of your request besides our hosting provider.

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

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

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

Luciq (BYOK) — Terms of Service

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

1. The Service. Luciq (BYOK) provides: Query your Luciq mobile app health data (crash-free sessions, crashes, network failures, launches) with your own Query 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 Luciq credentials and only access data you are allowed to access. Luciq's terms (https://www.luciq.ai/terms) apply to your use of Luciq; 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 Luciq. Luciq 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 Luciq returns, lightly trimmed; it may be incomplete, delayed or changed by Luciq. Check important facts at the source.
5. Read-only. The Service does not create, change, send or delete anything in your Luciq 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 Luciq'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; Luciq 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 Luciq 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 Luciq 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-luciq

Luciq (BYOK) support

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

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