Skip to content

Evidence pack: a signed record of what Apier observed about a Norwegian company

An evidence pack is one signed JSON file about one Norwegian company at one date. It holds the register facts Apier read, where each came from and when, every archived change in the window, the daily anchor proof for each archived record, and the coverage of the archive.

It is a record of what Apier observed. It is not a verdict on whether anyone may act, sign or is compliant, and Apier makes no claim that it is admissible in court. What it gives you is a file you can keep, hand to someone else, and check without trusting Apier's servers on the day you check it.

What a pack contains

The pack is a verification certificate whose result is the evidence pack. The names below are the fields as a real pack carries them, read from the pack the Claude run on Telenor ASA fetched.

ItemField in the packWhat it holds
Organisation numberresult.org_numberThe nine digit organisasjonsnummer the pack is about.
Identity and status in the registerresult.checks.checks, check, valueOne entry per check. registration_status holds the company's status as the register records it, bankruptcy_liquidation whether a bankruptcy or liquidation is registered, and vat_registration, roles, annual_accounts_filed and lei_status the other facts.
Status of each checkcheck_statusOne of verified, missing, stale, unavailable or not_checked. unavailable means the source could not be read, never that the check failed. There is no overall status and no summary field.
Signing wordingcoded_signing_authorityThe register's coded signing rules for the company, as the coded_signing_authority check: value.signatur_state for signaturrett and value.prokura_state for prokura. Reported as the register holds them, never as a yes or no answer.
Source referencessource, source_url, licence, result.attributionEach check names its source, the URL it was read from and the licence it is used under. attribution lists the licence and attribution sentence of every source in the pack.
Source observation timeretrieved_at, first_observed_at, detected_atWhen Apier read each check's fact (retrieved_at), when Apier first observed each archived record (first_observed_at) and when each change was detected (detected_at).
Generation timeissued_atWhen Apier built and signed the pack, with the Europe/Oslo offset. The pack has no separate processing time field; issued_at is the time the pack was produced.
Schema and rule versionsresult.pack_version, rulebook_versionpack_version is evidence-pack-v1; a new shape gets a new version. rulebook_version is the version of the rules Apier applied.
FreshnessfreshnessPer check: served_from (where the fact was read), max_age_days (Apier's freshness guidance for the source, or null) and stale (true when the fact is older than that).
Changes in the windowresult.changes, result.changes_fromEvery archived change event from changes_from to as_of, with its before and after value, effective date and observed date. truncated says when a list was longer than the pack carries.
Your own receiptsresult.receiptsThe caller's own receipts for the company: a reference and the SHA-256 of each receipt's signature, never the government response.
Archived records and anchor proofsresult.archived_records, anchor_status, merkle_root, leaf_index, proofEach archived snapshot record with its daily anchor: anchored records carry the day's Merkle root and an RFC 6962 inclusion proof. pending records are newer than the last anchor and carry no proof, never an invented one.
Coverageresult.coveragearchive_start, entity_first_observed, covered_from, requested_from, before_coverage and a plain note saying what the window covers.
Signaturesignature, kid, jwks_uri, issuerA detached JWS over the rest of the pack, signed RS256 (EdDSA for a sandbox pack). kid names the signing key. jwks_uri says where the issuer publishes its keys and is informational: check against a key set you configured yourself.
Verification instructionsresult.statement, public_logstatement says what the pack is and is not. Outside the signed pack, public_log gives the pack's entry in the public receipt log: entry_hash (the SHA-256 of the signature) and its sequence number seq. The steps below are the instructions.

Check a pack offline, without an Apier account

You need the pack file and Apier's public key set. Neither the signature check nor the anchor check needs an API key, and neither sends anything about the pack to Apier. The last step, the receipt log lookup, is optional and online: it sends the pack's public_log.entry_hash, the SHA-256 of its signature, to Apier, never the pack's content.

  1. Save the pack. Save the pack object of the response as a .json file. That object is the whole signed pack. public_log sits beside pack in the response, outside the signed pack, so keep the whole response as well, or note public_log.entry_hash, before you keep pack alone: the receipt log step needs it.
  2. Open it in the viewer, or check it yourself. The viewer at /evidence-pack/viewer opens the file on your own device, checks the signature and the anchor proofs in the browser, and prints the pack. Nothing is uploaded.
  3. Check the signature. Remove signature, serialise the rest as canonical JSON (keys sorted at every level), and check the detached JWS against the key whose kid the pack names, in a key set you configured yourself: /.well-known/jwks.json for a live pack. Never fetch keys from the pack's own jwks_uri: that field is informational, and whoever made the file controls it. A sandbox pack is signed with the public sandbox key (/.well-known/sandbox-jwks.json), which anyone can sign with, so it proves nothing and is only for rehearsing the check. Save the key set once and the check runs with no network at all. Retired keys stay in the set, so an old pack still verifies.
  4. Check each anchor proof. For a record with anchor_status anchored, rebuild the leaf from content_hash, first_observed_at and org_number, walk the proof path to a root, and compare it with merkle_root. Then compare merkle_root with the root Apier published for anchor_date.
  5. Find the pack in the public receipt log. Optional, and online: look up public_log.entry_hash in the public receipt log. The lookup sends that hash to Apier, never the pack's content. The log holds hashes only, never the pack's content or the organisation number.
    curl "https://www.apier.no/api/v1/public/receipt-log?entry_hash=<public_log.entry_hash>"

Fact versus receipt

A pack carries both, and they answer different questions. The fact is what the register holds. The receipt is Apier's signed record that it read that fact.

FactReceipt
What it isA value in a register, for example the company's status or its coded signing rules.A signed record that Apier read that value from that source at that time.
Where it livesIn the source register. It can change tomorrow.In your file. It does not change; a changed file no longer verifies.
How you check itAsk the register again, at its source_url.Check the signature and the anchor proofs, as above, without asking Apier.
What it does not sayWhether the value was the same at another time.Whether anyone may act, sign or is compliant. It records an observation, not a decision.

Copy a daily anchor root to your own log

Every UTC day Apier commits the records it first observed that day to one Merkle root and publishes it. A copy of that root kept somewhere Apier does not control lets you hold Apier to it later.

  1. Fetch the newest root. The anchors route is public and needs no key. Each entry has anchor_date, merkle_root, leaf_count and algorithm.
    curl "https://www.apier.no/api/v1/public/anchors?limit=1"
  2. Copy it to a log you control. Write anchor_date and merkle_root with the time you copied them into a place with its own history: a commit in your own repository, a ticket, an email to yourself or a printed page.
  3. Compare later. Any archived record a pack shows for that day must prove its way to that root. A different root for the same day, served later, would show the archive changed after you copied it.

Timestamps

Each daily anchor root is sent to two independent timestamp authorities for an RFC 3161 timestamp: FreeTSA and Sectigo's public timestamp service. The anchors route lists each token's provider and the time it was obtained in tsa_tokens; the token bytes themselves are not served there.

Neither timestamp is a qualified electronic time stamp under eIDAS. FreeTSA is not on an EU trusted list, and the Sectigo service Apier calls is a different service from the one Sectigo has on a trusted list (Apier's research note of 2026-11-10). The timestamps show that a root existed at a time; this page claims nothing about their legal effect.

What the archive covers

Apier's archive starts on 2026-07-30. A pack holds what Apier observed from then on, and for each company from the day Apier first observed it (coverage.entity_first_observed).

These are observations at the times shown, not a continuous record of the company's legal state between them. A pack asked for an earlier window answers as asked and says so in coverage.before_coverage and coverage.note.

Get a pack

Call the REST route with a key that has the read:brreg scope, or the MCP tool get_company_evidence_pack. The call is billed as one company read; prices are on /pricing. changes_from sets the start of the change window, at most 366 days back.

The sandbox serves packs for fixture companies, signed with the public sandbox key at /.well-known/sandbox-jwks.json, so you can try the viewer and the signature check above before you pay for anything. Sandbox packs hold no archived records and are never written to the receipt log, so the anchor and receipt log checks have nothing to check on them.

curl -H "Authorization: Bearer $APIER_API_KEY" \
  "https://www.apier.no/api/v1/company/999999999/evidence-pack" -o response.json

The statement on every pack

Every pack carries this fixed sentence in statement:

A record of what Apier observed about this company, with the source, retrieval time and licence of each fact. It is not a verdict on whether anyone may act, sign or is compliant, and Apier makes no claim that it is admissible in court.