Hex (BYOK)

Hex (BYOK) — connector documentation

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

What Hex (BYOK) is for

Hex (BYOK) lets an AI assistant read your own Hex data through the Hex API with a key you supply (Hex API key). Read-only: 9 tools (get_current_user, search_packages, get_package, get_release, list_repository_packages, list_repositories, list_organizations, get_organization, list_organization_members). 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 hex.pm. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Hex. Hex 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 Hex account and organizations does my key belong to?"
• "What are the most downloaded Hex packages about authentication?"
• "What is the latest version of the plug package and are there security advisories?"
• "What dependencies does phoenix 1.7.14 require?"
• "Which private packages does my acme organization have on Hex?"
• "Which Hex repositories can my key see?"

What it does

• get_current_user: Show the Hex account the key belongs to: username, email, the organizations it is a member of with its role in each, and timestamps.
• search_packages: Search or list public Hex packages with description, license, download counts and latest version. Up to 100 per page.
• get_package: Get one Hex package: description, licenses, links, owners, download counts, release list with versions, retirements and security advisories.
• get_release: Get one version of a Hex package: checksum, build tools, dependency requirements, retirement status, download count, publisher and security advisories.
• list_repository_packages: List packages in one Hex repository, such as an organization's private packages when the key has access. Up to 100 per page.
• list_repositories: List public Hex repositories plus the private ones the key is a member of, with creation and update times.
• list_organizations: List the Hex organizations the key's account belongs to, with billing status.
• get_organization: Get one Hex organization: billing status, number of seats and timestamps.
• list_organization_members: List the members of a Hex organization with their username and role (admin, write or read).

BYOK key

You bring your own Hex Hex API key (https://hex.pm/dashboard/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 hex.pm 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://github.com/hexpm/specifications/blob/main/apiary.apib (the API this connector calls, with a BYOK key)

Live from the Hex API (hex.pm) with a BYOK key; documentation: https://github.com/hexpm/specifications/blob/main/apiary.apib. 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 Hex. Hex 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 Hex account.

Built for: Worldwide. Languages: English.

Hex (BYOK) — Privacy Policy

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

What Hex (BYOK) is. Hex (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Hex data: Look up Hex packages, releases, security advisories, your organizations and private repositories with your own API key. You bring your own Hex Hex API key; the assistant sends it to us with each request.

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

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

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

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

Hex (BYOK) — Terms of Service

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

1. The Service. Hex (BYOK) provides: Look up Hex packages, releases, security advisories, your organizations and private repositories 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 Hex credentials and only access data you are allowed to access. Hex's terms apply to your use of Hex; 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 Hex. Hex 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 Hex returns, lightly trimmed; it may be incomplete, delayed or changed by Hex. Check important facts at the source.
5. Read-only. The Service does not create, change, send or delete anything in your Hex 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 Hex'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; Hex 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 Hex 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 Hex 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-hexpm

Hex (BYOK) support

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

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