Skip to Content
Docs are being rebuilt — start at Introduction → How it works.

Capabilities API

The Capabilities API tells you which models, tools, and knowledge bases exist in your workspace, so you can pass valid IDs when creating or updating an agent through the Agents API. Results are workspace-specific: only models and toolkits you’ve connected appear.

All endpoints are under https://tmmate.ai/api/v1, require an admin key, and return the { "data": ... } envelope.

Why it matters for agents

When you create an agent you must supply a model, and optionally tools and knowledge bases. The (provider, model) pair, each tool, and each KB must already be connected in your workspace — otherwise the create/update fails with 400. The capabilities endpoints are how you discover those valid IDs.

Endpoints

EndpointReturnsUse the result for
GET /capabilitiesEverything in one call.A single discovery request.
GET /capabilities/modelsConnected models.model.model (from id) and model.provider.
GET /capabilities/toolsSystem and connected-app tools.capabilities.tools[] entries.
GET /capabilities/knowledge-basesLightweight KB list.capabilities.knowledgeBases[] IDs.
GET /capabilities/embeddingThe embedding model for KB search/RAG.Reference only (fixed per deployment).

Mapping results onto an agent

Models — use id as model.model and provider as model.provider:

{ "id": "anthropic/claude-sonnet-4.6", "name": "Claude Sonnet 4.6", "provider": "ANTHROPIC", "hasReasoning": true }

Tools — each entry is a discriminated union on kind:

  • system{ "kind": "system", "id": "web_search" }
  • composio{ "kind": "composio", "appId": "gmail", "actions": ["GMAIL_SEND_EMAIL"] }

Knowledge bases — use id in capabilities.knowledgeBases, with an access of "read" or "read-write":

{ "id": "b2f1…UUID", "access": "read" }

Example

curl https://tmmate.ai/api/v1/capabilities \ -H "Authorization: Bearer $TEAMMATE_API_KEY"
{ "data": { "models": [ /* … */ ], "tools": [ /* … */ ], "knowledgeBases": [ /* … */ ], "embedding": { /* … */ } } }

Full reference

For every field, type, and the interactive explorer, see the canonical reference: