Rammeverk / Framework
AVERT — verifiable execution for AI agents
AVERT is a five-step loop an AI agent follows to check a Norwegian company before it acts, and to keep cryptographic proof of what it verified: 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 checks before it acts and ends with proof of what it verified.
De fem trinnene i AVERTThe five steps of AVERT
Authorize
Read the entity's registered signing rule (signaturrett and prokura from Brønnøysund) before anything else happens, and let your agent apply it to the action at hand. Apier does not check Altinn rights or delegations.
Validate
The agent checks the planned action against what the register states, and every error Apier returns is machine-readable, so the agent can self-correct. Apier forwards nothing to government.
Execute
The call made as the entity, in the entity's own systems and under its own credentials. Apier reads; it does not execute writes to Altinn, Maskinporten or Skatteetaten for anyone.
Receipt
A tamper-evident record of what was read, from which register and when: every response carries a response hash and timestamp in _meta, Apier stores a provenance record of each read, and a signed certificate is available on request, so the basis for the action can be independently verified later. Apier submits nothing to government, so no government response is involved.
Trail
An append-only, compounding audit chain recording the full history of an entity’s regulated actions, which no one, Apier included, 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 check a Norwegian company before it acts, and to keep cryptographic proof of what it verified: 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?
No. Apier's read actions are live today, and Apier does not execute writes to Altinn, Maskinporten or Skatteetaten. In the AVERT loop, Execute is the step the entity takes in its own systems; the framework asks that every executed action produce 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.