Case study · 2026-11-05
Claude checks a listed Norwegian company through apier.no
On 2026-11-05 Claude received one fixed prompt about Telenor ASA. It used apier.no to confirm that the company is active, to quote the registered signing rule as the register states it, and to fetch a signed evidence pack. Every statement on this page can be checked from public links, without trusting Apier.
Result
All three tasks passed. Claude made 3 tool calls. The total cost was NOK 1.50.
Before you repeat this
Claude needs the apier.no connector and a small credit balance before it can run this prompt. The setup guide lists each step: Connect apier.no to Claude.
The three tasks
| Task | Result | What Claude reported |
|---|---|---|
| 1. Verify that the company is registered and active | Passed | Active in Enhetsregisteret. Not bankrupt and not under dissolution. VAT registered. Annual accounts filed, latest year 2025. |
| 2. Fetch the signing rule as the register states it, not as a yes or no | Passed | Claude quoted the register wording and gave no verdict on who may sign. |
| 3. Fetch a signed evidence pack and explain how a third party can verify it | Passed | The pack is signed and logged in the public receipt log. |
Run sheet
| Item | Value |
|---|---|
| Date and time | 2026-11-05, 18:11 (Europe/Oslo) |
| AI product and model | Claude, Sonnet 5.5 (Medium), free plan |
| Client | claude.ai in the browser, with a custom connector to https://www.apier.no/api/mcp added through the standard sign-in flow. See the Connect apier.no to Claude. |
| Company | Telenor ASA, org number 982 463 718 |
| Prompt, verbatim | Using apier.no, for the Norwegian company with org number 982463718: 1. Verify that the company is registered and active. 2. Fetch the registered signing rule (signaturrett and prokura) and report it exactly as the register states it, not as a yes or no answer. 3. Fetch a signed evidence pack for the company and explain how a third party can verify it themselves. Say clearly what you could not do. |
| Tool calls | 3 |
| Cost | NOK 1.50 from a separate test wallet |
| Help given | The apier.no connector was installed in Claude before the run. Beyond that, Claude received the prompt and nothing else. This run tests the three tasks, not whether Claude can find apier.no on its own. |
| Anything that went wrong | Nothing failed in this run. See “What Claude could not do” below. |
The signing rule as the register states it
Apier classifies the rule as joint signing. Apier does not decide who may sign.
- Signaturrett:
- «Styret i fellesskap»
- Prokura:
- «Prokura», «Prokura i fellesskap», «Daglig leder alene»
The names of the people who hold these roles are public register entries. This page does not repeat them. They appear in the shared conversation and in the evidence pack file, as they do in the register.
What Claude could not do
Claude listed these limits itself. They are published here on purpose.
- It did not check the signature or the inclusion proofs itself, because its sandbox has no network access.
- It could not confirm any history before 2026-08-03. The Apier archive starts on 2026-07-30 and first saw this company on 2026-08-03.
- It could not say from the pack alone where the daily anchor root is published.
- It did not say who can sign. The pack is a record of what Apier observed, not a verdict.
- It said that a contract decision should rely on a company certificate from Brønnøysundregistrene or on legal advice.
How to verify this yourself
- Read the conversation. The shared chat is at https://claude.ai/share/ec3cb4ec-fcb1-47fb-8b27-0e5e679ac619. It contains the prompt, the answer and the tool calls, and nothing else from the account. Readers cannot edit it.
- Download the evidence pack: evidence-pack.json. The file is 12,542 bytes, with SHA-256
771f28d390116e9f354681b7a77925a989bab193fece7e15b5f38634bad7db0c. Compare the size and the hash to confirm that you hold the same file. - Check the signature. Open the file in the /evidence-pack/viewer. It checks the signature and the inclusion proofs in your browser and needs no key. The signing key id is
23ea57b8-e354-4de7-b346-373f2b0709d9and the key is published at /.well-known/jwks.json. - Find the receipt. The pack is entry 3 in the public receipt log, logged 2026-11-05 at 18:11 Oslo time, with entry hash
cd647de1e17f7e9dfa8103260edf7c11e55a97739cf853ec5199ab49eacb21ca. Look it up at https://www.apier.no/api/v1/public/receipt-log?entry_hash=cd647de1e17f7e9dfa8103260edf7c11e55a97739cf853ec5199ab49eacb21ca. - Check the anchor root for 2026-11-05:
921871d6ddedca7285bc14fc032d762e0d17ed9edb0c614d34627d6fda2b1286. It covers 419 leaves with the algorithm sha256-rfc6962 and carries an RFC 3161 timestamp from freetsa, obtained 2026-11-06 at 02:30 UTC. It is listed at /api/v1/public/anchors. - Compare with the source. The record Brønnøysundregistrene holds for the company is at https://data.brreg.no/enhetsregisteret/api/enheter/982463718.
The same facts, for every published run, are served as JSON at /api/v1/public/case-studies (Machine-readable list of all runs).