> ## Documentation Index > Fetch the complete documentation index at: https://docs.corti.ai/llms.txt > Use this file to discover all available pages before exploring further. # Get registry connector details and configuration schema ## OpenAPI ````yaml /agentic/auto-generated-openapi-v2.yml get /v2/agentic/registry/connectors/{connectorId} openapi: 3.1.0 info: title: Corti Agent API v2 version: 2.0.0 summary: Manage agents and converse with them over the A2A v1.0 protocol. description: > Version 2 of the Corti Agents REST API. ## What's new in v2 - **Unified `connectors`** — a single, flat, discriminated array replaces the v1 split between `experts`, `mcpServers`, and sub-agents. The envelope is extensible: new connector kinds (`a2a`, `openapi`, `custom`) slot in behind the `type` discriminator without breaking changes. - **Clean CRUD verbs** — `POST` creates, `GET` fetches/lists, `PATCH` performs a *true* partial update, `DELETE` removes. v1's PATCH was effectively a PUT. - **First-class metadata** — `visibility`, `model`, `lifecycle` (now a body field, not a query param), and free-form `labels`. ## A2A v1.0 only The conversational surface speaks **A2A protocol version `1.0` exclusively** (both the `JSONRPC` and `HTTP+JSON` bindings). The deprecated v0.3 binding from v1 is intentionally not carried forward. Per A2A §3.6, clients MUST send the `A2A-Version` header (`Major.Minor`, e.g. `1.0`) on every request to the `/a2a/*` surface, or supply it as the `A2A-Version` query parameter. This surface implements `1.0` only; an absent header is treated as `1.0`. Patch versions MUST NOT be sent. The server echoes the negotiated version in the `A2A-Version` response header. ## Partial updates (PATCH) `PATCH` uses **JSON Merge Patch** semantics (RFC 7386), served under the `application/merge-patch+json` media type: - **Omit a field** → left unchanged. - **`null`** → cleared / reset to its default. - **Arrays** (e.g. `connectors`) → *replaced wholesale*, never merged. To mutate a single connector without replacing the whole array, use the `/connectors` sub-resource endpoints. ## Streaming (Server-Sent Events) The streaming A2A surfaces — `message/stream`, `tasks/subscribe`, and the streaming JSON-RPC methods — respond with `text/event-stream`. The `text/event-stream` media type carries a sequence of Server-Sent Events; the attached schema describes a single event frame. Every event's `data` field is a string carrying a JSON document (`contentMediaType: application/json`); `contentSchema` declares the parsed payload (`StreamResponse` for the `HTTP+JSON` binding, `JSONRPCResponse` for the `JSONRPC` binding). The optional `id` field carries the SSE event id used for resumption via the `Last-Event-ID` request header. contact: name: Corti API Support url: https://corti.ai email: support@corti.ai license: name: Proprietary url: https://corti.ai/terms termsOfService: https://corti.ai/terms servers: - url: https://api.{env}.corti.app description: Corti regional API gateway variables: env: default: eu enum: - eu - us description: Deployment region. security: - bearerAuth: [] tenantHeader: [] tags: - name: Agents description: Create, read, update, and delete agents. - name: Agent Card description: A2A-compliant agent discovery cards. - name: A2A description: Converse with an agent over the A2A v1.0 protocol. - name: Connectors description: Manage the connectors attached to an agent. - name: Usage description: Bucketed invocation history for an agent. - name: Contexts description: Conversational contexts and their tasks. - name: Registry description: Discoverable, pre-built connectors offered by the platform. - name: Artifacts description: Retrieve artifacts produced by tasks. - name: Feedback description: Collect human or automated feedback on tasks and messages. paths: /v2/agentic/registry/connectors/{connectorId}: parameters: - name: connectorId in: path required: true schema: type: string description: Registry connector identifier (e.g. `@dedalus/coding-expert`). get: tags: - Registry summary: Get registry connector details and configuration schema operationId: RegistryGet responses: '200': description: The registry connector. content: application/json: schema: $ref: '#/components/schemas/RegistryConnectorResponse' '401': $ref: '#/components/responses/Unauthorized' '404': $ref: '#/components/responses/NotFound' components: schemas: RegistryConnectorResponse: type: object description: >- A discoverable, pre-built connector offered by the platform registry. Only `id`, `type`, `name`, `title`, `description`, and `configSchema` are populated by the server today. `version`, `provider`, `capabilities`, `tags`, and `documentationUrl` are declared for forward compatibility but are not yet returned. required: - id - type - name properties: id: type: string description: >- Stable, namespaced registry identifier; use as a `registry` connector's `name`. examples: - '@dedalus/coding-expert' type: $ref: '#/components/schemas/CommonConnectorType' description: The connector kind this entry provisions when attached to an agent. name: type: string description: Programmatic name (MCP convention). examples: - coding-expert title: type: string description: Human-readable display name (MCP convention). examples: - ICD-10 Coding Expert description: type: string description: Description for list and detail views. May contain CommonMark. version: type: string description: Latest published version (SemVer recommended). examples: - 1.4.2 icons: type: array description: Display icons (MCP convention). items: $ref: '#/components/schemas/RegistryIcon' provider: type: string description: Name of the publishing organisation. examples: - Dedalus websiteUrl: type: string format: uri description: Connector homepage (MCP convention). documentationUrl: type: string format: uri description: Documentation URL for the connector. capabilities: $ref: '#/components/schemas/RegistryConnectorCapabilities' tags: type: array description: Keywords for search and filtering. items: type: string configSchema: type: object description: >- JSON Schema (draft 2020-12) describing the connector's accepted `config`. additionalProperties: true examples: - id: '@dedalus/coding-expert' type: registry name: coding-expert title: ICD-10 Coding Expert description: Returns ICD-10 codes for a clinical encounter. version: 1.4.2 icons: - src: https://cdn.corti.ai/registry/dedalus/coding-expert.svg mimeType: image/svg+xml sizes: - any provider: Dedalus websiteUrl: https://dedalus.example.com/coding-expert documentationUrl: https://docs.dedalus.example.com/coding-expert capabilities: streaming: true inputModes: - text/plain outputModes: - text/plain - application/json tools: - lookup_icd10 - validate_code tags: - icd10 - billing - expert CommonConnectorType: type: string description: | The connector discriminator. v2 ships `registry`, `mcp`, `agent`, `a2a`, and `schema`; `openapi` and `custom` are reserved for future minor versions. enum: - registry - mcp - agent - a2a - schema RegistryIcon: type: object description: An icon resource, following the MCP `Icon` shape. required: - src properties: src: type: string format: uri description: Icon source URL. mimeType: type: string examples: - image/svg+xml - image/png description: MIME type of the icon resource. sizes: type: array description: '`WxH` size hints (e.g. `48x48`), or `any` for scalable icons.' items: type: string examples: - - 48x48 - - any RegistryConnectorCapabilities: type: object description: What the connector can do once attached. required: [] properties: streaming: type: boolean description: Emits incremental updates during a task. inputModes: type: array description: Accepted input media types. items: type: string outputModes: type: array description: Produced output media types. items: type: string tools: type: array description: Names of tools the connector exposes to the agent. items: type: string CommonErrorResponse: type: object description: > Corti management-plane error envelope, used by all non-A2A endpoints. - **Standard** — when the error chain contains at least one `PublicError`, `code` and `message` come from the outermost `PublicError` and `details` is merged across the whole chain (outer values take precedence). - **Fallback** — when the chain contains no `PublicError`, the response is a generic `500` carrying a `requestId` for support reference. - **Validation** — a single `PublicError` whose `details.validationErrors` lists the offending fields. Field names use camelCase on the wire (e.g. `requestId`, `howToFix`). The free-form `details` object may carry arbitrary caller-defined keys. Rate limiting (HTTP 429) is not yet implemented; the server does not emit a 429 response. required: - error properties: error: type: object required: - code - message properties: code: type: string description: Stable, machine-readable, SCREAMING_SNAKE_CASE error code. examples: - ASSIGNMENT_CONFLICT - VALIDATION_FAILED - INTERNAL_ERROR message: type: string description: Human-readable explanation. howToFix: type: string description: Optional guidance for the caller to resolve the error. details: type: object description: | Structured context, merged from every `PublicError` in the chain (outer values win). Omitted on the generic fallback response. additionalProperties: true properties: validationErrors: type: array description: Present when `code` is `VALIDATION_FAILED`. items: type: object required: - field - reason properties: field: type: string description: The field that failed validation. reason: type: string description: Why the field failed validation. requestId: type: string description: > Correlation ID from request middleware. Included only on the generic `500` fallback so consumers can quote it in support requests. description: The error object with code, message, and optional details. examples: - error: code: ASSIGNMENT_CONFLICT message: could not complete assignment details: assignment_id: asg_99 expert_id: exp_42 - error: code: VALIDATION_FAILED message: validation failed details: validationErrors: - field: email reason: invalid format - field: name reason: required - error: code: INTERNAL_ERROR message: internal server error requestId: req_abc123 responses: Unauthorized: description: Missing or invalid credentials. content: application/json: schema: $ref: '#/components/schemas/CommonErrorResponse' NotFound: description: The resource does not exist or is not visible to the caller. content: application/json: schema: $ref: '#/components/schemas/CommonErrorResponse' securitySchemes: bearerAuth: type: http scheme: bearer bearerFormat: JWT description: OAuth 2.0 / OIDC bearer token. tenantHeader: type: apiKey in: header name: Tenant-Name description: The tenant the request operates within. ````