GET /health
Check runtime availability before integration calls.
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
Use the API to verify bundles, run deterministic execution, and finalize proof-ready commit flows.
End users operate in dashboard UI. This page is for integrators connecting enterprise systems and automation.
Check runtime availability before integration calls.
Validate bundle admission and policy scope.
Run deterministic execution in selected mode.
Finalize controlled side effects when commit is required.
Deterministic ordered execution with explicit sequence control.
Deterministic branch orchestration for controlled parallel execution.
Auth: No
Body: No
Returns: Service health status
Purpose: Runtime liveness and baseline availability.
Use when: Before verify, execute, or commit flows.
Auth: Bearer token
Body: JSON required
Returns: Admission decision and reason
Purpose: Admission and verification checks before execution.
Use when: Whenever validating bundle and profile scope for tenant and app.
Auth: Bearer token
Body: JSON required
Returns: Execution state, counters, fingerprint
Purpose: Deterministic execution under selected mode.
Use when: After verify succeeds and runtime can proceed.
Auth: Bearer token
Body: JSON required
Returns: Commit state and finalization result
Purpose: Explicit side-effect boundary and proof-ready finalization.
Use when: When transactional commit flow is required.
bundle_b64Canonical base64 bundle payload.now_unix_secsRequest time reference for validation context.expected_tenant_idTenant boundary assertion.expected_app_idApplication boundary assertion.expected_program_hash_hexOptional program hash lock (64 hex).allow_test_bundlesExplicit test bundle allowance flag.{
"bundle_b64": "BASE64_BUNDLE",
"now_unix_secs": 1760000000,
"expected_tenant_id": "11111111-1111-1111-1111-111111111111",
"expected_app_id": "aaaaaaaa-bbbb-cccc-dddd-eeeeeeeeeeee",
"expected_program_hash_hex": "64_HEX_CHARS_OPTIONAL",
"allow_test_bundles": false
}bundle_b64Canonical base64 bundle payload.modeExecution mode. Must be exactly ordered or pool.client_commit_keyClient-side idempotency and commit tracking key.now_unix_secsRequest time reference for validation context.expected_tenant_idTenant boundary assertion.expected_app_idApplication boundary assertion.expected_program_hash_hexOptional program hash lock (64 hex).allow_test_bundlesExplicit test bundle allowance flag.{
"bundle_b64": "BASE64_BUNDLE",
"mode": "ordered",
"client_commit_key": "invoice-2026-0001",
"now_unix_secs": 1760000000,
"expected_tenant_id": "11111111-1111-1111-1111-111111111111",
"expected_app_id": "aaaaaaaa-bbbb-cccc-dddd-eeeeeeeeeeee",
"expected_program_hash_hex": "64_HEX_CHARS_OPTIONAL",
"allow_test_bundles": false
}commit_idCommit identifier returned from /commit/prepare.{
"commit_id": "64_HEX_CHARS"
}Step 01 - Setup variables
API_BASE="https://api.adingates.digital"
TOKEN="USER_PROFILE_API_TOKEN"
BUNDLE_B64="PASTE_BASE64_BUNDLE"Step 02 - Check health, verify bundle, execute
curl -s "$API_BASE/health"curl -s -X POST "$API_BASE/verify" \
-H "Authorization: Bearer $TOKEN" \
-H "Content-Type: application/json" \
-d "{
\"bundle_b64\":\"$BUNDLE_B64\",
\"expected_tenant_id\":\"11111111-1111-1111-1111-111111111111\",
\"expected_app_id\":\"aaaaaaaa-bbbb-cccc-dddd-eeeeeeeeeeee\",
\"allow_test_bundles\":false
}"curl -s -X POST "$API_BASE/execute/ordered" \
-H "Authorization: Bearer $TOKEN" \
-H "Content-Type: application/json" \
-d "{
\"bundle_b64\":\"$BUNDLE_B64\",
\"expected_tenant_id\":\"11111111-1111-1111-1111-111111111111\",
\"expected_app_id\":\"aaaaaaaa-bbbb-cccc-dddd-eeeeeeeeeeee\",
\"allow_test_bundles\":false
}"Minimum successful path: health -> verify -> execute/ordered.
Step 03 - Optional commit extension
curl -s -X POST "$API_BASE/commit/prepare" \
-H "Authorization: Bearer $TOKEN" \
-H "Content-Type: application/json" \
-d "{
\"bundle_b64\":\"$BUNDLE_B64\",
\"mode\":\"ordered\",
\"client_commit_key\":\"invoice-2026-0001\",
\"expected_tenant_id\":\"11111111-1111-1111-1111-111111111111\",
\"expected_app_id\":\"aaaaaaaa-bbbb-cccc-dddd-eeeeeeeeeeee\",
\"allow_test_bundles\":false
}"
curl -s -X POST "$API_BASE/commit/finalize" \
-H "Authorization: Bearer $TOKEN" \
-H "Content-Type: application/json" \
-d "{ \"commit_id\":\"PASTE_COMMIT_ID_FROM_PREPARE\" }"Use commit flow only when side-effect finalization is required.
{
"ok": false,
"reason": "ERROR_CODE",
"error": "detail"
}Branch integration logic on `reason`, not free-form `error` text.
unlocked, voided, halted
Use these flags to determine whether execution proceeded, was rejected, or halted.
memory_count, flow_count, branch_count, step_count
Use counters to inspect runtime workload size, branching, and processing depth.
gate_value, commit_eligible
Use gate and commit fields to decide whether commit flow can be safely started.
execution_fingerprint_hex
Use fingerprint identity for trace correlation, replay checks, and audit linkage.
Public API exposes verification, execution, and commit flows. Internal trust-store topology, deployment controls, and operations policy internals remain intentionally outside the public contract.