CAIN-42 · How it works

Live consensus cluster

The live 4-region cluster that signs every decision, watched in real time.

Last reviewed 2026-10-01

Live   Studio apps & labs · Studio app

Where it fits

Part of How it works: The 7 moats, the live consensus cluster and the research lab. Every CAIN-42 product runs behind the same rule: an AI agent's action is checked before it runs (identity, authority, policy, risk), decided as allow, hold for a human, or block, and recorded as signed evidence. Unknown or error never becomes allow.

Use it

• Open it https://cainstudio.online/live-cluster.html

Live now

Checked from your browser when this page opened, not from a cached list.

Fire a real decision

Send an action through the live CAIN-42 pipeline from this page, with no account, and watch every stage decide. This is the same pipeline every product here sits behind; it runs for a throwaway demo tenant and is rate limited.

For AI engineers

Every product sits behind one decision path: your agent proposes an action with the exact arguments, CAIN runs it through identity, authority, policy, risk, trust and quorum consensus, and answers ALLOW, REQUIRE_APPROVAL or DENY with an Ed25519-signed record. A timeout, outage or unknown verdict never becomes ALLOW. A brand-new agent has no trust history, so its first actions usually come back REQUIRE_APPROVAL.

Python (zero dependencies)

pip install https://cainstudio.online/cainstudio-0.3.0-py3-none-any.whl
export CAIN_API_KEY=...   # free key: https://cainstudio.online/signup

import cainstudio

@cainstudio.guard()
def transfer(amount_usd: float, to: str) -> str:
    ...  # runs only if CAIN allows this call, with these arguments

try:
    transfer(5000, "acme")
except cainstudio.ApprovalRequired as e:
    print("held for a human:", e.approval_id)
except cainstudio.ActionBlocked as e:
    print("refused:", e.decision.reasons)
except cainstudio.CainUnavailable:
    print("CAIN unreachable: not run")   # fail-closed

See a real decision with no account

cainstudio try          # live pipeline, stage by stage
cainstudio try --list   # the other attack scenarios

MCP clients (Claude Code, Cursor)

claude mcp add --transport http cain https://cainstudio.online/mcp

More: Python SDK · TypeScript SDK · framework integrations · AI quickstart · decision signing key

Tested guarantees in this area

Every rule in these niches has its own page with its recorded result.

• Consensus & distributed systems: 64 tested invariants — Many machines agreeing on one answer, even when some fail or lie.
• Prediction, world models & simulation: 417 tested invariants — Predicting consequences before acting, and never mistaking a guess for a fact.
• Trust & reputation: 484 tested invariants — How much each agent can be trusted, earned from evidence.

Related

• Architecture — How the pieces fit together, drawn out.
• CAIN-42 Frontier Lab — Where new agent-safety research is tested in the open.
• CAIN-42 now: current technical state — The current technical state of CAIN-42, read from live sources.
• Changelog — Everything that shipped, newest first.
• Moat 1: Trust State — Works out, from evidence alone, how much each agent can be trusted right now.
• Moat 2: Security-Context Continuity — Makes sure who-is-acting and what-they-may-do survive every hop between systems.
• Moat 3: Trust Graph — Maps how every agent, person, tool and resource is connected.
• Moat 4: Execution Provenance & Attestation — Proves what actually ran, under whose authority, and what it changed.
• Moat 5: Predictive Trust & Blast Radius — Predicts what an action could reach before it is allowed.
• Moat 6: Adversarial Trust Engine — Attacks CAIN's own guarantees nonstop to find weaknesses first.