Skip to content

guides

Intended Documentation

Quickstart

Get up and running with the Intended authority runtime in minutes.

beginner1 min readimplemented

Overview#

This guide walks through a first POST /intent call and how to interpret authority outcomes.

Prerequisites#

  • Intended account and tenant ID
  • API key (mrt_live_*)
  • curl
bash
export Intended_API_KEY="mrt_live_your_key_here"
export Intended_TENANT_ID="tenant_acme_prod"

Submit First Intent#

bash
curl -X POST https://api.intended.so/intent \
  -H "Authorization: Bearer $Intended_API_KEY" \
  -H "x-tenant-id: $Intended_TENANT_ID" \
  -H "Content-Type: application/json" \
  -d '{
    "tenantId": "tenant_acme_prod",
    "actor": { "id": "svc-ci-bot", "type": "service" },
    "targetSystem": "acme/platform-api",
    "proposedAction": "dispatch release workflow",
    "riskContext": {
      "baseRiskScore": 42,
      "policyCompliant": true,
      "requiresPrivilegedAccess": false,
      "touchesProduction": false,
      "containsSensitiveData": false,
      "github": {
        "owner": "acme",
        "repo": "platform-api",
        "ref": "refs/heads/main",
        "workflowId": "release.yml"
      }
    }
  }'

Interpret Outcome#

  • 200 Approved: token issued in authorityDecisionToken
  • 202 Escalated: approval required, no token yet
  • 403 Denied: fail-closed deny, execution skipped

Next Steps#