Agent capabilities

Capability discovery

Use authenticated connector discovery and MCP tools/list instead of the retired public catalog.

Discovery is caller-specific in v0. Use two authenticated surfaces instead of the retired public /catalog:

QuestionSource of truth
Which connectors exist, and which accounts can this caller see?GET /connectors
Which tools can this caller invoke now?MCP tools/list on POST /mcp

List connectors and account state

curl https://api.corespeed.io/connectors \
  -H "Authorization: Bearer $CORESPEED_API_KEY"

The response returns connector metadata and the current caller's account state in one request:

{
  "connectors": [
    {
      "id": "notion",
      "category": "connector",
      "name": "Notion",
      "icon_url": "https://api.corespeed.io/icons/notion.svg",
      "auth": {
        "type": "oauth2",
        "scopes": ["...provider scope..."]
      },
      "mcp_url": "https://api.corespeed.io/mcp",
      "status": "connected",
      "accounts": [
        {
          "id": "acct_...",
          "alias": "product-wiki",
          "identity": "Acme workspace",
          "scope": "private",
          "status": "connected",
          "can_remove": true
        }
      ]
    }
  ]
}

Use the returned fields as written:

  • The icon field is icon_url.
  • OAuth details live under auth.type, auth.scopes, and the optional auth.access_summary.
  • accounts[] contains aliases, private/shared scope, health, and removal permission for this caller.
  • Every connector currently points to the unified /mcp execution surface.

List callable tools

curl https://api.corespeed.io/mcp \
  -H "Authorization: Bearer $CORESPEED_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}'

tools/list is the final authority for execution. It reflects connected accounts, hidden registrations, and built-in capability settings for the current member and organization.

An authenticated GET /engines inventory does not exist yet. Do not infer a built-in tool list from the retired /catalog; only advertise or call a built-in when it appears in tools/list.

Visibility and detail URLs

The connector index is the discovery authority. A connector hidden from the index may still have an implementation route while upstream approval is in progress; that route is not evidence that the connector is publicly available.