Rammeverk / Framework
AVERT — verifiable execution for AI agents
AVERT is a five-step loop an AI agent follows to take a regulated action on Norwegian government systems and come away with cryptographic proof: Authorize, Validate, Execute, Receipt, Trail.
Hvorfor tradisjonelle API-er svikter for AI-agenterWhy traditional APIs fail for AI agents
Traditional APIs were built for developers who read docs and reason through edge cases. AI agents acting on Norwegian government systems (Altinn, Maskinporten, Brønnøysundregistrene, Skatteetaten, NAV) can’t — and the stakes are legal, not cosmetic. A hallucinated organisation number or a malformed tax submission is a liability, not a typo. AVERT defines how an agent takes a regulated action and ends with proof it can stand behind.
De fem trinnene i AVERTThe five steps of AVERT
Authorize
Confirm the agent is legally permitted to act for the entity, using Maskinporten credentials and Altinn delegation / acting-capacity checks, before anything else happens.
Validate
Every request passes through a deterministic sandbox that checks structure and legal grounding, returning machine-readable errors the agent can self-correct — no malformed payload reaches government.
Execute
The authorised call to Altinn, Maskinporten or Skatteetaten as the entity. Read actions are live today; write actions roll out per design partner.
Receipt
A signed, tamper-evident record of exactly what was submitted, alongside the raw government response, so the action can be independently verified later.
Trail
An append-only, compounding audit chain recording the full history of an entity’s regulated actions, which no one — including Apier — can rewrite.
AVERT og den juridiske tilstandsmaskinenAVERT and the Legal State Machine
Every AVERT loop advances the entity’s Legal State Machine — its position in a multi-step regulated workflow (register → organisation number → MVA → ongoing obligations). The agent always knows what is done, what is locked, and what comes next.
Vanlige spørsmålCommon questions
What is the AVERT framework?
AVERT is a five-step loop an AI agent follows to take a regulated action on Norwegian government systems and come away with cryptographic proof: Authorize, Validate, Execute, Receipt, Trail.
Why don’t traditional APIs work for AI agents?
Traditional APIs were built for developers who read docs and reason through edge cases. AI agents cannot, and the stakes are legal, not cosmetic — a hallucinated organisation number or a malformed tax submission is a liability, not a typo.
Does AVERT support write actions to Norwegian government systems?
Read actions are live today; write actions roll out per design partner. Execute is the authorised call to Altinn, Maskinporten or Skatteetaten as the entity, and every executed action produces a signed receipt and an append-only trail.
Kom i gangGet started
Data lookups are a commodity. Proof and trail are not — and that is the layer AVERT defines.