The Platform APIfor governed Work
Build applications for decisions that must withstand scrutiny—from a financial exception to a supplier assessment or an operational release. Indwel provides the programmable boundary for durable Work, admitted evidence, governed Runs, and inspectable outcomes. The institution still determines who may decide or act; each operation documents its access and refusal conditions.
curl --request POST \
--url 'https://api.indwel.ai/v1/runs:execute' \
--header "Authorization: Bearer ${INDWEL_TOKEN}" \
--header "Idempotency-Key: ${KEY}" \
--header 'Content-Type: application/json' \
--data @run.jsontype OperationAccepted = {
operationId?: string;
resourceId?: string;
status?: string;
receiptId?: string;
}API at the boundary of Work
One API surface. The whole governed lifecycle.
A supplier renewal begins with evidence, an owner's decision, and often an update to a separate system. An employee-policy answer may need no external action at all. Both require an explicit boundary between what cognition concludes and what the institution accepts. Install a versioned application, keep each matter in a durable Case, and plan and inspect Runs under the applicable authority. The API exposes those responsibilities without declaring an approved decision or a completed external effect simply because a request was accepted. A successful HTTP response does not prove Settlement.
The effective constitution draws on the contracts that apply to the institution, the Work, admitted sources, and the question. Different offices can contribute independent obligations to the same undertaking. The installed application defines its workflow; the Platform resolves authority rather than taking it from the client’s request. For one concrete implementation, see how institutional contracts govern consequential acts while leaving inquiry open.
Find an operation
Search by task, resource, route, or operation ID. Review scopes, parameters, schemas, responses, and refusal conditions without leaving the reference.