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

Axiom (BYOK)

Read your Axiom datasets, fields, monitors, annotations and query logs and events with APL with BYOK

Unify Dynamics LLC

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

Try asking

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

Which Axiom account is my token for?
Tools called
get_user
Which Axiom datasets do I have?
Tools called
list_datasets
Show my Axiom dataset my-logs
Tools called
get_dataset
Which fields does my Axiom dataset my-logs have?
Tools called
list_dataset_fields
Show the 20 latest error events in my Axiom dataset my-logs
Tools called
query_apl
Which Axiom monitors do I have and are any failing?
Tools called
list_monitors

About

Axiom (BYOK) lets an AI assistant read your own Axiom data through the Axiom API with a key you supply (API token (an API token, not a personal access token; query and read permissions are enough)). Read-only: 8 tools (get_user, list_datasets, get_dataset, list_dataset_fields, query_apl, list_monitors, get_monitor_history, list_annotations). 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.axiom.co. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Axiom. Axiom and its logos are trademarks of their owners and are used only to say which service the connector works with.

Sources: Live from the Axiom API (api.axiom.co) with a BYOK key; documentation: https://axiom.co/docs/restapi/introduction. 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
  • Get userShow the Axiom user or token identity behind the key: id, name, email and role.
  • List datasetsList the datasets (log, trace and metric collections) with kind, retention in days and update time.
  • Get datasetGet one dataset by name: kind, retention, description and who created it.
  • List dataset fieldsList the fields of a dataset with their type, unit and description (up to 200 shown).
  • Query aplRun a read-only APL query against Axiom, for example "['my-logs'] | where status >= 500 | limit 20".
  • List monitorsList monitors (threshold, match-event and anomaly alerts) with their APL query, interval, threshold, datasets, disabled flag and last error.
  • Get monitor historyList the alert history of one monitor in a time range: when it opened and closed.
  • List annotationsList annotations (deploy markers and notes) with title, type, time and the datasets they apply to, optionally for a time range.

Information

PublisherUnify Dynamics LLC
CategoryDeveloper tools
LanguagesEnglish
Built forWorldwide
CompatibilityAny MCP client · any agent · REST
Version0.1.0
MCP endpointhttps://byok-axiom.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-axiom.connectorbay.com/mcp
RESTPOST https://byok-axiom.connectorbay.com/v1/tools/<tool>
OpenAI function callinghttps://connectorbay.com/openai/byok-axiom.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 token (an API token, not a personal access token; query and read permissions are enough) in the X-Upstream-Key header (get one at axiom.co).
  • Ask a question; the agent picks the right tool and answers from the live data.

Axiom connector: questions and answers

What is the Axiom connector?

Axiom (BYOK) lets an AI assistant read your own Axiom data through the Axiom API with a key you supply (API token (an API token, not a personal… It is a hosted MCP server with 8 tools such as Get user, List datasets, Get dataset, List dataset fields, Query apl, List monitors, published by Unify Dynamics LLC. It is independent and not affiliated with Axiom.

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

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

Do I need a Axiom account or API key?

Yes: this is a bring-your-own-key connector. Create a API token (an API token, not a personal access token; query and read permissions are enough) at https://axiom.co/docs/reference/tokens 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 Axiom read-only?

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

Is the Axiom 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

Hevo Data (BYOK)

Read your Hevo Data pipelines, destinations, objects, transformation models and workflows with your own API key and secret

Live · MCP + REST11 tools

Hex (BYOK)

Read your Hex projects, run history, data connections, collections and groups with BYOK (app.hex.tech workspaces)

Live · MCP + REST8 tools

Hexnode UEM (BYOK)

Read your Hexnode UEM devices, users, groups, policies, apps and organizational units with your own API key

Live · MCP + REST9 tools

Hex (BYOK)

Look up Hex packages, releases, security advisories, your organizations and private repositories with your own API key

Live · MCP + REST9 tools

Hightouch (BYOK)

Read your Hightouch reverse ETL sources, models, destinations, syncs and sync runs with your own workspace API key

Live · MCP + REST11 tools

Hivelocity (BYOK)

Read your Hivelocity bare metal and VPS devices, IP assignments, VLANs, DNS zones, SSH key names and maintenance events with your own API key

Live · MCP + REST12 tools

Documentation

Back to top

Axiom (BYOK) — connector documentation

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

What Axiom (BYOK) is for

Axiom (BYOK) lets an AI assistant read your own Axiom data through the Axiom API with a key you supply (API token (an API token, not a personal access token; query and read permissions are enough)). Read-only: 8 tools (get_user, list_datasets, get_dataset, list_dataset_fields, query_apl, list_monitors, get_monitor_history, list_annotations). 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.axiom.co. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Axiom. Axiom 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 Axiom account is my token for?"
  • "Which Axiom datasets do I have?"
  • "Show my Axiom dataset my-logs"
  • "Which fields does my Axiom dataset my-logs have?"
  • "Show the 20 latest error events in my Axiom dataset my-logs"
  • "Which Axiom monitors do I have and are any failing?"

What it does

  • get_user: Show the Axiom user or token identity behind the key: id, name, email and role.
  • list_datasets: List the datasets (log, trace and metric collections) with kind, retention in days and update time.
  • get_dataset: Get one dataset by name: kind, retention, description and who created it.
  • list_dataset_fields: List the fields of a dataset with their type, unit and description (up to 200 shown).
  • query_apl: Run a read-only APL query against Axiom, for example "['my-logs'] | where status >= 500 | limit 20". Returns the matching events with time and fields, or aggregates as rows. Queries are limited to the time range given.
  • list_monitors: List monitors (threshold, match-event and anomaly alerts) with their APL query, interval, threshold, datasets, disabled flag and last error.
  • get_monitor_history: List the alert history of one monitor in a time range: when it opened and closed.
  • list_annotations: List annotations (deploy markers and notes) with title, type, time and the datasets they apply to, optionally for a time range.

BYOK key

You bring your own Axiom API token (an API token, not a personal access token; query and read permissions are enough) (https://axiom.co/docs/reference/tokens). 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.axiom.co 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

Live from the Axiom API (api.axiom.co) with a BYOK key; documentation: https://axiom.co/docs/restapi/introduction. 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 Axiom. Axiom 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 Axiom account.

Built for: Worldwide. Languages: English.

Privacy policy

Back to top

Axiom (BYOK) — Privacy Policy

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

What Axiom (BYOK) is. Axiom (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Axiom data: Read your Axiom datasets, fields, monitors, annotations and query logs and events with APL with BYOK. You bring your own Axiom API token (an API token, not a personal access token; query and read permissions are enough); the assistant sends it to us with each request.

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

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

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

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

Terms of service

Back to top

Axiom (BYOK) — Terms of Service

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

  1. The Service. Axiom (BYOK) provides: Read your Axiom datasets, fields, monitors, annotations and query logs and events with APL with BYOK. 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 Axiom credentials and only access data you are allowed to access. Axiom's terms apply to your use of Axiom; 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 Axiom. Axiom 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 Axiom returns, lightly trimmed; it may be incomplete, delayed or changed by Axiom. Check important facts at the source.
  5. Read-only. The Service does not create, change, send or delete anything in your Axiom 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 Axiom'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; Axiom 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 Axiom 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 Axiom 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-axiom

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

Get Axiom (BYOK)

Free · BYOK · Read-only

BYOK: bring your own keyThis connector uses your own Axiom API token (an API token, not a personal access token; query and read permissions are enough). Create one at https://axiom.co/docs/reference/tokens, 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 Axiom. Revoke it at the provider whenever you like. Unofficial connector: not affiliated with Axiom.