Secoda (BYOK)

Secoda (BYOK) — connector documentation

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

What Secoda (BYOK) is for

Secoda (BYOK) lets an AI assistant read your own Secoda data through the Secoda API with a key you supply (Secoda API key). Read-only: 11 tools (list_catalog_resources, get_resource, list_integrations, list_collections, list_tags, list_monitors, list_incidents, list_monitor_measurements, list_event_categories, list_failing_dbt_tests, list_manual_lineage). 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.secoda.co, eapi.secoda.co, aapi.secoda.co. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Secoda. Secoda 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 verified tables in Secoda are flagged as PII?"
• "Tell me about Secoda resource 5b4f0c1a-1111-4222-8333-444455556666"
• "Which integrations does Secoda have and when did they last sync?"
• "Which Secoda collections exist and how many resources do they hold?"
• "Which tags exist in Secoda?"
• "Which Secoda monitors are in an incident or error state?"

What it does

• list_catalog_resources: List catalog resources (tables, columns, dashboards, databases, schemas, documents and more) with type, description, PII and verified flags, row count and usage. Narrow with the filter, a URL-safe JSON object such as {"operator":"exact","field":"type","value":"table"}.
• get_resource: Get one catalog resource: type, description, PII and verified flags, row count, byte size, usage, parent and source integration.
• list_integrations: List connected integrations (warehouses, BI tools, dbt, event tools) with type, extraction schedule and last and next extraction time; credentials are not returned.
• list_collections: List collections (curated groups of resources) with title, description, resource count, owner counts and verified flag.
• list_tags: List the tags used to classify resources, with name, description and color.
• list_monitors: List data quality monitors with metric type, frequency, status, last run, last error and last measurement.
• list_incidents: List monitor incidents with status, summary, measured value and first and last seen times.
• list_monitor_measurements: List measurements of one monitor (or one incident) with value and lower and upper thresholds.
• list_event_categories: List event categories of the tracking plan (analytics event groups) with title, description and child count.
• list_failing_dbt_tests: List resources that have failing or warning dbt tests for one dbt integration, as resource ids.
• list_manual_lineage: List manually defined lineage links between resources, optionally filtered by source or target resource id.

BYOK key

You bring your own Secoda Secoda API key (https://docs.secoda.co/api/authentication). 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.secoda.co, eapi.secoda.co, aapi.secoda.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.

Notices

Read-only. Integration credentials, audit logs and user lists are not returned. Workspaces on a custom (on-premise) domain are not supported.

Data sources

• https://docs.secoda.co/api/reference/getting-started (the API this connector calls, with a BYOK key)

Live from the Secoda API (api.secoda.co, eapi.secoda.co, aapi.secoda.co) with a BYOK key; documentation: https://docs.secoda.co/api/reference/getting-started. 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 Secoda. Secoda 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 Secoda account.

Built for: Worldwide. Languages: English.

Secoda (BYOK) — Privacy Policy

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

What Secoda (BYOK) is. Secoda (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Secoda data: Read your Secoda data catalog resources, integrations, collections, tags, monitors, incidents and lineage with your own API key. You bring your own Secoda Secoda API key; the assistant sends it to us with each request.

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

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

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

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

Secoda (BYOK) — Terms of Service

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

1. The Service. Secoda (BYOK) provides: Read your Secoda data catalog resources, integrations, collections, tags, monitors, incidents and lineage 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 Secoda credentials and only access data you are allowed to access. Secoda's terms apply to your use of Secoda; 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 Secoda. Secoda 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 Secoda returns, lightly trimmed; it may be incomplete, delayed or changed by Secoda. Check important facts at the source.
5. Read-only. The Service does not create, change, send or delete anything in your Secoda 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 Secoda'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; Secoda 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 Secoda 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 Secoda 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-secoda

Secoda (BYOK) support

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

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