Skip to main content
ENTERPRISE API v1

Integration surface for governed enterprise AI

A stable façade over the same opportunity, workflow, agent, evidence, value and model-release domains used by the product UI. Protected operations require Microsoft Entra enterprise authentication and never bypass the underlying governance controls.

OpenAPI 3.1 JSONBuyer overview
AUTH

Microsoft Entra + app roles

Client-credentials service principals are supported through the existing validated JWT boundary. Tenant, audience, issuer, RS256 signature and app roles are checked server-side. Demo identities receive no Enterprise API authority.

RATE CONTROL

Fail-closed distributed limits

Protected API v1 calls reuse the platform distributed limiter contract. Enterprise traffic fails closed if the configured Upstash or HTTP limiter is unavailable.

MUTATIONS

Retry keys + domain concurrency

Mutating calls require an Idempotency-Key for retry correlation. Exact domain safety remains grounded in optimistic concurrency, non-overwrite evidence keys and the existing transactional policies rather than an unproven cross-instance exactly-once claim.

GOVERNANCE

No privileged bypass

Human Approval, Finance validation, tenant isolation and model-release separation of duties remain authoritative below the API façade. API integration does not create a second governance path.

ENDPOINT CATALOG

Versioned contract

POST/api/v1/opportunities/analyzeopportunities:analyzeStructured enterprise AI opportunity analysis
GET/api/v1/workflowsworkflows:readVersioned tenant workflow snapshot
POST/api/v1/workflows/actionsworkflows:writeGoverned workflow mutations with domain RBAC
POST/api/v1/agents/runsagents:runServer-Sent Events specialist-agent workflow that stops at human review
GET / POST/api/v1/evidenceevidence:read / evidence:writeIntegrity-verified governed evidence read/write
GET/api/v1/value-ledgervalue:readGoverned Value Ledger
POST/api/v1/value-ledger/actionsvalue:writeValue mutations with Finance-domain policy preserved
GET / POST/api/v1/model-releasesmodel-releases:read / model-releases:writeProvider certification and independent Risk Reviewer release authority
QUICK START

Machine-to-machine request

Obtain a Microsoft Entra access token for the buyer-owned application registration/service principal with the appropriate application role, then call the versioned endpoint. The API never accepts a client-supplied role or scope header as authority.

curl -sS https://YOUR_DEPLOYMENT/api/v1/workflows \
  -H "Authorization: Bearer $ACCESS_TOKEN" \
  -H "X-Request-Id: buyer-evaluation-001"
BOUNDARY

Reference platform, not buyer-live configuration

The API contract is productized and transferable. Buyer-live operation still requires buyer-owned Entra configuration, durable persistence where selected, distributed rate limiting, evidence storage, observability and provider credentials. Cross-instance exactly-once idempotency can be added at the buyer gateway/persistence layer if the buyer requires that operating guarantee.