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.

Apier.no publishes 16 API contracts indexed on the APIs.io network, including Account API, Actions API, Admin API, and 13 more. Tagged areas include Norwegian, Company Data, MCP, and Verification.

The Apier.no catalog on APIs.io includes 1 event-driven AsyncAPI specification, 1 JSON-LD context, and 1 Spectral governance ruleset.

Apier.no’s developer surface includes authentication, sandbox, changelog, getting-started guide, documentation, API reference, pricing, and 38 more developer resources.

Pull Apier.no's APIs, OpenAPI, scores and pricing into your own code or AI agent with a free APIs.io key — sign in with GitHub, Google or LinkedIn. No form to fill in; signing in shares your email address with us (Privacy).
72.7/100 exemplar ▬ flat Agent 66/100 agent native Full breakdown ↓
scored 2026-11-21 · rubric v0.28.1 · Show this score on your site →
1 published contract 1 MCP Servers
NorwegianCompany DataMCPVerification

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-11-21 · rubric v0.28.1
Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.
Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.
The six quality facets above are damped to 75 points between them, because the conditional facet above carries the other 25. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 75% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.
Show this score on your site. Kin Score badge preview for Apier.no It updates itself when the score changes. Paste this where you link to your API docs:
<a href="https://apis.io/providers/apier-no/"><img src="https://apis.io/badge/apier-no/card.svg" alt="Apier.no on APIs.io — Kin Score by API Evangelist"></a>
Other styles, a README pill and a shields.io endpoint are on the badge page.
Raise your score.
Agent readiness — checks not met, largest first (exact, from this profile):
  • A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0 Ask about this →
  • Documented Reversibility +6 pts — a reversal operation in the contract, graded up when a window is documented too Ask about this →
  • Pagination +5 pts — share of collection GETs (an array, or one wrapped in data/items/results ...) that declare a page/limit/offset/cursor parameter, a Link header or a next/cursor field; na with no collection GETs Ask about this →
  • Agentic Commerce Well-Known Document +5 pts — a parsing /.well-known/ucp (the IANA-registered path, probed first) or ucp.json / acp.json declaring a version and at least one service, OR (0.27) a live x402 payment challenge from _data/x402-adoption.json — `self` when its endpoints are on the provider's own domain, `platform` when they are on a vendor's Ask about this →
  • Onboarding Descriptor Published +3 pts — the provider page carries onboarding_descriptor.published (an APIOnboarding pointer, provider- or API-level, or a saved /.well-known/api-onboarding body with an `aod` key, build.py _onboarding_descriptor_meta) Ask about this →
  • Consent & Bot Identity +3 pts — (0.28.1) deployed = a served Web Bot Auth key directory at /.well-known/http-message-signatures-directory with a key set; signal = a Content-Signal or Content-Usage line in the provider website's robots.txt (the dated per-provider agent-docs probe, else the census); an apis.yml type claim alone earns nothing Ask about this →
Kin Score — facets with the most composite points still available (weight × headroom):
Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.
Not sure how this applies to your stack? Ask about any one item. Kin Lane reads every question, looks at your profile and your situation, and replies with what a fix would take — scoped to that one area, priced up front, yours whether you ship it or not. Ask a question →
Ask about:
Apier No · a person reads this and replies by email.
or email info@apis.io
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/apier-no/apis.yml: open an issue on github.com/api-evangelist/apier-no to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Standards implemented 5

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

measured — observed by APIs.io (documented)
measured — observed by APIs.io (verified)
measured — observed by APIs.io (published)
measured — observed by APIs.io (published)
measured — observed by APIs.io (served)

APIs 16

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 for all 16

MCP Servers 1

Model Context Protocol servers that expose these APIs to AI agents.

Apier.no MCP Server

Remote MCP server at www.apier.no.

MCP SERVER

Apier.no API pricing

Prices published by Apier.no.

PlanPrice
Pay-as-you-go 50 øre per metered company read

Plan details, limits and sources →

Rate limits

All 4 limits →

Pricing Plans 1

Published pricing tiers and plan structures.

Rate Limits 1

Documented rate limits and quota policies.

Apier.no Rate Limits

4 limits

RATE LIMITS

Service Levels 1

Uptime the provider promises or reports, as SLA4OAI. Read from its own pages; APIs.io runs no monitors.

Terms of Service 1

What its API terms permit and prohibit, quoted from its own page.

Apier.no

9 quoted statements, read from Apier.no's own page on 2026-11-09.

TERMS

Privacy & Data 1

Its role, the data it processes, retention and transfers, quoted from its own privacy page.

Apier.no

24 quoted statements, read from Apier.no's own page on 2026-11-09.

PRIVACY

Eligibility 1

Who may sign up and where, quoted from its own terms.

Apier.no

4 quoted statements, read from Apier.no's own page on 2026-11-09.

ELIGIBILITY

AI Preferences 1

Its stance on AI training, inference and agents, quoted from its own pages.

Apier.no

3 quoted statements, read from Apier.no's own page on 2026-11-09.

AI PREFS

Event Specifications 1

AsyncAPI definitions for this provider's event-driven and streaming APIs.

Semantic Vocabularies 1

JSON-LD contexts and semantic vocabularies used across these APIs.

Apier No Context

113 classes · 363 properties

JSON-LD

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs. Counts are the severity each rule declares, not results of running them.

Apier.no API Rules

78 rules · 61 error-severity 16 warn-severity 1 info-severity

SPECTRAL

OpenAPI Overlays 1

Overlays applied on top of this provider's contracts. Each card says who wrote it: a document the provider publishes, or one API Evangelist derived or generated.

Apier.no Openapi Overlay

0 actions · update

UNRECORDED

JSON Schema 6

Standalone JSON Schema definitions for this provider's data models.

CompanyContext

22 properties

JSON SCHEMA

CompanyVerification

15 properties

JSON SCHEMA

ErrorCode

0 properties

JSON SCHEMA

SandboxMeta

15 properties

JSON SCHEMA

SignedReceipt

12 properties

JSON SCHEMA

TrustMetadata

25 properties

JSON SCHEMA

Security Posture 4

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Apier.no Authentication

5 schemes

SECURITY

Apier.no Domain Security

TLSv1.3 · HSTS · DNSSEC · DMARC

SECURITY

Apier.no Vulnerability Disclosure

security.txt · contact published

SECURITY

Apier.no Trust Center

GDPR

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Apier.no Scopes

OAuth 2.0 · no documented scopes

0 scopes

SCOPES

Agentic Access (API Evangelist recommendations) 1

Recommended x-agentic-access execution contracts for AI agents.

Apier.no Agentic Access

156 operations · 48 acting · 6 human-in-the-loop

156 operations · 48 acting

AGENTIC

Resources

Get Started 3

Portal, sign-up, and the first successful call

Documentation 3

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 for all 10

Access & Security 8

Authentication, authorization, and security posture

Scroll for all 8

Operate 5

Status, limits, changes, and where to get help

Commercial 5

Pricing, plans, and the legal terms of use

Company 2

The organization behind the API

Other 4

Properties that don't map to a standard resource type

Source (apis.yml)

apis.yml Raw ↑
aid: apier-no
name: Apier.no
description: 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.
url: https://artifacts.apis.io/apier-no/apis.yml
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source:
  - plans
  - authentication
  - rate-limits
  - security
  - sandbox
  generated: '2026-11-20'
  method: derived
image: https://www.apier.no/logo.svg
x-type: company
x-source: harvest:mcp-registry
x-tier: profiled
x-tier-reason: enrichment pass 2026-11-01 (modular-v1; was harvest)
specificationVersion: '0.20'
created: '2026-11-01'
modified: '2026-11-01'
tags:
- Norwegian
- Company Data
- MCP
- Verification
tags_raw:
- Norwegian
- CompanyData
- API
- MCP
- Verification
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: AgenticAccess
  url: agentic-access/apier-no-agentic-access.yml
- type: RateLimits
  url: rate-limits/apier-no-rate-limits.yml
- type: Plans
  url: plans/apier-no-plans-pricing.yml
- type: Spectral
  url: rules/apier-no-rules.yml
- type: JSONLD
  url: json-ld/apier-no-context.jsonld
- type: Vocabulary
  url: vocabulary/apier-no-vocabulary.yml
- type: AgentSkill
  url: skills/_index.yml
- type: Webhooks
  url: asyncapi/apier-no-webhooks.yml
- type: DataModel
  url: data-model/apier-no-data-model.yml
- type: Idempotency
  url: conventions/apier-no-conventions.yml
- type: Conventions
  url: conventions/apier-no-conventions.yml
- type: Compliance
  url: https://www.apier.no/trust
- type: Authentication
  url: authentication/apier-no-authentication.yml
- type: Lifecycle
  url: lifecycle/apier-no-lifecycle.yml
- type: ErrorCatalog
  url: errors/apier-no-problem-types.yml
- type: Conformance
  url: conformance/apier-no-conformance.yml
- type: LLMsTxt
  url: llms/apier-no-llms.txt
- type: MCPServer
  url: mcp/apier-no-mcp.yml
- type: SecurityTxt
  url: well-known/apier-no-security.txt
- type: SecurityTxt
  url: well-known/apier-no-apier-security.txt
- type: WellKnown
  url: well-known/apier-no-well-known.yml
- type: Hosts
  url: hosts/apier-no-hosts.yml
- type: Vendors
  url: vendors/apier-no-vendors.yml
- type: Security
  url: https://www.apier.no/security
- type: Sandbox
  url: https://www.apier.no/sandbox
- type: ChangeLog
  url: https://www.apier.no/docs/changelog
- type: GettingStarted
  url: https://www.apier.no/docs/quickstart
- type: TrustCenter
  url: security/apier-no-trust-center.yml
- type: VulnerabilityDisclosure
  url: security/apier-no-vulnerability-disclosure.yml
- type: DomainSecurity
  url: security/apier-no-domain-security.yml
- type: Website
  url: https://apier.no/
- type: Documentation
  url: https://www.apier.no/docs
- type: APIReference
  url: https://www.apier.no/openapi.json
- type: Pricing
  url: https://www.apier.no/pricing
- type: Blog
  url: https://www.apier.no/blog
- type: Support
  url: https://www.apier.no/support
- type: Roadmap
  url: https://www.apier.no/roadmap
- type: Login
  url: https://www.apier.no/login
- type: TermsOfService
  url: https://www.apier.no/terms
- type: PrivacyPolicy
  url: https://www.apier.no/privacy
- type: StatusPage
  url: https://apier.betteruptime.com/
- type: UsageTerms
  url: terms/apier-no-terms-of-service.yml
- type: DataProcessing
  url: privacy/apier-no-privacy-policy.yml
- type: Eligibility
  url: eligibility/apier-no-eligibility.yml
- type: AIPreferences
  url: ai-preferences/apier-no-ai-preferences.yml
apis:
- aid: apier-no:apier-no-account-api
  name: Apier.no Account API
  description: '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 can request a magic link without holding any prior credential.'
  humanURL: https://www.apier.no/docs/api
  baseURL: https://www.apier.no
  tags:
  - Account
  properties:
  - type: OpenAPI
    url: openapi/apier-no-account-api-openapi.yml
  - type: JSONSchema
    url: json-schema/apier-no-trust-metadata-schema.json
  - type: JSONSchema
    url: json-schema/apier-no-company-verification-schema.json
- aid: apier-no:apier-no-actions-api
  name: Apier.no Actions API
  description: '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 `CAPABILITY_WITHDRAWN`: the dry run read Altinn
    delegation state and the live leg is the parked MVA submission line. Paths and schemas stay published (append-only contract).'
  humanURL: https://www.apier.no/docs/api
  baseURL: https://www.apier.no
  tags:
  - Actions
  properties:
  - type: OpenAPI
    url: openapi/apier-no-actions-api-openapi.yml
  - type: JSONSchema
    url: json-schema/apier-no-trust-metadata-schema.json
  - type: JSONSchema
    url: json-schema/apier-no-signed-receipt-schema.json
- aid: apier-no:apier-no-admin-api
  name: Apier.no Admin API
  description: Administrative endpoints for managing consumers and API keys. Requires ADMIN_API_KEY.
  humanURL: https://www.apier.no/docs/api
  baseURL: https://www.apier.no
  tags:
  - Admin
  properties:
  - type: OpenAPI
    url: openapi/apier-no-admin-api-openapi.yml
  - type: JSONSchema
    url: json-schema/apier-no-trust-metadata-schema.json
- aid: apier-no:apier-no-altinn-api
  name: Apier.no Altinn API
  description: 'Withdrawn (2026-10-21). The Altinn-sourced authorisation surface (acting-capacity resolution over Altinn roles
    and delegations) answers HTTP 410 `CAPABILITY_WITHDRAWN`; its paths and schemas stay published (append-only contract).
    Not affected: the static Altinn 2 to Altinn 3 migration map under `Public` (public Digdir documentation, no Autorisasjon
    data).'
  humanURL: https://www.apier.no/docs/api
  baseURL: https://www.apier.no
  tags:
  - Altinn
  properties:
  - type: OpenAPI
    url: openapi/apier-no-altinn-api-openapi.yml
  - type: JSONSchema
    url: json-schema/apier-no-trust-metadata-schema.json
- aid: apier-no:apier-no-auth-gateway-api
  name: Apier.no Auth Gateway API
  description: 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 call; the paths stay published (append-only contract).
    Apier reads no Altinn Autorisasjon data and brokers no government access. The approval-token mint stays callable but has
    no consumer of its tokens while the MVA line is parked (D63).
  humanURL: https://www.apier.no/docs/api
  baseURL: https://www.apier.no
  tags:
  - Auth Gateway
  properties:
  - type: OpenAPI
    url: openapi/apier-no-auth-gateway-api-openapi.yml
  - type: JSONSchema
    url: json-schema/apier-no-trust-metadata-schema.json
- aid: apier-no:apier-no-brreg-api
  name: Apier.no Brreg API
  description: Brønnøysund Enhetsregisteret context surface — agent-shaped company profile reads. NLOD-licensed public data;
    role codes only, never personal identifiers (two-layer defense).
  humanURL: https://www.apier.no/docs/api
  baseURL: https://www.apier.no
  tags:
  - Brreg
  properties:
  - type: OpenAPI
    url: openapi/apier-no-brreg-api-openapi.yml
  - type: JSONSchema
    url: json-schema/apier-no-trust-metadata-schema.json
- aid: apier-no:apier-no-changes-api
  name: Apier.no Changes API
  description: 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ør). Each row's derived observation_kind separates first-time
    archive sightings from real observed changes; queries without entity_id return non-personal rows only. Category B (read:changes
    scope, per-tier rate limit). Cursor-paginated for stable iteration over a moving stream.
  humanURL: https://www.apier.no/docs/api
  baseURL: https://www.apier.no
  tags:
  - Changes
  properties:
  - type: OpenAPI
    url: openapi/apier-no-changes-api-openapi.yml
  - type: JSONSchema
    url: json-schema/apier-no-trust-metadata-schema.json
- aid: apier-no:apier-no-company-api
  name: Apier.no Company API
  description: Reads over the Registry Engine's two-tier company model (Tier 1 public Brønnøysund data + Tier 2 gated commercial
    metrics).
  humanURL: https://www.apier.no/docs/api
  baseURL: https://www.apier.no
  tags:
  - Company
  properties:
  - type: OpenAPI
    url: openapi/apier-no-company-api-openapi.yml
  - type: JSONSchema
    url: json-schema/apier-no-company-context-schema.json
  - type: JSONSchema
    url: json-schema/apier-no-trust-metadata-schema.json
  - type: JSONSchema
    url: json-schema/apier-no-company-verification-schema.json
- aid: apier-no:apier-no-discovery-api
  name: Apier.no Discovery API
  description: 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.
  humanURL: https://www.apier.no/docs/api
  baseURL: https://www.apier.no
  tags:
  - Discovery
  properties:
  - type: OpenAPI
    url: openapi/apier-no-discovery-api-openapi.yml
  - type: JSONSchema
    url: json-schema/apier-no-trust-metadata-schema.json
  - type: JSONSchema
    url: json-schema/apier-no-error-code-schema.json
- aid: apier-no:apier-no-fullmakt-api
  name: Apier.no Fullmakt API
  description: Withdrawn (2026-10-21). The fullmakt line (agent principals, brokered Altinn systembruker delegations, their
    receipts and revocation) answers HTTP 410 `CAPABILITY_WITHDRAWN` on every call; the paths and the receipt schemas stay
    published (append-only contract). Brønnøysund's Fullmakttjenesten (signaturrett and prokura, `GET /api/v1/company/{org}/authority`)
    is Brønnøysund data under NLOD and is unaffected.
  humanURL: https://www.apier.no/docs/api
  baseURL: https://www.apier.no
  tags:
  - Fullmakt
  properties:
  - type: OpenAPI
    url: openapi/apier-no-fullmakt-api-openapi.yml
  - type: JSONSchema
    url: json-schema/apier-no-trust-metadata-schema.json
- aid: apier-no:apier-no-infrastructure-api
  name: Apier.no Infrastructure API
  description: Non-product endpoints (health checks, discovery).
  humanURL: https://www.apier.no/docs/api
  baseURL: https://www.apier.no
  tags:
  - Infrastructure
  properties:
  - type: OpenAPI
    url: openapi/apier-no-infrastructure-api-openapi.yml
- aid: apier-no:apier-no-knowledge-api
  name: Apier.no Knowledge API
  description: The Knowledge Catalog — canonical, machine-readable topic records answering what an agent needs to KNOW about
    Norwegian company authority and government-integration subjects (Altinn System Users, Maskinporten, company verification,
    signature rights, filing deadlines) before it acts. Zero-auth discovery surface outside /api/v1/; content is consolidated
    from Apier's docs guides and cross-references capabilities, MCP tools, and sibling topics strictly by id.
  humanURL: https://www.apier.no/docs/api
  baseURL: https://www.apier.no
  tags:
  - Knowledge
  properties:
  - type: OpenAPI
    url: openapi/apier-no-knowledge-api-openapi.yml
  - type: JSONSchema
    url: json-schema/apier-no-trust-metadata-schema.json
- aid: apier-no:apier-no-privacy-api
  name: Apier.no Privacy API
  description: 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 name-enumeration bulk-export vector.
  humanURL: https://www.apier.no/docs/api
  baseURL: https://www.apier.no
  tags:
  - Privacy
  properties:
  - type: OpenAPI
    url: openapi/apier-no-privacy-api-openapi.yml
  - type: JSONSchema
    url: json-schema/apier-no-trust-metadata-schema.json
- aid: apier-no:apier-no-public-api
  name: Apier.no Public API
  description: 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 baseline regulatory questions without credentials.
  humanURL: https://www.apier.no/docs/api
  baseURL: https://www.apier.no
  tags:
  - Public
  properties:
  - type: OpenAPI
    url: openapi/apier-no-public-api-openapi.yml
  - type: JSONSchema
    url: json-schema/apier-no-trust-metadata-schema.json
- aid: apier-no:apier-no-sandbox-api
  name: Apier.no Sandbox API
  description: 'Zero-auth, deterministic, CORS-open mirrors of every Category B company endpoint. Returns synthetic Norwegian
    company fixtures so agents can test failure-flows without provisioning an Apier API key, without hitting Altinn test infra,
    and without polluting production audit / provenance chains. `security: []` on every operation overrides any global Bearer
    requirement. Reserved test orgs (999000001-005), reserved error orgs (999000901-904), and `?simulate_error=<code>` are
    documented on `/api/v1/capabilities`. Determinism contract: same input → byte-equivalent response, EXCLUDING `_meta.response_timestamp`.'
  humanURL: https://www.apier.no/docs/api
  baseURL: https://www.apier.no
  tags:
  - Sandbox
  properties:
  - type: OpenAPI
    url: openapi/apier-no-sandbox-api-openapi.yml
  - type: JSONSchema
    url: json-schema/apier-no-trust-metadata-schema.json
  - type: JSONSchema
    url: json-schema/apier-no-company-verification-schema.json
  - type: JSONSchema
    url: json-schema/apier-no-sandbox-meta-schema.json
  - type: JSONSchema
    url: json-schema/apier-no-signed-receipt-schema.json
- aid: apier-no:apier-no-subscriptions-api
  name: Apier.no Subscriptions API
  description: Pro-tier change-detection webhook subscriptions. Consumers register a webhook URL + filter; Apier fires HMAC-SHA256-signed
    deliveries when matching change-archive events appear. SSRF-resistant (private CIDRs incl. RFC 6598 CGNAT, .local / .internal
    suffixes, 169.254.x.x metadata endpoints, IPv4-mapped IPv6, trailing-dot FQDN spellings — all blocked at create AND delivery
    time); the TCP connection pins the validator-approved IP so a hostile DNS server can't substitute a private address between
    validate and connect; 7-attempt exponential backoff (initial + retries at 1m / 5m / 15m / 1h / 6h / 24h) before abandonment;
    auto-disables after 6 consecutive 4xx (excluding 408 / 429). Webhook secrets are returned ONCE on creation and stored
    encrypted-at-rest with key-version support.
  humanURL: https://www.apier.no/docs/api
  baseURL: https://www.apier.no
  tags:
  - Subscription
  tags_raw:
  - Subscriptions
  properties:
  - type: OpenAPI
    url: openapi/apier-no-subscriptions-api-openapi.yml
  - type: JSONSchema
    url: json-schema/apier-no-trust-metadata-schema.json
x-enrichment:
  date: '2026-11-01'
  status: enriched
  artifacts_added: 43
  pass: modular-v1
  engine: identity=oss,contract=oss,surfaces=oss,docs=oss,regulatory=oss

Apier.no — frequently asked questions

Does Apier.no have an API?

Yes. APIs.io lists 16 APIs from Apier.no, including Apier.no Account API, Apier.no Actions API and Apier.no Admin API, and 13 more.

Is there an OpenAPI specification for the Apier.no?

Yes. APIs.io indexes 16 OpenAPI specifications for Apier.no, each linked for download from this page.

How do I authenticate with the Apier.no?

Apier.no documents its authentication (5 schemes). The details are profiled on APIs.io as Apier.no Authentication.

How much does the Apier.no cost?

Apier.no publishes its prices; its Pay-as-you-go plan is 50 øre per metered company read as of 2026-11-01. APIs.io lists 1 pricing plan for Apier.no, with each plan's price, limits and inclusions under Pricing on this page.

Does Apier.no have an MCP server?

Yes. APIs.io lists 1 MCP server for Apier.no: Remote MCP server at www.apier.no.

Is the Apier.no ready for AI agents?

Apier.no has a Kin Score of 72.7 out of 100 (exemplar) and an Agent Readiness score of 66.2 (agent-native), scored by API Evangelist on 2026-11-21.

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this
  • find_providersBrowse and filter every provider in the catalog.
  • get_provider_artifactsEvery artifact this provider publishes, grouped by type.
  • get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
  • get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
  • get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
  • get_provider_ratingPRO — composite, band, trend and facet scores.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This provider
curl "https://apis.io/api/v1/providers/apier-no"
All providers
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose
curl "https://apis.io/api/v1/providers/apier-no/operations?limit=25"
How their score was established
curl "https://apis.io/api/v1/providers/apier-no/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. By signing up you are subscribing to the APIs.io and API Evangelist newsletters — you can unsubscribe from any issue. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.