Beam Protocol Docs

Appearance

Beam ProtocolSafe AI Work Between Companies

Beam helps one company's AI ask another company to do work without losing who asked, who answered, or where it got stuck. Start with one real handoff and a visible paper trail.

Guided Evaluation
Request Hosted Beta
Hosted Quickstart
🤝

One Real Workflow

Beam starts with one concrete job: one company asks another company to do work and both sides can still see the same trail.

🆔

Known Senders And Receivers

Beam keeps company and agent identity explicit, so both sides know who asked for the work and who answered it.

🔐

Visible Paper Trail

Requests and replies stay attached to one trace, so operators can see what happened instead of guessing.

📊

Operator Visibility

The dashboard exposes traces, alerts, dead letters, audit history, and recovery context for the same handoff.

🔁

Recovery Built In

Retries, restart recovery, and dead-letter handling are part of the product surface, not hidden glue code.

🧩

Proof First, Depth Second

Start with the guided evaluation and only go deeper into quickstart, SDKs, compatibility, and rollout details once the use case is real.

Start Here ​

If you only do one thing, open the public Guided Evaluation. That is now the canonical buyer path from landing page to proof and hosted pilot intake.

Use the docs when you need one of these supporting paths:

  1. The First Production Partner Workflow Contract if you want the exact 1.0.0 workflow Beam is anchoring on.
  2. The Production Partner Onboarding Pack for prerequisites, proof expectations, and operator follow-up templates.
  3. The Production Go-Live Checklist if the workflow is moving from pilot to production.
  4. The Hosted Quickstart if you want to run the same proof stack locally.
  5. The Beam Workspaces guide if you want the first identity and control-plane model for teams, agents, and partner-facing access.
  6. The Beam Workspaces guide also covers the new OpenClaw Fleet model when you want one central Beam control plane managing multiple OpenClaw hosts.
  7. The Register page once the use case is real and you want to wire your own agent.

Choose Your Path ​

  1. See the proof first. Open the Guided Evaluation, inspect the real screenshots and operator evidence, then decide whether Beam is worth more time.
  2. Check the exact workflow contract. Open the First Production Partner Workflow Contract to see the named sender, recipient, latency, failure handling, and proof contract for 1.0.0.
  3. Prepare the evaluation properly. Use the Production Partner Onboarding Pack to align prerequisites, proof expectations, and next-step language before the call starts.
  4. Request hosted beta. If you want a guided rollout around one real partner workflow, use the Hosted Beta page.
  5. Run the technical proof yourself. Use the Hosted Quickstart when you want to self-run the same baseline locally.

What Beam Is For ​

Beam is not trying to be every possible agent standard at once. The current release direction is narrower and more useful:

  1. A company agent needs to hand work to another company's agent.
  2. Both sides need identity, signatures, replay protection, and policy controls.
  3. Operators need traces, retries, and audit logs when the handoff goes wrong.

If that is your problem, Beam is aimed directly at it. If it is not, Beam should probably not be your first tool.

Continue ​