Connect your workload to Runtime.
Submit asynchronous jobs, track execution and retain result and evidence hashes through the Runtime API.
Async Runtime Job API
The commercial contract starts as an asynchronous Job API rather than pretending the current platform is already a massive real-time cloud. The Control Plane queues work; a Runtime Worker claims and executes it.
# Submit a runtime job
curl -X POST https://creaim-runtime-core.base44.app/functions/runtime-api-submit \
-H "Authorization: Bearer $CREAIM_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"problem_type": "portfolio",
"execution_mode": "cpu_exact",
"runtime_profile": "adaptive",
"evidence_level": "full",
"input_url": "https://example.com/portfolio.json"
}'
# Poll job status + evidence
curl https://creaim-runtime-core.base44.app/functions/runtime-api-get \
-H "Authorization: Bearer $CREAIM_API_KEY" \
-G --data-urlencode "job_id=job_01HZEXAMPLE"/functions/runtime-api-submitSubmit an asynchronous Runtime Job/functions/runtime-api-get?job_id={id}Read job status, result and Evidence hashes/functions/runtime-evidence-verifyVerify a completed Job evidence hash/functions/runtime-capabilitiesRead the current verified capability declaration/functions/runtime-worker-claimAuthenticated Compute Worker claim endpoint/functions/runtime-worker-completeAuthenticated Compute Worker result / Evidence return endpointThese are the current Base44 function endpoints. A cleaner /v1 gateway can later map to the same contract. Worker endpoints are internal and require a separate Runtime Worker secret; their existence is not a claim of 24/7 compute availability.
API Keys
Raw keys are shown once. Only prefix + SHA-256 hash are stored.
Control / Compute split
Base44 is the Control Plane. Runtime Core workers remain the Compute Plane.
Evidence-first response
Each completed job can carry result hash, evidence hash, executor identity and Runtime version.