Be the first to get access to new connectors. Get early access →
ConnectorBay Early access

Codeant AI (BYOK) — connector documentation

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

What Codeant AI (BYOK) is for

Codeant AI (BYOK) lets an AI assistant read your own Codeant AI data through the Codeant AI API with a key you supply (CodeAnt API token (starts with cdt_)). Read-only: 5 tools (get_scan_history, list_scanned_containers, get_container_scan_vulnerabilities, list_teams, get_security_hotlist_summary). 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.codeant.ai. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Codeant AI. Codeant AI 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:

  • "When was my repository last scanned by CodeAnt?"
  • "Which container images does CodeAnt track and how vulnerable are they?"
  • "What vulnerabilities did CodeAnt find in this container image?"
  • "Which developer teams are defined in CodeAnt?"
  • "How many critical findings are on my CodeAnt security hotlist?"

What it does

  • get_scan_history: Show the last analysis result for every scanned commit of a repository (commit, branch, time, status).
  • list_scanned_containers: List tracked container images across AWS ECR, Azure ACR and GCP GAR with latest scan status, severity counts and scan id.
  • get_container_scan_vulnerabilities: List the vulnerabilities of one container scan: CVE id, package, installed and fixed version, severity and title.
  • list_teams: List developer teams with description, tags, parent team and assigned repositories (member lists are left out).
  • get_security_hotlist_summary: Show the organization's security hotlist rollup: finding totals by severity, confirmed-exploit and ticketed counts, filter facets and SLA days (individual findings are not returned).

BYOK key

You bring your own Codeant AI CodeAnt API token (starts with cdt_) (https://docs.codeant.ai/settings/api-tokens.md). 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.codeant.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.

Data sources

Live from the Codeant AI API (api.codeant.ai) with a BYOK key; documentation: https://docs.codeant.ai/llms.txt. 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 Codeant AI. Codeant AI 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 Codeant AI account.

Built for: Worldwide. Languages: English.