Skip to Content
IntegrationsOpenClaw x Beav3r

OpenClaw x Beav3r

OpenClaw x Beav3r routes OpenClaw approval events into Beav3r, then returns the terminal decision back into OpenClaw.

Authority split

The integration keeps one clear rule:

  • Beav3r is the approval authority
  • OpenClaw remains the policy gate and final enforcement point

Shortest setup path

The shortest path is:

  1. create a Beav3r project
  2. create a Beav3r API key
  3. start the OpenClaw plugin and bridge
  4. pair a signer
  5. run one OpenClaw approval through the bridge

Use the curl bootstrap:

curl -fsSL https://raw.githubusercontent.com/beav3r-ai/openclawXBeav3r/main/scripts/bootstrap-docker.sh | \
  BEAV3R_API_KEY=bvr_test_replace_me sh

Docker is required for this setup path.

Runtime flow

The runtime flow is:

  1. OpenClaw raises an approval
  2. the approval is routed through the bridge into Beav3r
  3. Beav3r creates the approval request
  4. a signer approves, rejects, or the request expires
  5. the bridge forwards the terminal callback back into OpenClaw

Decision mapping

Bridge decision mapping is:

  • pending -> unresolved
  • approved or executed -> approved
  • rejected or denied -> denied
  • expired -> expired
OverviewLangChain