Workspace · Runtimes

Runtimes

Agents connected to this workspace through the guard, across domains. Status reflects how recently each called KIFF.

Connect an agent

Start with one consequential action. Point an existing agent at KIFF, read the decision, then decide when to move from observe to enforce.

first touch
API endpoint https://api.kiff.dev
API key 2 active
Manage keys

Paste this into your coding assistant (Cursor, Claude Code, Codex, …) with your project open, it wires your agent's action through KIFF using the endpoint and a minted key.

Wire this agent's consequential action (the one that moves money or changes state) through KIFF before it runs. Immediately before the side effect executes, POST to https://api.kiff.dev/v1/proposals/decide with header `Authorization: Bearer $KIFF_API_KEY` and a JSON body of {id, entity_type, entity_id, action_name, actor_id, parameters}. Then branch on the response field `outcome`: run the action only when it is `allowed`; on `approval_required` queue it for a human and stop; on `blocked` or `invalid` do not run it and surface `message`. Keep the KIFF call in front of the side effect, never after, and read the KIFF_API_KEY from the environment. See https://kiff.dev/llms-full.txt for the decision contract and outcome semantics.

Connected runtimes

2 runtimes connected to this workspace.

StatusRuntimeModeAdapterLast seenCallsActions
idleinvoice-to-pay finance-operations · production · ap-payment-agentenforceopenai-agents 0.4.23420
idlecustomer-resolution support-automation · production · support-refund-agentshadowlanggraph 0.4.2284-