Apier.no
Apier.no provides machine‑verifiable Norwegian company authority data via an API. It offers status, roles, and coded signing authority directly from Brønnøysundregistrene, with source, history, and signed receipts. The service is self‑serve, with no sales call, and supports AI agents through MCP tools and OpenAPI specifications.
Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.
API Evangelist profiles Apier.no the way a machine reads it — 34 machine-readable artifacts across 1 API, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Apier.no scores 59.2/100 (strong), with a separate agent-readiness read of 68/100 (agent native). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-11-06 · rubric v0.27.0
Put this on your own site. The badge is drawn live from Apier.no's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/apier-no/"
title="Apier.no on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/apier-no.svg"
alt="Apier.no Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/apier-no/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/apier-no/"
title="Apier.no on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/apier-no/card.svg"
alt="Apier.no Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Apier.no
Each block below is one kind of artifact we hold for Apier.no. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 16
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Apier.no Account API
Consumer self-serve account management — sign-up, magic-link request, key issuance. The /api/v1/account/signup endpoint is `security: []` on purpose: an unauthenticated visitor ...
Apier.no Actions API
Withdrawn (2026-10-21). The filing-action surface (`POST /api/v1/actions/execute` in dry-run and live mode, the pending-action approve / reject / status routes) answers HTTP 410...
Apier.no Admin API
Administrative endpoints for managing consumers and API keys. Requires ADMIN_API_KEY.
Apier.no Altinn API
Withdrawn (2026-10-21). The Altinn-sourced authorisation surface (acting-capacity resolution over Altinn roles and delegations) answers HTTP 410 `CAPABILITY_WITHDRAWN`; its path...
Apier.no Auth Gateway API
Withdrawn (2026-10-21). The delegation endpoints that used to arrange Maskinporten and Altinn access on the consumer's behalf answer HTTP 410 `CAPABILITY_WITHDRAWN` on every cal...
Apier.no Brreg API
Brønnøysund Enhetsregisteret context surface — agent-shaped company profile reads. NLOD-licensed public data; role codes only, never personal identifiers (two-layer defense).
Apier.no Changes API
Cross-source change archive — detected archive events from Brreg, Altinn, DigDir, Norges Bank, NAV Aa-registeret, and Skatteetaten Tier 2 sub-results (MVA-register + Skatteoppgj...
Apier.no Company API
Reads over the Registry Engine's two-tier company model (Tier 1 public Brønnøysund data + Tier 2 gated commercial metrics).
Apier.no Discovery API
Agent-first discovery manifest. `/v1/capabilities` is the machine-readable menu of every callable capability; `llms.txt` and `workflows.json` are the prose and recipe counterparts.
Apier.no Fullmakt API
Withdrawn (2026-10-21). The fullmakt line (agent principals, brokered Altinn systembruker delegations, their receipts and revocation) answers HTTP 410 `CAPABILITY_WITHDRAWN` on ...
Apier.no Infrastructure API
Non-product endpoints (health checks, discovery).
Apier.no Knowledge API
The Knowledge Catalog — canonical, machine-readable topic records answering what an agent needs to KNOW about Norwegian company authority and government-integration subjects (Al...
Apier.no Privacy API
Zero-auth GDPR transparency endpoints — Article 15 access requests via DSR. Rate-limited per IP (10/min, lower than Category A's 1000/min) so the surface cannot be used as a nam...
Apier.no Public API
Free, zero-auth endpoints. Rate-limited per-IP (soft cap 1000/min). Distribution infrastructure, not revenue — these exist so agents can discover the API surface and answer base...
Apier.no Sandbox API
Zero-auth, deterministic, CORS-open mirrors of every Category B company endpoint. Returns synthetic Norwegian company fixtures so agents can test failure-flows without provision...
Apier.no Subscriptions API
Pro-tier change-detection webhook subscriptions. Consumers register a webhook URL + filter; Apier fires HMAC-SHA256-signed deliveries when matching change-archive events appear....
Scroll within the panel for all 16 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
Pricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Apier No Rate Limits
RATE LIMITSEvent Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Apier No Webhooks
ASYNCAPISemantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Apier No Context
JSON-LDSpectral Rules 1
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Apier.no API Rules
SPECTRALJSON Schema 6
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
CompanyContext
JSON SCHEMACompanyVerification
JSON SCHEMAErrorCode
JSON SCHEMASandboxMeta
JSON SCHEMASignedReceipt
JSON SCHEMATrustMetadata
JSON SCHEMASecurity Posture 4
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Apier.no — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 3
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 5
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 10
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 10 ·
Access & Security 8
Authentication, authorization, and security posture
Scroll within the panel for all 8 ·
Operate 5
Status, limits, changes, and where to get help
Commercial 4
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 2
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/apier-no · machine-readable index on apis.io
This is an independent, third-party profile of Apier.no, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.