Integrate
Protect your first endpoint in 30 minutes
Stand up a Gate in front of one route, mint or obtain an evaluation circuit, and prove a single allow path plus a replay reject.
Prerequisites
- Docker (or a Node host) for the evaluation Gate / Reference Kit path
- An evaluation circuit binary (Foundry eval or DEMO-HACK pack)
- A single high-value POST/PUT route you are willing to put behind proof-required
Steps
- Pick the form factor. SDK middleware if you own the app process; reverse proxy if you do not want to change the app.
- Define endpoint policy. Assign
endpoint_id, method allow-list,policy_hashsource string, freshness window, and fail-closed vs break-glass. - Wire Control (or local Model A). Point the gate at a durable ledger for anything beyond a laptop demo.
- Prove once. Client: challenge → respond → assemble envelope with the published binding → POST. Confirm allow.
- Replay once. Re-POST the same envelope; confirm reject at the nonce stage.
sha256(method || endpoint_id || request_body_hash
|| policy_hash || tau || nonce_uuid)When the allow path and replay reject both pass, you have a protected endpoint. Expand coverage with the migration guide (inventory → shadow → proof-required) rather than flipping every route on day one.
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
The nonce is burned before twin validation, so a failed or replayed submission cannot be spent twice.ShippingGate order spends nonce_uuid prior to validate-proof; spent nonces reject at the nonce stage.Holds under the reference architecture