Skip to main content
Oathera logo Oathera
Use casesFive stories: no identity, a new identity, impersonation, cloning, and a call outside the boundary. PlatformOathera Agent Enrollment, the Oathera Identity Service and Oathera Agent Enforcement. FeaturesWhat Oathera does for you, grouped by purpose. IntegrationsYour identity provider, your MCP servers, your cloud. SecurityHow Oathera fails closed, and what it doesn't do.
Developer sectionComponents, the identity token, standards and settings. Data sheetsThe buyer and developer data sheets, as PDFs. LearnGuides on giving AI agents an identity of their own. GlossaryPrincipal, sponsor, anchor key, key digest, identity token. SimulatorWatch a stolen token, a replayed proof and a tampered call get refused.
About usThe team and the mission behind Oathera. BlogPosts from the Oathera team. CareersOpen roles at Oathera. ContactTalk to the founders, or become a design partner. LinkedIn ↗Oathera on LinkedIn.
Privacy PolicyHow we handle data. Terms of ServiceTerms for using Oathera. Data Processing AgreementOur DPA for customers. Sub-processorsThird parties we rely on.
Become a design partner

Learn · Governance

AI agent audit trails and EU AI Act accountability

An audit trail for AI agents should answer one question for every action: which agent did this, and which person answers for it. Records like that support the record-keeping and human-oversight expectations in regulation such as the EU AI Act. They do not make a system compliant on their own.

On this page

  1. What to record
  2. Provenance you can re-verify
  3. The EU AI Act in one paragraph
  4. How Oathera helps
  5. FAQ

What to record

  • The agent's verified identity, not a shared key.
  • The principal who approved it.
  • The exact operation and a hash of its arguments.
  • The decision, allow or deny, and why.
  • The time, and a way to check the record was not changed.

Provenance you can re-verify

A log line that says a token was used does not prove which agent made the call. A single-use operation proof over the exact request does. Keeping the proof with the record lets someone verify attribution later without trusting the logging pipeline alone.

The EU AI Act in one paragraph

The EU AI Act sets obligations by risk class. For high-risk systems it expects record-keeping, human oversight and transparency about how the system is used. Which obligations apply to you depends on your system, your role and your use. This is not legal advice. Ask your counsel what applies, and use records like these as evidence, not as a claim of compliance.

How Oathera helps

The Oathera Identity Service keeps a hash-chained audit log with signed seals and chain verification. Credential-like values are replaced by a correlation ID. Events can be exported exactly once to a SIEM or a write-once store, and there is one audit event per call through Oathera Agent Enforcement. Records name the agent and the approving principal. Oathera does not certify compliance with any regulation.

Oathera does not verify people, judge model output, inspect or rewrite prompts, or replace your identity provider. Your identity provider and proofing sources do the first; Oathera is the layer under them for agents.

FAQ

What should an AI agent audit trail contain?

The verified agent, the approving person, the exact operation and its arguments hash, the decision and a tamper-evident record.

Does Oathera make me EU AI Act compliant?

No. It provides identity, approval and decision records that can support accountability. Compliance depends on your system, risk class and processes.

What is agent provenance?

Evidence of which agent performed an action and under whose authority, that can be re-verified later.

Where do audit records go?

They are held in a hash-chained log at the Oathera Identity Service and can be exported exactly once to a SIEM or write-once store.

Related: Audit every action an AI agent takes · What agentic identity governance looks like · Standards map for AI agent identity

Become a design partner Watch the simulator More guides

← Back to Learn
Oathera logo Oathera

Every AI agent, sworn in. Oathera gives every AI agent an identity bound to the machine it runs on, with a named person who answers for it, and checked every time it acts.

Product

  • Use cases
  • Platform
  • Features
  • Integrations
  • Security

Developers

  • Developer section
  • Data sheets
  • Learn
  • Glossary
  • Simulator

Company

  • About us
  • Blog
  • Careers
  • Contact
  • GitHub

Legal

  • Privacy Policy
  • Terms of Service
  • Data Processing Agreement
  • Sub-processors
© 2026 Oathera Inc. · All rights reserved
Know Your Agent (KYA)

Cookie preferences

We use cookies to run this site and, with your consent, to understand usage and improve Oathera. Strictly necessary cookies are always on; you can choose whether to allow analytics and marketing cookies below.

Read the privacy policy

  • Strictly necessaryAlways on

    Required for the site to work, security, load balancing, and remembering your cookie choices. These cannot be switched off.

  • Help us measure traffic and see how the site is used, so we can improve it. No personal profiles are built.

  • Used to make messages about Oathera more relevant across other sites. Off unless you turn it on.