Get This Tool
AGEF
Pricing
- Model
- Free
Summary
Regulated industries get burned when an agent incident happens and the only evidence is logs you wrote yourself — logs that prove nothing to an auditor who wants tamper-evident, independently verifiable records. AGEF is an open specification that defines exactly how agent sessions get packaged into bundles an auditor, regulator, or incident responder can verify without trusting you.
The specification defines a content-addressed, Merkle-linked event structure so every decision in an agent session can be hashed, bundled, and checked offline — no live service required. The reference implementation is Akmon (v2.0.0 and later), which handles bundle export, import, and journaling via akmon-journal. AGEF is a format standard, not a deployed platform: there is no SaaS, no API, and no hosted verification service. Teams adopting it are taking on the work of building or integrating bundle-producing substrates into their existing agent infrastructure. At v0.1.1, the spec is pre-stable — conformance profiles and bundle structure are defined, but tooling outside the Akmon reference implementation is essentially absent.
Bottom line: AGEF is the right foundation if your team is building agent infrastructure in aerospace, medical devices, or financial services and needs to hand an auditor a cryptographically verifiable session record — but if you need a drop-in solution that works with your existing agent framework today, the spec will hand you a build project, not a product.
Community Performance Report Card
No community ratings yet. Be the first to rate this tool!
Community Benchmarks Community
Sign in to submit a benchmarkNo community benchmarks yet. Be the first to share a real-world data point.
Pros
Sign in to edit- Offline, cryptographic bundle verification — no live service required — so an auditor or regulator can independently confirm session integrity without access to your internal systems or trusting your logging infrastructure.
- Merkle-linked event structure means the record is tamper-evident by construction, which means you hand a regulator a bundle and the math proves whether it was altered, rather than asking them to take your word for it.
- Deterministic session replay against recorded tools and providers, so incident responders can reconstruct exactly what the agent did during an outage or compliance event without relying on mutable runtime state.
- Apache-2.0 code license and CC BY 4.0 spec license, which means regulated organizations can adopt, implement, and distribute the format without commercial licensing friction or vendor lock-in.
- Two defined conformance profiles (Bundle and Substrate) give implementers a clear contract for what 'compliant' means, so independent tools from different vendors can interoperate around the same audit record.
Cons
Sign in to edit- The only shipped bundle exporter is Akmon v2.0.0 and later — teams not running Akmon must implement the spec themselves from SPEC.md, which means committing engineering time to build and maintain a conforming substrate before a single audit bundle gets produced.
- At v0.1.1, the spec is explicitly pre-stable, so the bundle structure and conformance requirements are subject to change before a stable release; teams that ship a production implementation against v0.1.1 inherit the maintenance cost of tracking and absorbing breaking changes.
- There is no SaaS verification service, no hosted tooling, and no API — organizations that need a drop-in audit trail solution with minimal integration lift will abandon AGEF for a commercial agent observability platform that ships its own tamper-evident logging and verification UI out of the box.
Community Reviews
Sign in to write a reviewNo reviews yet. Be the first to share your experience.
About
- Platforms
- Cross-platform (specification language-agnostic)
- API Available
- No
- Self-Hosted
- Yes
- Last Updated
- 2026-06-01T01:51:31.209Z
Best For
Who it's for
- Organizations in regulated industries (aerospace, medical devices, financial services, defense)
- Teams needing to prove agent behavior during incident response or regulatory reviews
- Developers building agentic systems that must demonstrate tamper-evident audit trails
What it does well
- Creating auditable records of autonomous agent decisions for regulatory compliance
- Enabling offline verification and cryptographic validation of agent session integrity
- Supporting incident response by replaying agent sessions deterministically against recorded tools and providers
- Producing tamper-evident evidence for SOC 2, FDA, SEC, and other regulatory audits
Integrations
Discussion Community
Sign in to commentNo discussion yet. Sign in to start the conversation.
Compare AGEF
Spotted incorrect or missing data? Join our community of contributors.
Sign Up to ContributeCommunity Notes & Tips Community
Sign in to contributeBe the first to contribute. General notes, observations, gotchas, and tips from people who use this tool day-to-day.
Frequently Asked Questions
- Is AGEF free?
- Yes — AGEF is fully free to use. There is no paid tier.
- Is AGEF open source?
- Yes. AGEF is open source — the source repository is at https://github.com/radotsvetkov/agef.
- Can I self-host AGEF?
- Yes. AGEF supports self-hosting on your own infrastructure.
- When was AGEF released?
- AGEF was first released in 2024.
- What platforms does AGEF support?
- AGEF is available on: Cross-platform (specification language-agnostic).
Hours Saved & ROI Stories Community
Sign in to contributeBe the first to contribute. Concrete time/cost savings, with context. e.g. "Cut my code review backlog from 4h to 45m per week."
AGEF (Agent Governance Evidence Format) defines how an AI agent session gets serialized into a portable, tamper-evident bundle: content-addressed objects plus Merkle-linked events that can be transferred across systems, verified offline, and reviewed by independent tooling. The core workflow is that a conforming substrate records agent events during a session, exports them as an AGEF bundle (per SPEC.md Sections 5–14), and any downstream tool — an auditor’s workstation, an incident responder’s isolated environment — can import and verify the bundle without calling back to the original system.
The format’s primary differentiator is cryptographic independence. Because events are content-addressed and Merkle-linked, verification does not require the original agent system to be running or trusted. An auditor can replay the session deterministically against the recorded tools and providers, which is exactly what SOC 2, FDA, SEC, and similar regulatory frameworks require when they ask you to prove what your agent did and that the record was not altered after the fact.
AGEF fits teams who own their agent infrastructure and are willing to build conforming bundle producers. The spec defines two conformance profiles — Bundle Profile (producing and consuming bundles) and Substrate Profile (maintaining the event journal) — and the only shipped reference implementation is Akmon v2.0.0 and later. Teams not running Akmon have no off-the-shelf exporter; they implement the spec themselves. At v0.1.1, this is a pre-stable format, which means the structure can change before a stable release and teams building against it should track CHANGELOG.md and SPEC.md closely.
Licensing is split: the specification text is released under CC BY 4.0 and the code under Apache-2.0, so organizations can adopt and implement the format without commercial licensing concerns. The repository includes a minimal-bundle example under the examples directory, which is the primary onboarding artifact for teams evaluating implementation scope.