Why Apier

Sovereign friction is real and Norway should win from it.

Norwegian regulatory infrastructure is excellent for humans, and structurally unfinished for AI agents. Apier is the layer that turns the second statement into the first.

The thesis

Altinn, Brønnøysundregistrene, Maskinporten, and Skatteetaten are public infrastructure that Norwegian companies, accountants, and government services rely on every working day. The portals are documented. The APIs exist. The legal framework is published on Lovdata. What is missing is the layer that translates all of it into a single, deterministic, machine-readable answer that an AI agent can plan against. Agents do not read Norwegian PDF forskrifter. They do not infer from Brønnøysund role codes which person can submit MVA on behalf of which entity. They do not keep an Aksjeloven amendment calendar. That work is done once, correctly, by a small number of Norwegian compliance specialists today — and replicated badly, in private, by every team that tries to integrate. Apier exists to do it once and expose it as an API.

What is structurally missing

The gap is not one missing endpoint. It is the absence of a translation layer between four moving surfaces:

• Altinn 3 delegation as machine state. Altinn returns who has been granted which access package on behalf of which organisation. It does not return the next-step question an agent has: given this delegation set, which of the actions my user wants are legally authorised, and what specifically is missing if any of them is not.
• MVA thresholds and obligation cadence. The MVA threshold for registration, the bimonthly versus annual termin choice, the auditor trigger at 27 million NOK in turnover, the årsregnskap deadline that shifts on weekends — these are codified in Skatteforvaltningsloven, MVA-loven, Aksjeloven, and a stack of forskrifter. No public API returns the consolidated verdict for a given organisation. Every integrator either pays a compliance specialist to read the rules or hard-codes a brittle subset.
• Brønnøysund roles in Norwegian PDFs. Daglig leder, styremedlem, signaturrett, prokura, innehaver — the role taxonomy that determines who can act for an entity is spread across Brønnøysundregistrene, Aksjeloven, and per-role precedent. The data is published; the operational mapping from role plus action to “yes, this person can sign that filing” is not.
• Maskinporten as a credential lifecycle. Maskinporten is a clean OAuth2 server. Around it sit virksomhetssertifikat issuance, Samarbeidsportalen onboarding, scope approval cycles, key rotation, and the test versus production environment split. The cost of doing this once per integrating team is the cost of a senior engineer for several weeks per team, every year.

Who Apier is for, and who it is not for

Apier is for builders who need the verdict, not for end-users who need a portal.

• AI agent platforms. Claude, Cursor, MCP-compatible harnesses, LangChain or AutoGen pipelines, custom orchestrators. The tools the agent calls should be deterministic, dated, and legally citable. Apier ships that shape over both REST and the Model Context Protocol.
• Integrators wiring agents into Norwegian compliance. The team building an internal agent that files MVA, checks an auditor threshold, or validates an Altinn 3 delegation chain before acting. Apier removes the integration tax so the integrator can focus on the workflow.
• Foreign companies operating in Norway. Norwegian compliance is famously specific. Apier returns the same structured verdict regardless of which country the agent is reasoning from, so the team does not need a Norwegian compliance hire to ship.
• Accounting-software vendors. Tripletex, Fiken, Conta, PowerOffice and their peers all own the human workflow. Apier serves the integration layer underneath, so vendor teams can ship Altinn 3 delegation and obligation logic without owning the Maskinporten credential lifecycle in-house.
• Not the audience: individual taxpayers, end-users filing for themselves, or teams with one-off lookup needs. The agencies' own portals already serve those well, and Apier is intentionally not in that lane.

The moat

Norway has 5.5 million people. That is roughly the population of a mid-sized European metro. The math does not pay for a global platform to build a per-country regulatory translation layer at this scale — the integration is too specific, the rule cadence too local, and the customer base too small to land on a slide at an annual product review in Silicon Valley. The same math works in reverse for a domestically-anchored team: regulatory translation, government API integration, and auditable provenance are exactly the shape of product that scales sub-linearly with population and super-linearly with rule complexity. The relevant question is not whether a global player will compete on this surface — it is whether a Norwegian team will ship a deterministic, citable, agent-ready API before the window closes. Apier is that bet.

FAQ

Why route through Apier instead of calling Altinn, Brønnøysund, or Skatteetaten directly?

The agencies expose raw data. Apier turns that raw data into the verdict an AI agent actually needs to act on — who is allowed to file what, when the next deadline lands in Europe/Oslo, which Maskinporten scope authorises a given Altinn 3 endpoint, which MVA termin a given organisation owes. Direct calls are free and reasonable if your software needs one row from one register. If your agent needs to plan or act across registers, the integration cost flips toward Apier.

Is the data live or cached, and how fresh?

Brønnøysund company state is reconciled on read with a short cache; Altinn 3 delegations are resolved per request because they are the legal hook for who can act. Every response carries a _meta block with rulebook_version, data_freshness, and last_verified so an agent can decide whether to replan or proceed. Apier is deterministic: same inputs and rulebook version produce byte-identical outputs.

Where is data hosted? Does anything leave Norway or the EU?

Primary data lives in Supabase EU (Stockholm). Build and edge hosting is on Vercel EU edge with a migration off Vercel planned before real customer data flows. The well-known attestation at /.well-known/data-sovereignty publishes the subprocessor list, regions, and DPA status in a machine-readable shape so procurement teams and agents can verify it without asking us. See also our trust + transparency page.

Who is the typical Apier user, and who is not?

The typical user is an AI agent platform, an integrator wiring an agent harness to Norwegian compliance, a foreign company that needs to act in Norway without hiring a Norwegian compliance lead, or an accounting-software vendor whose product needs Altinn 3 delegation without owning the Maskinporten lifecycle. Apier is not for end-users filing their own taxes — that is Skatteetaten's surface — and not for one-off lookups, where calling Brønnøysund directly is cheaper.

How does Apier differ from Visma, Tripletex, or other Norwegian accounting platforms?

Accounting platforms own the human workflow: ledger, invoicing, payroll, the visible UI a finance team operates. Apier is the layer underneath, exposed as an API. An accounting platform can build on Apier the same way an agent can — get the obligation verdict, the deadline, the delegation chain, the structured error envelope — without rebuilding the Maskinporten and Altinn 3 plumbing in-house. Apier does not compete with the human-facing product; it serves the integration layer those products already need.

Related reading

• /sandbox — the zero-auth public sandbox surface, with curl-able examples of obligations, deadlines, and authorization verdicts.
• /docs — the developer docs, including the OpenAPI spec, the MCP server config, and the Compliance Explainer error catalogue.
• /use-cases/altinn-migration — the Altinn 2 to Altinn 3 migration page, with the access-package mapping table and the 19 June 2026 deadline math.
• /blog/altinn-3-migration-for-developers — the developer-facing migration guide, with code samples and the structured-error envelope shape.
• /blog/maskinporten-guide — the Maskinporten primer covering client setup, token lifecycle, and the Altinn System User delegation path.