> ## 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.

# Browse the connector registry

> Learn how to list and inspect pre-built registry connectors and get their configuration schemas.

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](/agentic/connectors)

## List registry connectors

```bash theme={null}
# 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

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

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

```bash theme={null}
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).

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

## Get a registry connector

```bash theme={null}
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:

<Warning>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.</Warning>

| 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:

```bash theme={null}
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"}
  }'
```

<Info>The `config` object is validated against the registry connector's `configSchema`. If your config doesn't match the schema, the request will be rejected.</Info>

## Available registry connectors

For a catalog of available registry connectors with detailed documentation, see the [Registry Connectors](/agentic/registry/overview) section.

## Next steps

* Learn how to [manage connectors](/agentic/guides/manage-connectors) on your agents
* Read about [connector auth](/agentic/guides/connector-auth) for outbound connectors
* Browse the [registry connector catalog](/agentic/registry/overview)