Documentation
Concepts, guides, and reference for integrating intent verification into agentic systems and runtime boundaries.
Developers
Build against intent verification.
Use the Open Intent Layer, verify actions before they execute, validate Authority Tokens independently, and make autonomous systems legible to engineering, security, and compliance at the same time.
Quick example
bash
curl -X POST https://api.intended.so/v1/execute \
-H "Authorization: Bearer mrt_test_abc123" \
-H "Content-Type: application/json" \
-d '{
"action": "deployment.trigger",
"target": "service-checkout",
"environment": "staging",
"adapter": "github-actions"
}'
# → VERIFIED | decision: ALLOW | authority_token: eyJhbG...
# → audit_chain_entry: appendedBuild stack
API Reference
REST API for verification, execution, escalation workflows, audit retrieval, and evidence-aware operations.
SDKs
SDKs for submitting intent, validating Authority Tokens, and handling decisions in code.
Quickstart
Go from install to first governed action quickly: submit intent, receive a decision, and validate the Authority Token.
Open Source
Open Intent Layer, verifier tooling, CLI flows, connector hooks, and standards components you can adopt without asking permission.
Runtime facts
< 50ms p99
Decision latency
306 intents / 14 domains
Open Intent Layer
RS256 (per-tenant keys)
Token algorithm
SHA-256 hash chain
Audit integrity