Get runtime capabilities

GET
/v1/capabilities

Authorization

BearerAuth
AuthorizationBearer <token>

Bearer credential resolved to an opaque authenticated Principal by the Server deployment.

In: header

Response Body

application/json

application/json

application/json

application/json

curl -X GET "https://example.com/v1/capabilities"
{  "prompts": {},  "artifact_dreaming": false,  "artifact_dreaming_operations": [],  "source_types": [    "string"  ],  "artifact_families": [    "string"  ],  "memory_extraction": true,  "extraction": {    "configuration": "configured",    "background": {      "location": "local",      "role": "leader",      "state": "running",      "automatic_processing_enabled": true    },    "observation": {      "status": "unverified",      "since": "2019-08-24T14:15:22Z",      "last_failure": {        "code": "string",        "stage": "inference",        "occurred_at": "2019-08-24T14:15:22Z"      },      "last_success_at": "2019-08-24T14:15:22Z"    }  },  "experience_generation": false,  "managed_skill_generation": false,  "external_skill_registry": false,  "handoff_generation": true,  "search_modes": [    "auto"  ],  "context_versions": [    "powercontext.prepared-context.v1"  ]}

Get stable Server deployment identity and protocol contracts GET

Returns deployment identity and compatibility metadata only. Runtime availability, enabled behavior, limits and inventory remain owned by health, capabilities and statistics endpoints.

List observable Scopes GET

Inspect available Scopes for an explicit navigation or organization request. Do not enumerate Scopes to bypass the current session binding or search another work context implicitly. Reuse the host-selected Scope for ordinary data-plane operations. Discover Scope descriptors with an explicit literal-substring field and exact relationship filters. Query matches the selected original field using the database's native substring operation. Regular expressions and wildcard syntax are not supported. Case, accent, and full-width/half-width matching follow the underlying database collation; results need not be identical across backends. Requests without query parameters preserve the existing complete-list behavior.