Capability Matrix

Use GET /v1/capabilities for runtime discovery, but do not treat its projection as proof of a successful request. Source review on 2026-09-10 found optimistic account/feature checks; connected/enabled does not guarantee current upstream permission, token validity or quota. Handle runtime refusals and unknown states.

How to Read This Matrix

Supported — The platform supports this capability globally
Tenant-dependent — Availability depends on the workspace’s connected accounts
Public API — Available through the /v1/* data plane
Streaming — Supports SSE streaming
Artifact output — Produces downloadable artifacts

Matrix

Capability	Supported	Tenant-dependent	Public API	Streaming	Artifacts	Notes
Chat completions	Yes	Yes (needs ChatGPT)	Yes	Yes	No	Core feature
Conversation continuity	Yes	Yes	Yes	No	No	Preserve conversation ID
Projects	Yes	Yes	Yes	No	No	Project files need upstream auth
Image input (vision)	Yes	Yes	Yes	Yes	No	Inline base64 or attachment
File input	Yes	Yes	Yes	Yes	No	PDF, TXT, code, data files
Generated images	Yes	Yes	Yes	Yes	Yes	Use `assets` array, not base64
Generated files	Yes	Yes	Yes	Yes	Yes	CSV, code, etc.
Artifact download	Yes	No	Yes	No	No	Authenticated, tenant-scoped
Transcription	Yes	Yes	Yes	No	No	Arabic + English
Audio in conversations	Yes	Yes	Yes	No	No	Text → audio → text continuity
Speech generation (TTS)	Yes	Yes (needs Savio)	Yes	No	Yes	Async job lifecycle
Async audio jobs	Yes	Yes	Yes	No	No	Poll for completion
Capability discovery	Yes	No	Yes	No	No	Always available
Models discovery	Yes	No	Yes	No	No	Always available
Usage tracking	Yes	No	No public report endpoint	No	No	Recorded internally; User App/admin reporting
Action execution and runs	Yes	Yes	Yes	Events endpoint	Depends on Action	Beta/cohort and scopes required
Teach/compile/verify/publish journey	Internal workflows	Yes	Not through `/v1`	No	Evidence	Authorized operator workflow, not public API parity
Error model	Yes	No	Yes	Yes	No	Canonical envelope + streaming
Request IDs	Yes	No	Yes	Yes	No	`X-Request-Id` header

Checking Capabilities at Runtime

curl https://ghostmind.optdmsa.com/v1/capabilities \
  -H "Authorization: Bearer $GHOSTMIND_API_KEY"

Each capability has:

supported — boolean, platform-level support
enabled — boolean, effective for your workspace
reason — string, why it’s disabled if enabled: false

Common reason values:

no_connected_account — no provider account connected
upstream_not_authorized — account connected but lacks upstream permissions
account_disabled — account is disabled

Next Steps

Capabilities API — API reference
Provider Matrix — Provider support details
Start Here — Getting started guide