Compliance glossary
Norwegian regulatory terms + Apier-specific concepts in plain English.
[Cite this as: Apier.no Docs v0.1.0 — last updated 2026-10-21]
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 may sign for the company, as the register records it |
| 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: the API key your agent presents, with Apier's own Maskinporten client kept for Apier's own government reads. Apier does not broker Maskinporten or Altinn credentials, system users or delegations for customers (withdrawn 2026-10-21).
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 filing 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 at /api/mcp, packaged as @apier-no/mcp
on npm, exposing 21 deterministic MCP tools (20 discoverable via tools/list +
1 hidden-by-design: the sandbox-only submit_vat_return) covering company reads, obligations
and deadlines, signing authority from Brønnøysund, signed evidence packs, and keyless
issuance-token redemption — each forwarding to an
Apier REST endpoint — so an AI agent can call Apier as native MCP tools.
("Deterministic" is the Rule-9 output contract of the read and validation
tools; the onboarding write redeem_issuance_token is deliberately
single-use — its one-time token cannot be redeemed twice, so it must never
be retried on the deterministic-read assumption.)
Intent-to-Action Parser
The component that once resolved an action request into dry-run and live-submission pipelines. Filing submission is parked and not offered (2026-10-21): the action routes answer HTTP 410 CAPABILITY_WITHDRAWN. See the capability status page for the operational state.
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.
Agent verification terms
Terms for checking an AI agent and the company it acts for. These are industry terms, not Norwegian legal terms and not terms Apier coined.
Know Your Agent (KYA)
Verifying an AI agent: which agent it is and who operates it. Agent identity comes from the agent platform or an identity provider. Apier does not provide it.
Know Your Business Agent (KYBA)
Verifying the legal entity behind an AI agent and the authority that agent claims to act under. Apier provides the company-authority layer of KYBA for Norway: whether the company exists and is active, and the register's coded signing rules for it, with signed evidence.
The full definition and the coverage table are at /kyba (Norwegian: /no/kyba).
Apier MCP Server: Tool Reference and Setup Guide
Developer reference for the Apier MCP server at /api/mcp: how a tool call flows, what the 21 tools cover and where to configure an MCP client.
Error reference
The canonical Apier error reference: the standard error envelope, the explanation and handover schemas, and the full structured error_code catalogue.