Openterms
Open source cryptographic consent receipts + programmable guardrails + provider verification for AI agents.
Your agent proves what it agreed to. Your policy controls what it's allowed to do. The API provider can verify both.
License Tests
Live Demo · Quickstart · Self-Host · MCP Server · Contributing · Open Receipt Spec
What It Does Openterms sits between your AI agent and the actions it takes. Three layers:
Receipts — Before your agent calls an API, it gets an Ed25519-signed receipt. Canonical JSON (RFC 8785), SHA-256 hash, real cryptography. Anyone can verify it using public keys — no API key needed, no trust in the server required.
Policy Engine — Daily spending caps, action type whitelists, escalation thresholds. The policy engine evaluates before the receipt is signed. Denied actions never get a receipt.
Provider Verification — API providers register their terms URL and verify agent consent before serving requests. One public GET call. Both sides of the transaction trust the proof.
