Developers

Build against intent verification.

Two paths: clone IntendedOps and self-host the entire governed back office, or request platform access to build on the commercial Intended runtime with full SDK support. The governance contract is the same across both — you can start on one and upgrade to the other without code changes.

Open source Quickstart Request platform access

bash

curl -X POST https://api.intended.so/intent \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "tenantId": "tenant-acme",
    "actor": { "id": "github-actions", "type": "service" },
    "targetSystem": "acme/frontend",
    "proposedAction": "deploy.production",
    "riskContext": {
      "baseRiskScore": 45,
      "policyCompliant": true,
      "requiresPrivilegedAccess": false,
      "touchesProduction": true,
      "containsSensitiveData": false,
      "github": { "owner": "acme", "repo": "frontend", "ref": "main" }
    }
  }'

# Same path as services/api/openapi.yaml — POST /intent (no /v1 prefix on the public API host).
# Execution after authorization uses POST /execute with a valid authority token.

One call: verify intent, receive a decision, issue authority, append evidence.

Build stack

Open Source

IntendedOps (the governed back-office operating system) and the Open Intent Layer (the canonical taxonomy). Both Apache 2.0. Both self-hostable today.

Explore