> ## Documentation Index
> Fetch the complete documentation index at: https://docs.checkfu.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Capability status

> See what is mature, where it runs, and whether your Workspace can use it now.

Checkfu's overall access program is in private alpha. Each capability also has
its own maturity, intended topology, and live readiness.

<Warning>
  Plain HTTP against the Checkfu API needs no private package.
  Live readiness is deployment- and Workspace-specific and is not asserted by this page.
</Warning>

## The short version

* **Stability** says how mature the capability contract is.
* **Availability** says where it is intended to run.
* **Live readiness** says whether this deployment and Workspace can use it now.

The table below is the source posture generated from Checkfu's typed registry.
For a current answer, call authenticated `GET /v1/support/capabilities`. A
visible endpoint or configured resource is not enough.

## Read the labels

| Stability | Meaning |
| - | - |
| `supported` | Supported for general use under the compatibility policy. |
| `alpha` | Usable in the current alpha, with alpha change and support expectations. |
| `preview` | Visible for evaluation, but rollout or qualification may still block use. |
| `internal` | Used by Checkfu's runner, gateway, or operator planes rather than customers. |

| Availability | Meaning |
| - | - |
| `hosted` | Intended for the Checkfu-hosted control plane. |
| `customer_runner` | Requires a customer-operated Runner. |
| `local` | Available through an explicitly local path. |
| `rollout_fenced` | An operator-controlled rollout or qualification is still closed. |
| `unavailable` | No admitted execution path exists for this posture. |

`audience` is independent: `customer`, `runner`, `gateway`, or `operator`.
Region, retention, and prerequisites narrow the posture further.

In the live response, `available: true` requires an admitted source posture,
qualifying release evidence when the capability defines a runtime journey, and
no missing evaluated prerequisite for the selected deployment and Workspace.
The endpoint fails closed when readiness cannot be established.

## Source capability map

| Capability | Stability | Availability | Readiness |
| - | - | - | - |
| Capability support status | `alpha` | `hosted` | Check live Workspace status |
| Identity and source directories | `alpha` | `hosted` | Check live Workspace status |
| Tenant, Environment, and API-key control | `alpha` | `hosted` | Check live Workspace status |
| Agents and immutable releases | `alpha` | `hosted` | Check live Workspace status |
| Harness catalog and profiles | `alpha` | `hosted` | Check live Workspace status |
| Environments | `alpha` | `hosted` | Check live Workspace status |
| Computers | `alpha` | `hosted` | No runtime qualification required |
| Governance and audit | `alpha` | `hosted` | Check live Workspace status |
| Files | `alpha` | `hosted` | Check live Workspace status |
| Memory documents | `alpha` | `hosted` | Check live Workspace status |
| Versioned Memory | `preview` | `rollout_fenced` | Operator qualification required |
| Model routing | `alpha` | `hosted` | The Workspace must configure provider credential custody. |
| API MCP server | `alpha` | `hosted` | Check live Workspace status |
| A2A server | `preview` | `hosted` | Check live Workspace status |
| Skills and proposals | `alpha` | `hosted` | Check live Workspace status |
| Connections | `alpha` | `hosted` | Check live Workspace status |
| Connected runtimes | `alpha` | `hosted` | An operator-owned connected runtime must be enrolled and online. |
| FileTrees and mounts | `alpha` | `hosted` | Check live Workspace status |
| Installations and collaboration | `alpha` | `hosted` | Check live Workspace status |
| Automations | `alpha` | `hosted` | Check live Workspace status |
| ActionApprovals and StandingApprovals | `alpha` | `hosted` | Check live Workspace status |
| Usage | `alpha` | `hosted` | Check live Workspace status |
| Commercial billing | `preview` | `rollout_fenced` | Operator qualification required |
| Outcomes and Reports | `alpha` | `hosted` | The deployment must configure the production Outcome grader. |
| Sessions and Runs | `alpha` | `hosted` | Real managed execution requires a qualified runtime tuple. Steering and interruption need a qualified runtime tuple that proved both. |
| Managed runtime availability | `preview` | `rollout_fenced` | Operator qualification required |
| Outbound webhooks | `alpha` | `hosted` | Check live Workspace status |
| Tools and capability catalog | `alpha` | `hosted` | Check live Workspace status |
| Managed Tool release discovery | `preview` | `hosted` | No runtime qualification required |
| Zero-data-retention managed execution | `preview` | `rollout_fenced` | Operator qualification required |

“Check live Workspace status” means the static docs cannot answer readiness.
Authenticate to the deployment you will use:

```bash theme={"theme":{"light":"github-light","dark":"github-dark"}}
curl "https://api.checkfu.com/v1/support/capabilities" \
  --header "Authorization: Bearer $CHECKFU_API_KEY" \
  --header "Checkfu-Version: 2026-08-31"
```

Look at `available` and `missing_prerequisites` on the capability you need. A
`rollout_fenced` capability cannot be enabled by copying a flag; its named
operator qualification must complete.

## Common runtime failures

| Error | Meaning |
| - | - |
| `runtime.runner_unavailable` | No compatible Runner can take custody. |
| `runtime.harness_unavailable` | The admitted harness release is not installed on an eligible Runner. |
| `model.platform_supply_unavailable` | Platform-funded model supply is disabled or unhealthy. It never silently falls back to BYOK. |
| `memory.backend_unavailable` | The required versioned Memory backend is not enabled. |
| `billing.entitlement_unavailable` | Commercial entitlement could not be established. |

Use the [error reference](/reference/errors) for request-specific recovery and
[access and identities](/reference/access) for the credentials needed to call
the live endpoint.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.