Browse the connector registry

This guide shows you how to browse the registry of pre-built connectors maintained by Corti and partners. You will learn how to search for connectors, inspect their details, and use them in your agents.

Prerequisites

An access token or client credentials
Understanding of connectors

List registry connectors

# Replace these with your values
ENVIRONMENT="<eu-or-us>"
TENANT="<your-tenant-name>"
TOKEN="<your-access-token>"

curl "https://api.${ENVIRONMENT}.corti.app/v2/agentic/registry/connectors" \
  -H "Authorization: Bearer ${TOKEN}" \
  -H "Tenant-Name: ${TENANT}"

Searching

The q free-text search parameter is in private preview — accepted by the API but silently ignored.

Use the q parameter for free-text search over connector names and descriptions:

QUERY="coding"

curl "https://api.${ENVIRONMENT}.corti.app/v2/agentic/registry/connectors?q=${QUERY}" \
  -H "Authorization: Bearer ${TOKEN}" \
  -H "Tenant-Name: ${TENANT}"

Pagination

The registry list endpoint supports pageSize and pageToken query parameters. The response includes nextPageToken (opaque cursor for the next page) and totalSize (not currently populated by the server — treat as absent).

curl "https://api.${ENVIRONMENT}.corti.app/v2/agentic/registry/connectors?pageSize=20" \
  -H "Authorization: Bearer ${TOKEN}" \
  -H "Tenant-Name: ${TENANT}"

Get a registry connector

CONNECTOR_ID="coding-expert"

curl "https://api.${ENVIRONMENT}.corti.app/v2/agentic/registry/connectors/${CONNECTOR_ID}" \
  -H "Authorization: Bearer ${TOKEN}" \
  -H "Tenant-Name: ${TENANT}"

The response includes:

The version, provider, capabilities, tags, and documentationUrl fields are in private preview — declared in the schema but not yet populated. Only id, type, name, title, description, and configSchema are returned.

Field	Description
`id`	Stable, namespaced identifier (use as the `name` when attaching)
`type`	Connector kind this entry provisions
`name`	Programmatic name
`title`	Human-readable display name
`description`	Description (may contain CommonMark)
`version`	Latest published version
`provider`	Publishing organization
`capabilities`	Connector capabilities
`tags`	Keywords for search and filtering
`configSchema`	JSON Schema describing accepted `config`
`documentationUrl`	Documentation URL
`icons`	Icon URLs for the connector (e.g. logo)
`websiteUrl`	Website URL for the connector provider

Using a registry connector

When you find a registry connector you want to use, attach it to an agent by referencing its id as the name field:

AGENT_ID="<your-agent-id>"

curl -X POST "https://api.${ENVIRONMENT}.corti.app/v2/agentic/agents/${AGENT_ID}/connectors" \
  -H "Authorization: Bearer ${TOKEN}" \
  -H "Tenant-Name: ${TENANT}" \
  -H "Content-Type: application/json" \
  -d '{
    "type": "registry",
    "name": "coding-expert",
    "config": {"codingSystem": "icd-10"}
  }'

The config object is validated against the registry connector’s configSchema. If your config doesn’t match the schema, the request will be rejected.

Available registry connectors

For a catalog of available registry connectors with detailed documentation, see the Registry Connectors section.

Next steps

Learn how to manage connectors on your agents
Read about connector auth for outbound connectors
Browse the registry connector catalog

Quickstart

Concepts

Guides

Reference

Registry Connectors

Agent SDK

v1 Documentation (archived)

Prerequisites

List registry connectors

Searching

Get a registry connector

Using a registry connector

Available registry connectors

Next steps

​Prerequisites

​List registry connectors

​Searching

​Pagination

​Get a registry connector

​Using a registry connector

​Available registry connectors

​Next steps

Prerequisites

List registry connectors

Searching

Pagination

Get a registry connector

Using a registry connector

Available registry connectors

Next steps