ExternalInstallation
One paired, Workspace-owned record of an external system tenant.
exti_…CollaborationSpace
One governed scope inside that installation.
cspace_…AgentPlacement
One Agent placed across selected CollaborationSpaces with a declared identity posture.
aplace_…POST /v1/sessions has no installation, space, or placement. Create these resources when you need an A2A endpoint, a scoped policy or budget, scoped Memory, or a governed resource subscription.
Checkfu does not operate messaging adapters. To connect a messaging app, see Connect your own messaging app.
These resources place work and scope governance. They do not own Agent execution, a transcript, or an approval ledger.
What uses them
ExternalInstallation
An ExternalInstallation links one external system tenant to a Checkfu Workspace. You identify it withprovider and external_tenant_id, and you can add a display_name.
Creating or reactivating it requires a short-lived signed pairing proof bound to the exact Workspace, tenant, operation, and installation identity. Issue the proof with POST /v1/external-installations/pairing-proofs, then pass it as pairing_proof to POST /v1/external-installations. Checkfu validates and consumes the proof once.
The pairing proof establishes the installation. It does not authenticate later requests from the external system. Anything you build on an installation authenticates its own callers.
Credentials for the external system stay with you. They do not appear on the ExternalInstallation, in Session events, in a Harness, or in a Computer.
The lifecycle is active, disabled, disconnected, or uninstalled. Checkfu treats the live installation as authority. Holding a token for the external system does not make a disabled installation active.
CollaborationSpace
A CollaborationSpace is the governed scope used by policy and admission. Create one withPOST /v1/collaboration-spaces.
collaboration_space_id you put on a request does not grant access, join Memory, pick a budget, or place a transcript. Checkfu trusts a space only when it comes from an admitted placement.
AgentPlacement
An AgentPlacement places one mutable Agent on one or more CollaborationSpaces. Create one withPOST /v1/agent-placements.
The placement coordinates these authorities. It does not copy the Agent or create another ACL.
Identity posture
autonomous means the placement acts as its own service Principal. Its Connections and PermissionAssignments belong to that service identity.
delegated means the placement acts as a person Principal. The acting identity must satisfy the current admission rules. The placement itself grants nothing.
The ExternalInstallation is context, not a Principal and not an author.
Session admission freezes execution truth
When a Session is admitted through an active placement, Checkfu derives admission from the ExternalInstallation, CollaborationSpace, AgentPlacement, and acting Principal. The Session freezes the selected immutable AgentVersion and the Environment admission snapshot. Later edits to the mutable Agent, Environment, or placement do not rewrite that Session.Next steps
A2A edge
Expose a placed Agent through an Agent Card and JSON-RPC endpoint.
Tenancy and governance
See how scopes, Principals, and permissions fit together.