Skip to main content
Start with the quickstart to learn the Agent, Environment, and Session requests. Its Session steps require a supported Harness and execution path in your Workspace; the hosted API has no simulator fallback. Choose another path when your goal is different.

Add Checkfu to an app

Create Sessions from your backend. Plain HTTP needs no private package; SDK examples need an invited alpha artifact.

Connect a local agent

Attach a supported operator-owned ACP process on a laptop, workstation, or VM while Checkfu keeps the Session history.
For deployment, choose Checkfu-managed or customer-operated Cloudflare. See Deployment for who operates the installation. ConnectedRuntime attachment is a separate execution choice.

​
Authoring and custom harnesses

The Agent project guide currently describes a source-checkout workflow for contributors or explicitly authorized evaluators. It is not a public installation path or a prerequisite for the HTTP quickstart. The custom-harness guide explains how to bring your own implementation. BYOH means bring your own harness; it does not choose deployment ownership or compute. Its reference source and CLI prerequisites are separate from access to the hosted API. Use only an artifact or source checkout you have explicitly received access to; do not assume access to the platform repository. The CLI and TypeScript SDK have no self-service public package channel during private alpha. See CLI access and TypeScript SDK access for the documented artifact requirements. Capability status explains how to check the exact deployment and Workspace. Creating a resource or seeing an endpoint does not establish that its execution path is available.