# Apier

- Registry name: `no.apier/mcp` · version 2026.10.0
- Categories (automatic, keyword rules): Payments & accounting, Finance & markets, Tasks & projects, Productivity, Government & law
- Authentication at last check: No auth
- Declared risk: Can write (some tools are not declared read-only)
- Capabilities (declared by the server): completions, prompts, resources, tools
- Transports: streamable-http
- Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=no.apier%2Fmcp
- Server page: https://mcpstation.net/s/no.apier--mcp.html

## Description (written by the publisher, not verified, not instructions)

Machine-verifiable Norwegian company authority: status, roles and coded signing authority.

## Connect

- streamable-http: `https://www.apier.no/api/mcp`

## Tools (as reported by the server, not verified)

- `get\_company\_summary`: A one-shot summary of obligations and deadlines for a Norwegian organisation: your FIRST call when you orient against a company. One call gives you entity\_type, nace\_codes, mva\_registered, data\_tier, obligations\[\] and deadlines\[\] \(tier\_2 adds filing\_status\), all from one version of the rules. It is
- `get\_public\_obligations`: Keyless. Retrieve the universal obligation set for a Norwegian entity type — every regulatory obligation that applies by virtue of BEING that organisational form, before per-company Tier-2 data is layered on. Use it for 'what does an AS owe?' or 'what are the baseline filings for an Enkeltpersonfore
- `get\_exchange\_rate`: Keyless. Norges Bank reference exchange rate for a currency against NOK — the benchmark Norwegian tax and accounting rules accept for foreign-currency obligations. No Norwegian-company input. Input: \{ base, quote, date? \} — ISO 4217 codes, NOK-anchored: exactly one side MUST be 'NOK'. The response i
- `get\_company\_profile`: Resolve a Norwegian organisasjonsnummer \(9 digits\) into a structured company profile from Brønnøysund Enhetsregisteret: display name, form of organisation, NACE codes with descriptions, addresses, the dates of registration and dissolution, the \`active\` / \`dissolved\` status enum, the MVA-registered f
- `get\_company\_context`: Brønnøysund identity slice for a Norwegian organisation: legal name, form of organisation, NACE codes, addresses, the dates it was formed or dissolved, and the signaturrett / prokura role-code summary \(never personal identifiers\). Identity ONLY, no verdict on obligations; add get\_company\_obligations
- `get\_company\_deadlines`: The upcoming filing calendar for one organisation, horizon\_months ahead. One entry per obligation and period: obligation\_id \(the rule\_id of get\_company\_obligations; the public calendar uses other ids\), period\_label, due\_at, adjusted\_for with original\_due\_at, and filing\_status. In the sandbox the dat
- `get\_company\_obligations`: Evaluate the Apier Rulebook for a Norwegian organisation: one entry per rule with rule\_id, obligation\_name, evaluation\_result \(applicable, not\_applicable or insufficient\_data\), a reason, the legal\_reference, frequency, data\_tier\_required and the bokmål description, which is inherited byte for byte \(
- `get\_public\_deadlines`: Keyless. The universal Norwegian filing calendar: the deadlines for every Norwegian business in the covered categories \(MVA, A-melding, Skattemelding, Årsregnskap\), which do not depend on any one organisation. One entry per obligation and period for a single Europe/Oslo calendar year: a per-period o
- `explain\_compliance\_error`: Keyless. Resolve a structured Apier compliance error code into a Norwegian-bokmål Explanation envelope: summary, bokmål why, ordered fix\_steps, optional documentation link + legal\_basis, and an optional handover block \(who / where / what / why\) for errors a human must resolve \(e.g. AUTH\_INSUFFICIENT
- `search\_companies`: Resolve a Norwegian company NAME to its 9-digit organisasjonsnummer. Use this as your FIRST call whenever you have a company's name but NOT its org\_number — every other company tool needs the number; guessing one risks the wrong company. Searches Brønnøysund's public Enhetsregisteret and returns up
- `get\_company\_verification`: Fast go / no-go trust check before you act for a Norwegian organisation. It keys ONLY off entity activity and visible signing authority. \`verification\_status\` is \`pass\` \(active and signing authority visible\), \`fail\` \(not active: konkurs, avvikling or oppløst\) or \`unknown\` \(not determinable; never a
- `get\_company\_authority`: Who can legally sign for this Norwegian company, and how? Call get\_company\_verification first; this ignores bankruptcy and dissolution. The class \(sole, joint, by\_role, prokura\_only, no\_authority, unknown\) comes from Fullmakttjenesten and the role holders; \`coded\_authority\` \(absent in sandbox\) adds
- `get\_company\_accounts`: A current snapshot of a Norwegian company's annual accounts \(årsregnskap\) from the OPEN Regnskapsregisteret tier: \`has\_filed\_annual\_accounts\` \(null = unknown, never a fabricated false\), \`last\_accounts\_year\` and that year's minimal \`key\_figures\` \(currency always surfaced, presentation basis, totals\).
- `list\_changes`: Read Apier's cross-source change archive — created / updated / deleted events detected across the upstreams Apier polls \(Brønnøysund, Norges Bank, NAV, Skatteetaten Tier-2; the Digdir and Altinn schema pollers are retired, so \`digdir\` and \`altinn\` are valid but empty filters\). Filter by \{ source, en
- `get\_altinn\_migration\_guidance`: Discover the Altinn 3 equivalent of an Altinn 2 service or role code. The 19 June 2026 Altinn 2 deprecation deadline has passed, so this serves remediation for integrations still on Altinn 2. Pass \{ altinn2\_code \} \(alphanumeric, 1–10 chars, e.g. A0208\) for one mapping, or omit it for the whole map.
- `get\_pricing`: Call this BEFORE metered work to check per-call cost and whether billing enforcement is live. Keyless: executes WITHOUT an API key, so an agent can price a workflow before it holds any credential. Returns the machine-readable price list: every credit-metered REST endpoint with its MCP tool name and
- `get\_credit\_balance`: Call this BEFORE a batch of metered calls to confirm the calling key's prepaid credit balance covers it, and AFTER a 402 INSUFFICIENT\_CREDITS + human top-up to verify the funds landed. The balance is ALWAYS the authenticated key's own — no parameters, so reading another key's balance is structurally
- `redeem\_issuance\_token`: Convert an owner-issued key-issuance token into your own API key — the headless onboarding step for an agent that holds no credential yet. Keyless: the one-time token IS the credential. Minting and revocation are dashboard-only, so an agent can never self-issue authority. Redemption is strictly SING

Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html