Skip to main content

Discover Omega capabilities

Use the Omega capability manifest before selecting a retrieval operation. The manifest reports what the current authenticated principal can invoke in the current environment and whether recent evidence verifies that capability.

Capability discovery is informational. It does not grant access, replace generated RBAC or ACL checks, or guarantee that a later request will succeed.

Read the capability manifest​

Send an authenticated request to:

GET /v1/graymatter/omega/capabilities

For example:

curl --fail-with-body --silent --show-error \
  --header "Authorization: Bearer $VALKYR_AUTH_TOKEN" \
  https://api-0.valkyrlabs.com/v1/graymatter/omega/capabilities \
  | jq '{checkedAt, expiresAt, capabilities, warnings}'

Keep tokens in an environment variable or the platform credential store. Do not put them in source files, URLs, logs, or examples.

Interpret the response​

The response is scoped to the authenticated tenant, principal, policy, schema version, and authority set. The most useful fields are:

FieldUse
checkedAt, expiresAt, ttlSecondsDetermine whether the manifest is still current.
capabilitiesInspect each operation's endpoint, state, evidence tier, and limits.
subsystemsIdentify a degraded or unavailable dependency.
limitsApply the returned retrieval and context bounds instead of hard-coding them.
warningsSurface qualification or recovery guidance to operators.

Each capability reports separate invocable and liveVerified values. An installed runtime component can be invocable without current live evidence.

Capability states​

StateMeaningRecommended behavior
LIVE_VERIFIEDRecent authenticated evidence verified the capability for this scope.The operation can be considered, subject to normal policy and authorization.
IMPLEMENTED_UNVERIFIEDThe runtime exposes the capability but current live evidence is unavailable.Use a controlled probe before critical work.
DEGRADEDA dependency or verification check failed in a controlled way.Follow safeNextAction; do not silently substitute a broader operation.
PLANNEDThe contract describes future behavior that is not invocable.Do not call it or describe it as available.
UNAVAILABLEA required runtime component is absent.Choose an explicitly supported alternative or stop.

Select an operation safely​

  1. Refresh the manifest after expiresAt or after a role, policy, or tenant change.
  2. Match the capability's operation and endpoint instead of inferring a route from its label.
  3. Require invocable: true before calling the operation.
  4. Treat liveVerified: false, warnings, and degraded states as qualifications—not success.
  5. Continue to obey the operation response's answer policy, receipts, and generated access checks.

Do not reuse one user's manifest as evidence for another user or tenant. The scope and authority hashes exist to make that boundary explicit.