Axtary vs Legibility Field Kit

Axtary and Legibility Field Kit are both guardrails & safety tracked by AIDiveForge. Below is a side-by-side comparison of pricing, capabilities, platforms, and ownership — sourced from each tool's live website and verified before publishing.

Axtary

Axtary sits beside the agent and evaluates each tool call against deterministic policy before the underlying provider is called. Routine actions — ones that clear the policy rules — pass automatically. Higher-risk actions pause for a human to review the normalized payload, and the approval is cryptographically tied to that specific hash. If anything changes after sign-off, the adapter catches the mismatch and blocks execution. Every attempt, pass, and rejection lands in a verifiable ledger. The self-hosted path keeps provider credentials local, which matters for teams that cannot route credentials through a third-party service.

Legibility Field Kit

The kit is a zero-dependency Python CLI that runs three checks against your AI decision records: does every change name a specific human owner, is time-to-reverse recorded for reversible actions, and does each entry carry a complete OTW receipt — Owner, Time, Witness. Run `audit` against a directory of governance files and it surfaces every defect in seconds. The scoring command turns those findings into a maturity grade across the three tests, giving compliance teams a number to track sprint over sprint. The wall appears fast: the kit reads files, flags gaps, and stops — it does not integrate with your ticketing system, your CI pipeline, or your approval workflow.

Attribute	Axtary	Legibility Field Kit
Pricing	Paid	Paid
Free trial	30 days	No
Open source	No	Yes
Has API	No	No
Self-hosted option	Yes	Yes
Platforms	—	Python
Pros	Payload hash binding ties every human approval to the exact diff or message reviewed, so a payload altered after sign-off is rejected at the adapter before the provider is called — eliminating the attack surface where approval covers a summary rather than the literal content. Deterministic policy evaluation on routine actions means low-risk tool calls clear automatically, so human reviewers only see the calls that actually warrant attention rather than approving every agent action manually. Self-hosted policy enforcement keeps provider credentials local, so teams under data-residency or credential-exposure constraints can run authorization checks without routing sensitive tokens through a third-party service. A verifiable ledger records every decision, pass, execution result, and trace reference, so teams facing a post-incident audit have a timestamped, tamper-evident record of what the agent was authorized to do and what actually ran. ActionPass artifacts carry normalized action records — actor, intent, resource, constraints, and policy version — structured for consumption across SDKs and MCP wrappers, so teams can integrate authorization evidence into existing tooling without custom log parsing.	Zero external dependencies, so the tool runs in an air-gapped or locked-down environment without a dependency audit of its own — which means regulated teams do not have to clear a supply-chain review just to use the auditor. The `init` command scaffolds governance files before a system goes live, so teams start with compliant structure rather than retrofitting it after a finding. OTW receipt detection — Owner, Time, Witness — catches the specific pattern where 'the team' or 'engineering' appears in the owner field, which is the defect that makes approval records legally meaningless under most accountability frameworks. Apache-2.0 license with self-hosted option, so your governance records and their audit results never leave your own infrastructure — critical when the files themselves contain sensitive decision rationale. Maturity scoring across three discrete tests gives compliance leads a metric that moves, so governance improvement has a number attached rather than being a qualitative assertion.
Cons	The hash-binding guarantee only holds for connectors that implement the adapter-side verification step. Teams whose agents call tools outside the documented connector set — anything not in the GitHub, Slack, Linear, AWS/GCP, MCP, or document-search list — must write and maintain their own adapter verification before Axtary's core security property applies to those calls. Axtary enforces policy on proposed actions; it does not generate, plan, or sequence agent tasks. Teams that need an authorization layer bundled with agent orchestration — where the same system routes tasks and enforces rules — will hit this ceiling immediately and look at platforms that combine both concerns. The product is in access-request stage with a small documented connector surface, which means teams with production timelines that cannot absorb an integration build or a waitlist delay will default to a more established policy enforcement tool rather than waiting for connector coverage to expand.	The kit audits files that already exist — if your team's governance process lives in Jira tickets, Confluence pages, or Slack threads rather than structured files in a directory, there is nothing for the tool to read, and the first project becomes manually exporting records into a format the CLI can parse. There is no CI integration, webhook, or pre-commit hook provided out of the box, so the audit runs when someone remembers to run it; teams that need enforcement at the moment a decision is logged — not after the fact — add their own pipeline glue, at which point they are maintaining that integration themselves. The repository shows two stars and a single commit at time of listing, which means community-tested edge cases, maintained issue trackers, and peer-vetted documentation are absent; teams with complex governance schemas that do not match the demo structure have no community forum to consult and will be reading source code to understand behavior, which pushes some teams toward building a custom linter in-house instead.

Bottom line

Legibility Field Kit is open source. Choose based on which difference matters most for your workflow.

Frequently asked questions

What is the difference between Axtary and Legibility Field Kit?

Axtary is Paid, while Legibility Field Kit is Paid and open source. Compare pricing, free trial, API, platforms, and pros/cons in the table above on AIDiveForge.

Is Axtary better than Legibility Field Kit?

It depends on your workflow. Use the side-by-side attributes (pricing, open source, API, self-hosted, platforms) to decide. AIDiveForge does not rank a universal winner — we publish verified facts so you can choose.