Documentation overview
Machine-verifiable Norwegian company authority: status, roles and coded signing authority. Reference for the REST API, the MCP server and the SDKs.
[Cite this as: Apier.no Docs v0.1.0 — last updated 2026-11-17]
Apier.no gives AI agents machine-verifiable Norwegian company authority, read from Brønnøysund Enhetsregisteret and the public registers around it. It answers three questions that otherwise require weeks of integration work:
- Authorization: the register's coded signing rules for the company (signaturrett and prokura from Brønnøysund)
- Obligations: which regulatory filings apply, with what deadlines?
- Provenance: where did each answer come from, and when was it read? Apier does not submit filings to government.
Your first call
No signup and no API key. This keyless call reads the synthetic sandbox
company 999999999 from the public sandbox mirror, in the same shape as
production plus _meta.is_sandbox: true:
curl "https://www.apier.no/api/v1/sandbox/public/company/999999999/summary"With an API key, the same read runs against the live register. Put the
company's 9-digit organisation number in place of 999999999:
curl -H "Authorization: Bearer <YOUR_API_KEY>" \
"https://www.apier.no/api/v1/company/999999999/summary"An MCP client that speaks streamable HTTP connects to the hosted server.
The handshake and tools/list are keyless; the header is needed once
you call a protected tool:
{
"mcpServers": {
"apier": {
"type": "http",
"url": "https://www.apier.no/api/mcp",
"headers": { "Authorization": "Bearer <YOUR_API_KEY>" }
}
}
}A client set up through a local stdio config, such as Claude Desktop's
claude_desktop_config.json, launches the @apier-no/mcp package
instead; see MCP server.
Keyless means no API key and no Authorization header. The one
keyless MCP tool that writes, redeem_issuance_token, still needs the
one-time issuance token it redeems.
Read, computed, never
- Read: register facts, as Brønnøysund and the other public registers publish them, with their source and retrieval time.
- Computed: deadlines and obligations, from the versioned Universal Rulebook.
- Never: compliance or legal verdicts, legal advice, identity checks or filings.
Four terms
- Signaturrett: the company's registered signing rules, as Brønnøysund records them. Apier returns them uninterpreted.
- Prokura: a power of procuration the company has registered in Brønnøysund, returned beside signaturrett.
- Category A / B: Category A endpoints need no API key (public
obligations, public deadlines, discovery); Category B endpoints, such
as
/api/v1/company/{org}/*, need one. - Universal Rulebook: Apier's versioned store of Norwegian regulatory rules, each with its legal reference. The same input and rulebook version give the same output.
Every response is deterministic, versioned against a Universal Rulebook,
and carries a _meta block so agents can reason about data freshness.
Base URL
https://www.apier.no/api/v1Start here
Quick start
Five-minute walkthrough: call a zero-auth endpoint, read the response envelope, and inspect _meta provenance, with no key required.
Endpoint reference
Per-endpoint reference grouped by capability. The machine-readable contract at /openapi.json is the single source of truth.
Sandbox
Hit the live public endpoints without an API key.
Examples
Golden-path agent workflows cross-checked against the capabilities manifest.
Agent payments
The prepaid-credit loop an autonomous agent has to survive: price discovery, the 402 recovery contract, top-ups, and what changes when a subscription lapses.
Authentication
Every request to Category B endpoints carries an API key in the
Authorization: Bearer <YOUR_API_KEY> header. Keys are stored as
SHA-256 hashes and scoped per API key, with rate limits per level.
Category A endpoints (discovery, public obligations, public
deadlines) require no auth at all; they exist for agent
build-vs-buy decision loops. See
Authentication for the full model.