External API

Manage external REST API connectors registered by an organization: register a connector, import its OpenAPI spec to synthesize endpoints, configure and test endpoints, author MCP tool definitions from those endpoints, and dispatch AI features (description refinement) against a connector. The transparent proxy that actually forwards calls to the upstream API is documented separately under the "External API Proxy" tag.

📄️ List external API connectors

Lists connectors registered by the caller's current organization, with each connector's enabled endpoint count. Requires at least the `client` role in the caller's current organization.

📄️ Register a new external API connector

Creates a bare connector (no spec, no endpoints) scoped to the caller's current organization. Requires at least the `member` role.

📄️ Browse the cross-organization connector marketplace

Lists connectors flagged `isPublic` and `status: active` across every organization, for the marketplace catalog. Not scoped to the caller's organization. Requires at least the `client` role in the caller's current organization (any authenticated org member may browse); secret fields stay unserialized regardless.

📄️ Get an external API connector

Visible to the owning organization, or to anyone when the connector is public.

📄️ Update an external API connector

Updates connector metadata, auth configuration, or status. Requires at least the `admin` role in the owning organization. If the name changes, the slug is regenerated and every authored MCP tool name and tool reference for this connector's endpoints is renamed to match.

📄️ Delete an external API connector

Soft-deletes the connector, its endpoints, and the MCP tool definitions backed by those endpoints, in one transaction. Requires at least the `admin` role in the owning organization.

📄️ List a connector's endpoints

Requires at least the `client` role in the owning organization (or the connector is public — visibility follows the connector's `view` policy).

📄️ Get a single endpoint

Get a single endpoint

📄️ Update an endpoint's configuration

Enable/disable, publish, re-time out, price, or pin query params on this endpoint. Requires at least the `admin` role in the owning organization.

📄️ Import (or re-import) an OpenAPI spec into a connector

Requires at least the `admin` role in the owning organization.

📄️ Bulk-update endpoints on a connector

Enable/disable, publish, or price multiple endpoints at once. Every `endpointIds` entry must belong to `connectorId`. Requires at least the `admin` role in the owning organization.

📄️ Execute a live test call against an endpoint

Issues a real HTTP request to the upstream API using the connector's configured auth, applying any `pinnedParams`. Does not create call logs or bill data tokens. A successful JSON 2xx response is cached as the endpoint's `sampleResponse`. Requires at least the `client` role in the owning organization; unlike the transparent proxy, test calls are never available cross-organization even for public connectors.

📄️ List a connector's authored MCP tool definitions

Each row includes its backing endpoint. Requires at least the `client` role in the owning organization (or the connector is public).

📄️ Bulk-create default MCP tool definitions for a connector

Idempotent: creates a default, disabled tool definition for every enabled endpoint on the connector that does not already have one, skipping the rest. Requires at least the `admin` role in the owning organization.

📄️ Update an authored MCP tool definition

Updates display copy, schema, annotations, tags, or lifecycle flags. Requires at least the `admin` role in the owning organization.

📄️ Soft-delete an authored MCP tool definition

A missing row returns 404 rather than silently succeeding, so callers can distinguish 'deleted' from 'already gone'. Requires at least the `admin` role in the owning organization.

📄️ List MCP tool definitions for a single endpoint

List MCP tool definitions for a single endpoint

📄️ Create a default MCP tool definition for one endpoint

Pre-fills the tool from the endpoint's OpenAPI-derived schema; the tool is created disabled so it can be reviewed before being exposed. Requires at least the `admin` role in the owning organization.

📄️ List AI features applicable to a connector

Returns the catalog of registered AI features scoped to connectors (currently only `refine_mcp_descriptions`), with the cost/duration hints shown before a run starts. Requires at least the `client` role in the owning organization (or the connector is public).

📄️ List AI feature run history for a connector

Ordered by `createdAt` descending. `before` is a cursor on the run id for stable backwards pagination (not offset-based). Requires at least the `client` role in the owning organization (or the connector is public).

📄️ Get a single AI feature run

The lookup is double-scoped on the connector id in the URL, so a run belonging to a different connector cannot be fetched via id-guessing. Requires at least the `client` role in the owning organization (or the connector is public).

📄️ Trigger the 'Refine MCP descriptions' AI feature for a connector

Dispatches an iterative audit-and-rewrite loop (orchestrator + auditor + critic agents) that rewrites every enabled MCP tool description on this connector, verified by an independent critic before it ships. Requires at least the `client` role in the owning organization (or the connector is public) — note this checks the `view` ability, not `manage`. Returns 409 if a non-terminal run for this feature and connector is already in flight. Estimated cost $1-5, estimated duration 60-900s.