Be the first to get access to new connectors. Get early access →
ConnectorBay Early access
Discover
Helicone (BYOK) icon

Helicone (BYOK)

Read your Helicone LLM request logs, sessions, users, properties, prompts and webhooks with your own API key

Unify Dynamics LLC

Tools8read-only
Sign-inBYOKbring your own key
Key keptNeverused for one call only
PriceFreeoptional Pro limits
ProviderHeliconeunofficial, not affiliated
Works withMCP · RESTany agent

Try asking

Real questions, and the tools your agent calls to answer them.

What were my most recent LLM requests in Helicone and what did they cost?
Tools called
query_requests
How many LLM requests has Helicone logged in total?
Tools called
count_requests
Which users cost me the most in Helicone this week?
Tools called
query_users
Show my Helicone sessions from the last day
Tools called
query_sessions
Which custom properties do I track in Helicone?
Tools called
list_properties
Which prompts are saved in Helicone?
Tools called
list_prompts

About

Helicone (BYOK) lets an AI assistant read your own Helicone data through the Helicone API with a key you supply (API key). Read-only: 8 tools (query_requests, count_requests, query_users, query_sessions, list_properties, list_prompts, count_prompts, list_webhooks). 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.helicone.ai. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Helicone. Helicone and its logos are trademarks of their owners and are used only to say which service the connector works with.

Sources: Live from the Helicone API (api.helicone.ai) with a BYOK key; documentation: https://docs.helicone.ai/rest/request/post-v1requestquery. Endpoints checked against that documentation on 2026-10-16.

Privacy

The publisher, Unify Dynamics LLC, states that tool inputs are processed in memory and not retained.

Data not collectedNo account, no profile, no stored prompts or results.

What it can do

8 tools, grouped by job. Every one is read-only or compute-only.

OpenAPI
Read your data8 tools
  • Query requestsList logged LLM requests, newest first, with model, provider, status, token counts, cost in USD, latency, user and custom properties (prompt and…
  • Count requestsCount all logged LLM requests in the Helicone account.
  • Query usersList the end users that made requests in a time window with request count, prompt and completion tokens and cost.
  • Query sessionsList sessions (grouped traces) in a time window with name, request count, tokens, cost and average latency.
  • List propertiesList the custom property names attached to requests (for example Environment or Feature).
  • List promptsList saved prompts with name, tags and creation time, one page at a time.
  • Count promptsCount the saved prompts.
  • List webhooksList configured webhooks with destination, version and creation time (the signing key is not returned).

Information

PublisherUnify Dynamics LLC
CategoryDeveloper tools
LanguagesEnglish
Built forWorldwide
CompatibilityAny MCP client · any agent · REST
Version0.1.0
MCP endpointhttps://byok-helicone.connectorbay.com/mcp
REST APIopenapi.json
SupportGet help · Status
CountryWorldwide
FunctionOther
LayerDeep connectors

Connect it to your agent

Three ways in, the same 8 tools.

MCP (Claude, Cursor, Windsurf, VS Code, any MCP client)https://byok-helicone.connectorbay.com/mcp
RESTPOST https://byok-helicone.connectorbay.com/v1/tools/<tool>
OpenAI function callinghttps://connectorbay.com/openai/byok-helicone.json
OpenAI-compatible chathttps://connectorbay.com/v1/chat/completions · how it works
  • Add the MCP URL in your client's connector, MCP or integration settings (streamable HTTP, no OAuth).
  • Key: send your API key in the X-Upstream-Key header (get one at us.helicone.ai).
  • Ask a question; the agent picks the right tool and answers from the live data.

Helicone connector: questions and answers

What is the Helicone connector?

Helicone (BYOK) lets an AI assistant read your own Helicone data through the Helicone API with a key you supply (API key). It is a hosted MCP server with 8 tools such as Query requests, Count requests, Query users, Query sessions, List properties, List prompts, published by Unify Dynamics LLC. It is independent and not affiliated with Helicone.

How do I connect Helicone to Claude, ChatGPT or Cursor?

Add the MCP endpoint https://byok-helicone.connectorbay.com/mcp to your client's MCP, connector or integration settings (streamable HTTP, no OAuth). For REST, POST JSON to https://byok-helicone.connectorbay.com/v1/tools/<tool>; the OpenAPI description is at /openapi.json. For OpenAI function calling, load https://connectorbay.com/openai/byok-helicone.json.

Do I need a Helicone account or API key?

Yes: this is a bring-your-own-key connector. Create a API key at https://us.helicone.ai/settings/api-keys and send it in the X-Upstream-Key header. ConnectorBay uses it for that one call only and never stores, logs or caches it.

Is Helicone read-only?

Yes. Every tool reads or computes. Nothing is created, changed, sent, paid or deleted in your account.

Is the Helicone connector free?

Yes. It is free to use within the published rate limits; an optional Pro key raises them. There is no account to create.

More like this

More in Other

Webflow Analyze (BYOK)

Read your Webflow site analytics with your own token: traffic, top pages, top dimensions, events, scroll depth, time on page and goal conversions (aggregates only)

Live · MCP + REST9 tools

Webflow Site Assets (BYOK)

Read the asset library, asset folders, custom fonts, registered scripts, custom code blocks, components and Google tags of your Webflow sites with your own token

Live · MCP + REST8 tools

Hosted Weblate (BYOK)

Read your Hosted Weblate localization projects, components, translation progress, strings and recent changes with your own API token

Live · MCP + REST12 tools

WhatsApp Account Admin (BYOK)

Read WhatsApp Business account activity history, subscribed apps, QR code links, calling and storage settings and official business account status through the Cloud API with your own system user token

Live · MCP + REST6 tools

Wheel Size (BYOK)

Look up vehicle makes, models, generations and trims and the factory wheel, rim and tire fitment of a vehicle with your own Wheel Size API key

Live · MCP + REST7 tools

Wildberries Marketplace (BYOK)

Read your Wildberries FBS supplies, warehouses, offices and orders awaiting re-shipment with your own API token (buyer data is not returned)

Live · MCP + REST8 tools

Documentation

Back to top

Helicone (BYOK) — connector documentation

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

What Helicone (BYOK) is for

Helicone (BYOK) lets an AI assistant read your own Helicone data through the Helicone API with a key you supply (API key). Read-only: 8 tools (query_requests, count_requests, query_users, query_sessions, list_properties, list_prompts, count_prompts, list_webhooks). 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.helicone.ai. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Helicone. Helicone 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:

  • "What were my most recent LLM requests in Helicone and what did they cost?"
  • "How many LLM requests has Helicone logged in total?"
  • "Which users cost me the most in Helicone this week?"
  • "Show my Helicone sessions from the last day"
  • "Which custom properties do I track in Helicone?"
  • "Which prompts are saved in Helicone?"

What it does

  • query_requests: List logged LLM requests, newest first, with model, provider, status, token counts, cost in USD, latency, user and custom properties (prompt and response bodies are left out).
  • count_requests: Count all logged LLM requests in the Helicone account.
  • query_users: List the end users that made requests in a time window with request count, prompt and completion tokens and cost.
  • query_sessions: List sessions (grouped traces) in a time window with name, request count, tokens, cost and average latency.
  • list_properties: List the custom property names attached to requests (for example Environment or Feature).
  • list_prompts: List saved prompts with name, tags and creation time, one page at a time.
  • count_prompts: Count the saved prompts.
  • list_webhooks: List configured webhooks with destination, version and creation time (the signing key is not returned).

BYOK key

You bring your own Helicone API key (https://us.helicone.ai/settings/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.helicone.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.

Notices

Reads logs and analytics only (queries are sent as POST bodies but change nothing). Request and response bodies are not returned. EU-region accounts use a different Helicone host that this connector does not call.

Data sources

Live from the Helicone API (api.helicone.ai) with a BYOK key; documentation: https://docs.helicone.ai/rest/request/post-v1requestquery. 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 Helicone. Helicone 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 Helicone account.

Built for: Worldwide. Languages: English.

Privacy policy

Back to top

Helicone (BYOK) — Privacy Policy

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

What Helicone (BYOK) is. Helicone (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Helicone data: Read your Helicone LLM request logs, sessions, users, properties, prompts and webhooks with your own API key. You bring your own Helicone API key; the assistant sends it to us with each request.

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

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

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

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

Terms of service

Back to top

Helicone (BYOK) — Terms of Service

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

  1. The Service. Helicone (BYOK) provides: Read your Helicone LLM request logs, sessions, users, properties, prompts and webhooks 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 Helicone credentials and only access data you are allowed to access. Helicone's terms apply to your use of Helicone; 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 Helicone. Helicone 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 Helicone returns, lightly trimmed; it may be incomplete, delayed or changed by Helicone. Check important facts at the source.
  5. Read-only. The Service does not create, change, send or delete anything in your Helicone 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 Helicone'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; Helicone 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 Helicone 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 Helicone 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-helicone

Helicone (BYOK) support

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

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. Helicone (BYOK) never asks for them.

Get Helicone (BYOK)

Free · BYOK · Read-only

BYOK: bring your own keyThis connector uses your own Helicone API key. Create one at https://us.helicone.ai/settings/api-keys, with the fewest permissions it needs (read-only if the provider offers it). Your assistant sends it in the X-Upstream-Key header with every request. It is used for that one call only: never stored, logged or cached, and only ever sent to Helicone. Revoke it at the provider whenever you like. Unofficial connector: not affiliated with Helicone.