list_connectors

List the Connectors Marketplace — every connector Subscriby knows, lane by lane, with its badges, manifest and the form that connects it.

Purpose

Answer "which connectors exist, which can a creator install today, and what does each do?". Every card carries its lane (status: available, beta, paused, in_development, coming_soon), whether it is installable, whether it is official, its badges (official or community, new, trending), the category, tagline, overview and links, and, for a connector that exists as a package, the whole manifest: install_mode, scopes, the resource_kinds it gates with their grant mode, capabilities, messaging limits, pacing, the management_commands its in-chat surface renders and the missing_commands it does not, relay_modes, the recovery facets, and the declarative install_fields and settings_fields a client renders as the connect form. The payload is exactly what GET /v1/connectors returns; the same document is the subscriby://connectors/catalog resource.

Required ability

project-connector:view-any

Input schema

{
  "type": "object",
  "properties": {
    "status": {
      "type": "string",
      "enum": ["available", "beta", "paused", "in_development", "coming_soon"],
      "description": "Narrow to one lane. Omit for every lane."
    }
  }
}

Output shape

{
  "data": [
    {
      "key": "telegram",
      "name": "Telegram",
      "vendor": "Subscriby",
      "version": "1.0.0",
      "status": "available",
      "status_label": "Available Now",
      "installable": true,
      "official": true,
      "badges": [{ "key": "official", "label": "Official" }],
      "category": "messaging",
      "tagline": "Sell access to Telegram channels, groups and supergroups through your own bot.",
      "install_mode": "paste_credential",
      "scopes": ["project", "platform"],
      "resource_kinds": [
        { "kind": "channel", "label": "Channel", "portal_label": "Channel", "icon": "megaphone", "grant_mode": "bearer_link", "supports_early_admission_hold": true, "upgrades_from": null, "plan_kinds": ["one_time", "recurring", "pass", "pass_series"] }
      ],
      "capabilities": ["messaging", "access_control", "management_surface"],
      "install_fields": [
        { "name": "token", "type": "secret", "label": "Bot token", "required": true, "rules": ["string"], "steps": [], "links": {} }
      ]
    },
    {
      "key": "slack",
      "name": "Slack",
      "status": "coming_soon",
      "status_label": "Coming Soon",
      "installable": false,
      "badges": [],
      "eta": "Planned",
      "install_mode": null,
      "resource_kinds": [],
      "install_fields": []
    }
  ],
  "meta": { "total": 5 }
}

Cards come installable lanes first, then by name. See the Connectors API for every lane, badge and manifest key.

Example prompts

"Which connectors can I add to my project right now?"

"What does connecting Telegram ask me for?"

Failure modes

AUTHENTICATION_REQUIRED — no authenticated user on the request.
TOKEN_MISSING_ABILITY — token lacks project-connector:view-any.
VALIDATION_FAILED — status names no lane; context.accepted lists them.

get_connector — one card by key.
list_connector_installations — what a project actually runs.
Connectors API