Skip to main content
Checkfu is in private alpha. There is currently no self-service public CLI installation channel. The CLI artifact is not published for general download, and these docs do not provide an installation command. The public Agent authoring workflow is useful as a format and authority reference, but its commands still require one of the authorized paths below. Without CLI access, use the HTTP API reference and typed OpenAPI schemas; do not substitute an unlisted package install.

​
When CLI examples apply

Commands beginning with checkfu assume that you already have CLI access through an explicitly authorized alpha arrangement. The examples describe the supported command surface; they do not authorize or initiate artifact delivery. MCP setup through checkfu connect is available only after that CLI access is established.

​
Use an available path

  • Contributors and local evaluators: work from a Checkfu source checkout and follow Run Checkfu from source. That workflow uses pnpm exec checkfu and does not depend on a customer installation channel.
  • API-first integrations: call the documented public contract directly from your backend. Start with the HTTP API reference; the OpenAPI document and ordinary HTTP examples do not require the CLI.
  • MCP clients: once CLI access is established, follow the MCP server setup to register the endpoint without writing a secret into the client configuration.
This access statement is the canonical availability boundary for CLI examples. It will change only when an external distribution channel is explicitly approved.