Apier's docs are written in English, but the Norwegian regulatory vocabulary does not translate cleanly. Terms like MVA, skattemelding, and signaturrett are treated as technical proper nouns throughout the docs and the API — the same way you would not translate GDPR or OAuth2. This glossary bridges the two: use it when a Norwegian term appears in an API response, an error message, or a legal citation and you want the one-line English context.

Terms

Norwegian	English	Context
MVA (Merverdiavgift)	VAT	Tax on goods and services
A-melding	Employer payroll report	Monthly reporting to tax authority
Skattemelding	Tax return	Annual tax filing
Årsregnskap	Annual accounts	Financial statements filed to Brønnøysund
ENK (Enkeltpersonforetak)	Sole proprietorship	Business entity type
AS (Aksjeselskap)	Limited company	Business entity type
Prokura	Power of procuration	Legal authority to bind a company
Signaturrett	Signing authority	Who can legally sign for the company
Daglig leder	CEO / Managing director	Company leadership role
Regnskapsbyrå	Accounting firm	Professional service provider
Brønnøysundregistrene	Norwegian Business Register	Government registry
Skatteetaten	Norwegian Tax Administration	Government agency
Altinn	Government digital services platform	Filing and delegation portal
Maskinporten	Machine-to-machine auth gateway	Government OAuth2 service
Yrkesskadeforsikring	Occupational injury insurance	Mandatory employer insurance
Revisor	Auditor	Required above certain thresholds
NACE-kode	Industry classification code	EU standard activity codes
Foretaksregisteret	Register of Business Enterprises	Legal entity registry
Tilgangspakke	Access package	Altinn permission bundle
Organisasjonsnummer	Organisation number	Unique 9-digit identifier from Brønnøysundregistrene

How terms appear in the API

Norwegian terms are preserved in API responses as proper nouns — for example, mva_registered, signaturrett_type, prokura, and entity_type: "AS". See /openapi.json for the canonical field names and shapes.

Apier-specific terms

Apier's own infrastructure is described in terms of named components — the eight that do the work behind every tool — plus the framing concept the platform is built around. These describe Apier's architecture, not Norwegian legal terms.

Auth Gateway

Apier's authentication layer: Maskinporten client-assertion, token caching, and the Altinn 3 System User delegation flow, so callers use one Bearer API key and raw government tokens are never exposed.

Registry Engine

The component that reconciles canonical company state across Brønnøysund, Skatteetaten, NAV, and Altinn.

Universal Rulebook

Apier's versioned store of Norwegian regulatory rules with legal-reference citations. Evaluation is deterministic — the same input plus rulebook version produces byte-identical output.

Deadline Engine

The component that computes Norwegian compliance deadlines — MVA terminer, A-melding cadence, skattemelding, årsregnskap — as calendar math in Europe/Oslo, DST- and holiday-aware.

MCP Server

Apier's Model Context Protocol server, exposing the same tools as the REST API at /api/mcp and packaged as @apier-no/mcp on npm, so an AI agent can call Apier as native MCP tools.

Intent-to-Action Parser

The component that resolves an action request into dry-run and live-submission pipelines, running validation gates before any upstream call and requiring a one-time approval token for live submission.

AI-Agent Discovery

Apier's machine-discovery surfaces — llms.txt, llms-full.txt, workflows.json, /api/v1/capabilities, and the well-known manifests — kept populated and stable so agents can discover the API.

Compliance Explainer

The component that resolves every Apier error_code into a structured Explanation envelope (summary, why, fix_steps, legal_basis, handover) in Norwegian bokmål via POST /api/v1/explain.

Sovereign Friction

Apier's framing for the structural cost of integrating Norwegian regulatory infrastructure — excellent for humans but unfinished for AI agents, and changing every quarter. The platform exists to absorb that friction once and expose it as an API. A concept, not one of the eight components.

Compliance glossary