background gif

Integrate

Reference Kit

A working example path: assemble envelopes, hit a Gate, observe allow and named rejects. Re-badged from the demo packs for developers who need copy-pasteable integration.

BetaDemo

The Reference Kit is the developer-facing packaging of the same curriculum DEMO-HACK teaches: ordinary REST/JSON, different authority object. Use it to learn the protocol before you wire production Gate form factors.

What you get

  • Prover path: canonicalize → challenge → respond → envelope
  • Gate path: recompute binding → burn-before-validate → twin validate
  • Language-shaped examples for the client assembly step (six-language target)
  • Hooks into Verify / adversary flows for falsifiable reject stages

Start with the quickstart for a single endpoint, then keep the Kit as the oracle for “does my client still assemble a conforming envelope?”

Mechanism claims

Protected routes do not rely on a reusable API key, bearer token, or service certificate as the authority object.ValidatedThe gate accepts a per-call envelope; agents and MCP faces are not configured with a bypass secret.Holds under the reference architecture

A conformance suite can falsify envelope assembly, binding, burn ordering, and reject stages against a deployment.ValidatedVerify / adversary harness exercises allow path, replay reject, and named reject stages.