Quickstart

1

Register and obtain credentials

Call POST /auto-register with your email. You receive: tenant_id, api_key, node_id, log_url, and a link to your dashboard. The trial is live immediately — no approval step.

curl -X POST https://api.obligationsign.com/auto-register \ -H "Content-Type: application/json" \ -d '{"email": "you@example.com"}'

✓ Done: You have an api_key and a governance identity.

2

Collect gate evidence for your first governed action

Prepare the five gate evidence fields for one decision your AI system makes. Start with the simplest: a model deployment, a configuration change, or an inference decision you want to put on record.

Minimum required: G1 CI bounds, G2 causal_attribution boolean, G3 protected_metrics object, G4 evidence_class, G5 operator_id + four evidence hashes.

See full gate evidence reference →

3

Submit governance evidence — your first canonical leaf

curl -X POST https://api.obligationsign.com/governance/evidence \ -H "Authorization: Bearer $API_KEY" \ -H "Content-Type: application/json" \ -d @your-evidence.json # Response: { "leaf_index": 0, "leaf_hash": "3b8f1c...", "artifact_hash": "c7d9e2...", "sth": { "tree_size": 1, "root_hash": "...", "log_signature": "..." } }

✓ Done: You have a canonical leaf in the transparency log. The governance decision is on the permanent record.

4

Verify the leaf — cryptographic inclusion proof

curl "https://log.obligationsign.com/agts/v1/log/proof?leaf_hash=3b8f1c..." # Returns inclusion proof — verify client-side with SHA-256 # Or in browser: https://obligationsign.com/verify?leaf=3b8f1c...

✓ Done: The leaf exists in the Merkle tree. Independent parties can verify without contacting you or ObligationSign.

5

Retrieve your compliance report

curl -H "Authorization: Bearer $API_KEY" \ "https://api.obligationsign.com/governance/report/c7d9e2..." # Returns AGTS_COMPLIANCE_REPORT_V1: 6 claims, 17 sub-articles # Export (JSON/Markdown) requires L2 tier

✓ Done: You have a machine-readable compliance report linked to the canonical leaf. Share the leaf_hash permalink with your auditor.

6

Register a webhook — real-time governance events

curl -X POST https://api.obligationsign.com/webhooks \ -H "Authorization: Bearer $API_KEY" \ -H "Content-Type: application/json" \ -d '{ "url": "https://your-system.example.com/governance-hook", "events": ["leaf_admitted", "gate_fail", "compliance_report_ready"] }'

See all 8 event types →

✓ Done: Your system receives real-time governance events. Gate failures trigger your alert workflow immediately.

7

Integrate into your deployment pipeline — continuous governance

Wire POST /governance/evidence into your CI/CD pipeline or model deployment workflow. Every model update, configuration change, or significant AI decision becomes a canonical leaf before the action executes.

# In your deployment script: LEAF=$(curl -s -X POST https://api.obligationsign.com/governance/evidence \ -H "Authorization: Bearer $API_KEY" \ -H "Content-Type: application/json" \ -d "$(governance_evidence_for_this_deployment)" \ | jq -r '.leaf_hash') # Gate: only deploy if leaf was admitted if [ -n "$LEAF" ]; then echo "Governance leaf $LEAF admitted — deploying" deploy_model else echo "Governance gate failed — deployment blocked" exit 1 fi

✓ Done: Your deployment pipeline is governed. No model change executes without a canonical leaf in the log.

Full API reference → Webhook reference → Start free →