Developers

Build governed applicationson the Indwel Platform.

Use ordinary APIs and schemas to create durable Work, run governed cognition, and inspect the evidence, state, and receipts that follow. Start with Platform API. Use Business App Engine when the application itself needs versioned domain semantics.

API Reference Implementation guide

First request

Run work through the Platform API.

Address durable Work, submit a governed Run with an idempotency key, then read the same resource for status and receipts. A run may complete, pause for a person, or refuse. Retrying the same operation does not create a second act.

cURL · governed run

curl https://api.indwel.ai/v1/work/{work_id}/runs \
  -H "Authorization: Bearer $INDWEL_TOKEN" \
  -H "Idempotency-Key: review-vendor-2026-09" \
  -H "Content-Type: application/json" \
  -d '{
    "objective": "Review the vendor against the approved control set",
    "contract": "vendor-risk/default",
    "evidence_policy": "require-admitted"
  }'

IdentityThe idempotency key keeps retries attached to one intended operation.

AuthorityAPI scope permits the call; the governing contract determines what may proceed.

EvidenceRetrieved material supports the run only after it is admitted as evidence.

ResultThe Run and its receipts remain available after the HTTP response ends.

Read the implementation guide →Open API Reference →

Resource model

Durable by default.

Work is the stable resource behind an undertaking. Collections and Sources supply governed information, and Fieldwork can acquire what is missing. Cognitive Contracts and Cognitive Governors resolve the authority under which a Run may proceed.

Your integration keeps addressing the same Work even when models, retrieval strategies, or orchestration change. Runs preserve execution; Effects, observation, receipts, and Settlement preserve what happened afterward.

On the wire

Caller: OAuth principal, tenant, scopes, and delegated or service authority.
Work: The durable undertaking your application continues to address.
Run: One governed operation with stable identity, lifecycle, and receipts.
Evidence: Admitted support with provenance and applicability.

Enterprise integration

Fits the controls you already operate.

Platform API uses familiar engineering patterns—OAuth, idempotency, versioned resources, webhooks, Problem Details, and explicit lifecycle state. It is designed to sit beside enterprise systems of record rather than replace them.

Pattern	Platform behaviour	Engineering rule
OAuth & IAM	Caller identity and bounded API scope	Scope permits the request; governing authority still resolves for the act.
Idempotency	Stable operation identity	Retry the intended operation instead of creating another one.
Concurrency	Explicit resource revision	Reject stale state transitions rather than silently overwriting them.
Events	Notification of state change	Re-read the authoritative resource before consequential action.
Problem Details	Typed transport, application, and governed failure	Preserve why the Platform could not proceed.

Business App Engine

Build domain applications without a second governance stack.

Business App Engine adds versioned application definitions, installations, cases, and run plans on top of the Platform. Domain state can live with the application while governed execution, evidence, human participation, effects, receipts, and Settlement remain Platform concerns.

DefinitionSchemas, workflows, actions, policies, and declared capabilities.

VersionAn immutable published application contract.

InstallationWorkspace binding, configuration, and capability grants.

CaseDomain state associated with durable Work.

RunGoverned execution through Platform authority.

Explore Business App Engine →

Contracts and tooling

Use contracts you can put in a build.

OpenAPI, JSON Schema, AsyncAPI, generated types, and machine-readable registries are published alongside the operating semantics they implement. Pin the version you reviewed, generate clients, validate payloads, and use Cognitive Unit Testing to exercise the same contracts before production.

Start with one bounded workflow. Keep your existing IAM, systems of record, and security tooling; add only the Work, evidence rules, authority, human gates, and capabilities that workflow needs.