Integrate
SDKs
Client helpers assemble envelopes; Gate middleware enforces them inside your process. Start with the Node middleware path that ships in evaluation.
Gate middleware (Node)
Embed Gate in an Express (or compatible) application: declare endpoint_id, policy string, freshness window, and ledger endpoint. Incoming requests must present a conforming envelope before your route handler runs.
Client libraries
Client SDKs wrap challenge/respond against the circuit binary (or agent respond for M2M), reserve a nonce, and fill the published binding fields. Language coverage tracks the Reference Kit; Node is the evaluation reference implementation.
Configuration surface
- endpoint_id, policy_hash source, method allow-list
- TTL / use count and freshness window per route
- fail-open vs fail-closed with break-glass
- audit mode: hash_only vs full capture
Mechanism claims
Every envelope binds method, endpoint_id, request body hash, policy hash, tau, and nonce_uuid into one composite digest.Shippingrequest_hash = sha256(method || endpoint_id || request_body_hash || policy_hash || tau || nonce_uuid).Holds under the reference architecture
Model A (local validate-proof) and Model B (registry validate-proof) are security-equivalent at the envelope layer.ValidatedThe client assembles the same envelope either way; only verifier acquisition differs.