API Token
Bearer token used by your integration client.
Preparing deterministic execution surface.
Restoring policy context, topology constraints, and proof pipeline metadata.
Validate
Route
Seal
Restoring policy context, topology constraints, and proof pipeline metadata.
Validate
Route
Seal
Configure once in Profile, then run the same controlled execution model from dashboard or API integration.
1.Register with email and password, then confirm your email address.
2.Open the dashboard and configure your workspace security defaults.
3.Open Profile -> API & Security.
4.Generate an API token for gateway access.
5.Set validation policy: Tenant ID, App ID, optional Program Hash, and Allow test bundles.
6.Save profile policy and set default execution mode (ordered or pool).
7.Upload or pass your signed bundle (base64) into the API workflow.
Bearer token used by your integration client.
Scopes execution requests to your tenant boundary.
Scopes requests to your application boundary.
Locks requests to a known program fingerprint when needed.
Explicitly enables or blocks test bundles per profile policy.
Select ordered or pool execution behavior by default.
Call GET /health to confirm service availability.
Call POST /verify to validate admission and policy context.
Call POST /execute/ordered or /execute/pool to run the bundle.
For transactional confirmation, call /commit/prepare then /commit/finalize.
1.Open the dashboard.
2.Select a process and provide request input.
3.Run the process and monitor status in real time.
4.Receive a clear result: Approved, Rejected, or Requires More Input.
5.Download a report for audit and recordkeeping.