Veldora › Datasets › Norwegian companies

Norwegian company data from Enhetsregisteret

Q: Can my agent use this over MCP?

Yes. Connect to https://veldora.no/mcp and call get_company or search_companies. Listing the tools is free; each call is paid at the same price as the REST route.

Look up a Norwegian company by organisation number (orgnr), or search the register by name, municipality, industry, legal form and status. The data is the official Enhetsregisteret from Brønnøysundregistrene (Brreg), cleaned into one stable JSON shape for AI agents.

What you get
Example
Price
Questions

What you get

orgnr, name and org_form (code and description, for example ASA).
status: active, bankrupt, winding_up, forced_dissolution or deleted, with the bankruptcy, winding-up and deletion dates.
founded, registered_date, vat_registered and in_business_register.
industry (NACE code and description), employees and sector_code.
address and postal_address, with municipality and municipality number, plus website, parent_orgnr and last_annual_accounts_year.
A link to the company on Brønnøysundregistrene.
Search by q, municipality, nace, org_form and status, 100 results per page at most.

No person data: no board members, managers or owners, and no phone or e-mail. Sole proprietorships (ENK) are named after a person, so they come without name or street address and are left out of name search.

Source: Brønnøysundregistrene. Licence: NLOD 2.0.

Example

Look up one company by organisation number:

curl https://veldora.no/v1/companies/923609016

{
  "data": {
    "orgnr": "923609016",
    "name": "EQUINOR ASA",
    "org_form": { "code": "ASA", "description": "Allmennaksjeselskap" },
    "status": "active",
    "bankrupt": false,
    "founded": "1972-09-18",
    "vat_registered": true,
    "industry": [{ "code": "06.100", "description": "Utvinning av råolje" }],
    "employees": 4000,
    "address": { "street": "Forusbeen 50", "postal_code": "4035", "city": "STAVANGER", "municipality_number": "1103" },
    "website": "www.equinor.com",
    "links": { "brreg": "https://virksomhet.brreg.no/nb/oppslag/enheter/923609016" }
  },
  "meta": { "source": "brreg", "fetched_at": "2026-10-12T08:15:00Z", "stale": false, "license": "NLOD-2.0", "attribution": "..." }
}

Without payment this returns 402 with the price. With an x402 client such as @x402/fetch the same request returns the JSON above, trimmed here. The values are an illustration of the shape.

Price and MCP tools

Endpoint	What it does	MCP tool	Price
`GET /v1/companies/{orgnr}`	Look up a company	`get_company`	$0.005
`GET /v1/companies`	Search companies	`search_companies`	$0.01

Per successful call, in USD, paid as USDC on Base. The MCP server is at https://veldora.no/mcp.

How payment works

Your agent sends a normal HTTP request and gets 402 Payment Required with the price. It signs a USDC authorization on Base for that amount and repeats the request, and Veldora returns the data with a receipt. There is no account or API key, and failed calls are not charged. See Pay per call and the payment section of the docs.

Questions

What is the licence of the company data?

The data is under the Norwegian licence for Open Government data (NLOD 2.0), distributed by Brønnøysundregistrene. Every response repeats the notice in meta.attribution; pass it on when you republish the data.

How fresh is the data?

Companies are read live from Brønnøysundregistrene on each call. If the register is down, Veldora answers from an offline mirror and flags it with meta.stale: true and the X-Data-Stale header.

What happens if a call fails?

You are not charged for any response with status 400 or higher. A malformed organisation number is rejected with 400 before payment is asked for, and a retry with the same payment costs nothing extra.

Do I need an API key or an account?

No. Your agent pays for each call in USDC on Base with the x402 protocol. The payment is the credential.

Can my agent use this over MCP?

Yes. Connect to https://veldora.no/mcp and call get_company or search_companies. Listing the tools is free; each call is paid at the same price as the REST route.