Soda Cloud US (BYOK)

Soda Cloud US (BYOK) — connector documentation

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

What Soda Cloud US (BYOK) is for

Soda Cloud US (BYOK) lets an AI assistant read your own Soda Cloud US data through the Soda Cloud US API with a key you supply (API key ID). Read-only: 11 tools (test_login, list_datasets, get_dataset, list_checks, get_check_result_history, list_incidents, get_incident, list_datasources, list_scans, list_dataset_monitors, list_contracts). 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 cloud.us.soda.io. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Soda Cloud US. Soda Cloud US 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:

• "Is my Soda Cloud API key valid and which organization is it for?"
• "Which Soda datasets have failing checks?"
• "How healthy is the Soda dataset orders?"
• "Which Soda checks are failing right now?"
• "How did the Soda check chk-1 evolve over the last runs?"
• "Which Soda incidents are open?"

What it does

• test_login: Check that the key works and show the Soda Cloud organization name it belongs to.
• list_datasets: List datasets with data source, health, check and incident counts, passing percentage and last update. Owners and attributes are left out.
• get_dataset: Get one dataset: data source, health status, check and incident counts, contract flag, tags and last update.
• list_checks: List data quality checks with type, column, definition, latest evaluation status, source and dataset. Latest result diagnostics are left out.
• get_check_result_history: List the past results of one check: time, status, measured value and scan id. Diagnostics queries are left out.
• list_incidents: List data quality incidents with number, title, status, severity, dates and description.
• get_incident: Get one incident by id: number, title, status, severity, dates, description and resolution notes.
• list_datasources: List connected data sources with name, type, version and timestamps.
• list_scans: List recent scans with type, state, start and end time and the datasets they covered. Uses a cursor for paging.
• list_dataset_monitors: List the metric monitors of one dataset with metric type, column, evaluation status and enabled flag.
• list_contracts: List data contracts with dataset, creation and update times and the contract YAML text.

BYOK key

You bring your own Soda Cloud US API key ID (https://docs.soda.io/reference/soda-apis/generate-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 cloud.us.soda.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://docs.soda.io/reference/soda-apis/rest-api (the API this connector calls, with a BYOK key)

Live from the Soda Cloud US API (cloud.us.soda.io) with a BYOK key; documentation: https://docs.soda.io/reference/soda-apis/rest-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 Soda Cloud US. Soda Cloud US 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 Soda Cloud US account.

Built for: Worldwide. Languages: English.

Soda Cloud US (BYOK) — Privacy Policy

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

What Soda Cloud US (BYOK) is. Soda Cloud US (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Soda Cloud US data: Read your Soda Cloud datasets, data quality checks and results, incidents, scans, monitors, contracts and data sources (US region) with your own API key. You bring your own Soda Cloud US API key ID; the assistant sends it to us with each request.

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

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

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

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

Soda Cloud US (BYOK) — Terms of Service

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

1. The Service. Soda Cloud US (BYOK) provides: Read your Soda Cloud datasets, data quality checks and results, incidents, scans, monitors, contracts and data sources (US region) 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 Soda Cloud US credentials and only access data you are allowed to access. Soda Cloud US's terms apply to your use of Soda Cloud US; 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 Soda Cloud US. Soda Cloud US 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 Soda Cloud US returns, lightly trimmed; it may be incomplete, delayed or changed by Soda Cloud US. Check important facts at the source.
5. Read-only. The Service does not create, change, send or delete anything in your Soda Cloud US 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 Soda Cloud US'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; Soda Cloud US 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 Soda Cloud US 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 Soda Cloud US 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-soda-cloud-us

Soda Cloud US (BYOK) support

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

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