Skip to content

Case study · 2026-11-14

A scripted agent checks a listed Norwegian company through apier.no

On 2026-11-14 a script with no AI model ran a fixed plan about Telenor ASA. It called apier.no to read whether the company is active, to read 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.

  • Task: Company verification
  • Run type: Scripted agent, no language model
  • Result: Passed
  • Tool calls: 6
  • Cost: NOK 1.50

What this shows

A plain script, with an API key, a fixed plan and no AI model, read that a company is active, read its signing rule word for word without giving a verdict, and fetched a signed record that anyone can check. It made 6 tool calls, 3 of them billed, and the wallet was debited NOK 1.50.

Result

All three steps passed. The script made 6 tool calls: 3 billed company reads and 3 free calls (the price list, and the wallet balance before and after). The total cost was NOK 1.50, measured as the wallet balance before the run minus the balance after it.

Repeat this run yourself

Two routes: make the same three tool calls against the MCP endpoint, or fetch the evidence pack with one call to the REST API. Both need an API key with a small credit balance.

Route 1. The same tool calls, over MCP

The script sent three requests of the kind tools/call to https://www.apier.no/api/mcp. The first one looks like this:

curl -X POST "https://www.apier.no/api/mcp" \
  -H "Authorization: Bearer <YOUR_API_KEY>" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"get_company_verification","arguments":{"org_number":"982463718"}}}'

The other two calls use the tool names get_company_authority and get_company_evidence_pack with the same arguments. A new pack has a new time and a new signature. Compare the structure and the checks, not the hash.

Route 2. One call to the REST API

Fetch a signed evidence pack for Telenor ASA (billed as one company read)

curl -H "Authorization: Bearer <YOUR_API_KEY>" \
  "https://www.apier.no/api/v1/company/982463718/evidence-pack" \
  -o my-evidence-pack.json

Then open my-evidence-pack.json in the evidence pack viewer. It checks the signature in your browser, and the file is not uploaded.

The three steps

The three steps in the plan, the result of each and what the script read.
StepResultWhat the script read
1. Read whether the company is registered and activePassedActive in Enhetsregisteret. Not bankrupt, not under dissolution and not under forced dissolution. VAT registered. Annual accounts filed, latest year 2025.
2. Read the signing rule as the register states it, not as a yes or noPassedThe register wording for signaturrett and prokura, quoted below. The script gave no verdict on who may sign.
3. Fetch a signed evidence packPassedA signed pack with 9 checks: 7 came back with the status verified and 2 with the status missing (requirements_evidence and finanstilsynet_licences). The pack is entry 4 in the public receipt log.

Run sheet

The run in detail: time, run type, client, company, task statement, tool calls, cost and the help the script was given.
ItemValue
Date and time2026-11-14, 13:01 (Europe/Oslo)
Run type and modelScripted agent. No language model took part.
Clienttools/case-study-harness, a TypeScript script that uses Node fetch to send requests to https://www.apier.no/api/mcp with an API key.
CompanyTelenor ASA, org number 982 463 718
Task statement, verbatim
For the Norwegian company with org number 982463718: 1. Read whether the company is registered and active. 2. Read the registered signing rule (signaturrett and prokura) exactly as the register states it, not as a yes or no answer. 3. Fetch a signed evidence pack for the company. Record what could not be done.
Tool calls6: get_pricing, get_credit_balance, get_company_verification, get_company_authority, get_company_evidence_pack, get_credit_balance
CostNOK 1.50 from a separate test wallet: 3 billed calls at NOK 0.50 each. The balance was NOK 50.00 before the run and NOK 48.50 after it.
Help givenThe plan named the three tools and their arguments in advance, so the script discovered nothing by itself. This run tests the three steps, not whether an agent can find apier.no.
Anything that went wrongNothing failed in this run. Every request was sent once. See “What the script 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 and the run transcript do not repeat them. They appear in the evidence pack file, as they do in the register.

What the script could not do

A script states no limits of its own. These are the limits of what this run did, published here on purpose.

  • It did not check the signature or the inclusion proofs of the pack. It checked one thing: that the entry hash in the public receipt log is the SHA-256 of the pack's signature.
  • 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 read the daily anchor root for its own day. That root is cut after the UTC day ends, so it was added to this page the day after the run.
  • It interpreted nothing. It copied the fields its plan named and gave no summary, no explanation and no advice.
  • It did not say who can sign. The pack is a record of what Apier observed, not a verdict.

How to verify this yourself

  1. Read the run transcript: run-transcript.json. It lists every call the script made, with tool name, arguments, HTTP status, time and wallet debit, and what each step read. It holds no personal names. A scripted run has no chat to share, so this file is its record.
  2. Download the evidence pack: evidence-pack.json. The file is 13,428 bytes, with SHA-256 c4f04a2df9df43d6d4500923003ced7eead3ff69111628fa862c042350c85916. Compare the size and the hash to confirm that you hold the same file.

    macOS or Linux

    shasum -a 256 evidence-pack.json

    Windows

    certutil -hashfile evidence-pack.json SHA256
  3. 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-373f2b0709d9 and the key is published at /.well-known/jwks.json.
  4. Find the receipt. The pack is entry 4 in the public receipt log, logged 2026-11-14 at 13:01 Oslo time, with entry hash 4e4f41c699f9b593d9489ee890872159320c88292e2e8ad11c182d8f287893e7. Look it up at https://www.apier.no/api/v1/public/receipt-log?entry_hash=4e4f41c699f9b593d9489ee890872159320c88292e2e8ad11c182d8f287893e7.
  5. Check the anchor root for 2026-11-14: 2150f9a6019e3e611534bcc9cd6014bf6e2348a3bba772afa98c02c951cba48e. It covers 232 leaves with the algorithm sha256-rfc6962 and carries an RFC 3161 timestamp from freetsa, obtained 2026-11-15 at 02:30 UTC. It is listed at /api/v1/public/anchors.
  6. Compare with the source. The record Brønnøysundregistrene holds for the company is at https://data.brreg.no/enhetsregisteret/api/enheter/982463718.

Machine-readable data

AI agents and scripts can read this run without parsing the page. The same facts, for every published run, are served as JSON at /api/v1/public/case-studies (Machine-readable list of all runs). The JSON holds no personal names.

This run, as the endpoint serves it

{
  "company": "Telenor ASA",
  "org_number": "982463718",
  "ai_product": "Scripted agent",
  "model": "no language model",
  "run_date": "2026-11-14",
  "task": "company_verification",
  "task_label": {
    "en": "Company verification",
    "nb": "Selskapsverifisering"
  },
  "result": "passed",
  "cost_nok": "1.50",
  "tool_calls": 6,
  "page_url": {
    "en": "https://www.apier.no/case-studies/scripted-agent-telenor-asa",
    "nb": "https://www.apier.no/no/kasusstudier/skriptbasert-agent-telenor-asa"
  },
  "share_url": "https://www.apier.no/case-studies/scripted-agent-telenor-asa/run-transcript.json",
  "evidence_pack_url": "https://www.apier.no/case-studies/scripted-agent-telenor-asa/evidence-pack.json",
  "evidence_pack_sha256": "c4f04a2df9df43d6d4500923003ced7eead3ff69111628fa862c042350c85916",
  "evidence_pack_bytes": 13428,
  "receipt_log": {
    "seq": 4,
    "entry_hash": "4e4f41c699f9b593d9489ee890872159320c88292e2e8ad11c182d8f287893e7",
    "url": "https://www.apier.no/api/v1/public/receipt-log?entry_hash=4e4f41c699f9b593d9489ee890872159320c88292e2e8ad11c182d8f287893e7"
  },
  "anchor": {
    "date": "2026-11-14",
    "merkle_root": "2150f9a6019e3e611534bcc9cd6014bf6e2348a3bba772afa98c02c951cba48e",
    "url": "https://www.apier.no/api/v1/public/anchors"
  },
  "source_url": "https://data.brreg.no/enhetsregisteret/api/enheter/982463718"
}

The page head carries Schema.org TechArticle and BreadcrumbList data, with no price or rating markup.

Repeat runs of this plan

One run shows that it can work. Later runs of the same plan are published here, including failures. For the health of the government sources behind the data, see source health.

Every row below is a real run. No success rate is shown until there are at least five runs.

Every published run of this plan on this company: date, run type, result and cost.
Run dateRun typeResultCost
2026-11-14Scripted agent, no language modelPassedNOK 1.50

About this page

An evidence pack is a signed record of what Apier observed and when. It is not a verdict on who may sign, and it makes no claim about how a court or a counterparty will treat it.

This was a test run on a separate account and wallet. It is not counted as customer usage.

This run covers the company side of Know Your Business Agent (KYBA).

View the evidence pack file