ObligationSign
From ≈ $0.09 per use
not read yet
Use
- For
- Organisations deploying autonomous AI systems that need auditable records of authorised decisions.
- Price
- From ≈ $0.09 per use€0.08 · pricing page, read Oct 24, 2026Trial & discounts: 30-day free trial
- Used for
- Gate AI agent tool calls through governance checks
- Record authorisation of AI decisions before execution
- Replay a governance decision gate by gate
- Has an MCP server (2 in the registry)public registry →
From ≈ $0.09 per use
€0.08
Trial & discounts 30-day free trial
These are ObligationSign's own statements, read from its pages. We did not audit them. A line that is missing was not found on the pages we read; it does not mean the practice is absent.
- MCP servercom.obligationsign.mcp/agts-mcpverified in the MCP registry
- Stateanswers, requires sign-inchecked 2026-10-24
- Address to connectmcp.obligationsign.com/mcp
- MCP docsobligationsign.com/mcpthe vendor's page ↗
This card as JSON, for your agent →
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.
Not it? Say what you need
betaThree tools from the Atlas for the job you describe, each with what fits and what does not.
No notes yet. What do you use ObligationSign for?
Sign in to leave a noteWhat is ObligationSign?
Gates autonomous AI decisions through entropy, coherence and energy checks, then signs each approved decision into an append-only Merkle log.
Who is ObligationSign for?
Organisations deploying autonomous AI systems that need auditable records of authorised decisions.
How much does ObligationSign cost?
Paid plans start at ≈ $0.09 per use (€0.08 per use), per ObligationSign's pricing page on 2026-10-24.
Is ObligationSign free?
No. Its pricing page showed no free plan on 2026-10-24.
Do people use ObligationSign?
Little sign of use.
Does ObligationSign have a free trial?
Yes, a 30-day free trial, per its pricing page (2026-10-24).
How we read a tool
No votes, no reviews, no vendor claims. Every week a crawler reads each tool's own site and a few public registries, and the words on the card are bands over what it read.
- Use: visits to the site (estimated), installs from npm and PyPI, presence in Chrome's usage report.
- Activity: the newest release on GitHub, npm or PyPI; the newest dated page on the site; open roles on a public jobs board.
- Price: the vendor's own pricing page, read with the date. A figure is printed only when it is on that page.
- The line and the use cases are written by us from the homepage, one tool at a time, and refused when they repeat the vendor's marketing.
How AI assistants read each site — the reading vendors ask us about — is on each tool's own visibility page.
How we read every tool → · By INITE Atlas Desk
Before we count this visit
Analytics and ad measurement tell us which pages and which of our ads do their job: Google Analytics and Google Ads, the Meta pixel, Yandex Metrica, and one first-party id of our own. Nothing is stored until you answer, and declining changes nothing about the site.