Build on the control plane.

11/11 exposes a public governance API. Health and proof endpoints are open; the execute endpoint issues a signed authorization decision and requires an API key. Every decision is Ed25519-signed over an enumerated field set and hashed with SHA-256 and SHA-512. The audit lineage is chained with SHA3-512 and BLAKE2b-512.

SDK · Open source · live on npm

One SDK for the control plane.

@11ai/execution-governance is the single developer surface for the 11/11 control plane. One package, one integration, two capabilities. The SDK requests and verifies. The control plane holds the keys and signs. Governance sits on the action, not the model, so one integration covers OpenAI, Anthropic, Grok, and your own custom agents alike.

INSTALL
$ npm install @11ai/execution-governance

v0.1.0, Apache-2.0. It is early and moving fast, so treat v0 as a preview.

VERIFY

Check any decision yourself

Verify governance decisions against the public JWKS and proof endpoint. The same public verification surface this site already exposes, now callable from your own code.

GOVERN

Put your agent behind the boundary

Wrap your own agent's actions in pre-execution authorization and fail-closed enforcement, with a signed proof of every decision. The fuller use of the same SDK.

How the govern path works

Every action your agent takes is authorized before it can run, and proven after.

01

Agent builds a request

02

SDK signs and sends it

03

Signed allow or deny

04

Verify against public JWKS

05

Proceed, or never run

Status

The SDK is open source and installable from npm today. You can install it, run the demo, and verify a real signed decision yourself right now. Full details on the SDK page.

Verify Before RuntimeEnforce During RuntimeProve After Runtime

Execution Governance™ · Governed Execution™ · EA-11™ · Execution Arithmetic™ · Execution Evidence State™ · Patent Pending

Endpoints

Base URL: control.11aiblockchain.com

Response format

Signed, hashed, typically in under 100ms.

Each decision returns the verdict, an Ed25519 authorization artifact, dual audit hashes, and the bound tenant. Both ALLOW and DENY are signed and persisted to the audit chain.

  • Submit identity, action, environment, and tenant
  • Receive a deterministic allow or deny verdict
  • Reproduce the result against the public proof endpoint
POST /v1/execute (authenticated: API key required)
# request
{
  "action": "http.post",
  "identity": "svc_42",
  "tenant_id": "tenant_1111"
}
# response, retrieved 6 Aug 2026 (API key required to reproduce)
{
  "tenant_id": "tenant_1111",
  "decision": "DENY",
  "verified": false,
  "reason": "missing resource",
  "timestamp": "2026-08-06T21:52:49.190Z",
  "hash_algorithm": "SHA-256 + SHA-512",
  "signature_algorithm": "Ed25519",
  "signed_fields": ["execution_id", "tenant_id", "decision", "verified", "trust_score", "required_trust_score", "reason", "timestamp"],
  "ed25519_signature": {
    "algorithm": "Ed25519",
    "status": "SIGNED",
    "kid": "ea11-ed25519-public-2026",
    "public_key_ref": "/.well-known/jwks.json"
  },
  "audit_persisted": true
}

Reference specifications

The protocol is published.