Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Aksjonær i virksomhet API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fswaggerhub.skatteetaten%2Faksjonr-i-virksomhet-api" | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fswaggerhub.skatteetaten%2Faksjonr-i-virksomhet-api" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
What an agent can do with Aksjonær i virksomhet API.
Hent aksjonærer i en virksomhet
Manage developer tools data programmatically
Integrate Aksjonær i virksomhet API into automated workflows
Query and filter Aksjonær i virksomhet API records by parameters
Monitor Aksjonær i virksomhet API operational status and events
GET STARTED
Patterns agents use Aksjonær i virksomhet API for, with concrete tasks.
★ Developer Tools Operations
Use the Aksjonær i virksomhet API to perform developer tools operations programmatically. The API provides 1 endpoints covering core functionality including hent aksjonærer i en virksomhet.
Call GET /{rettighetspakke}/aksjonaerer/{organisasjonsnummer} to hent aksjonærer i en virksomhet
Data Retrieval and Monitoring
Query Aksjonær i virksomhet API resources on a schedule to track changes, generate alerts, or feed downstream dashboards. Agents poll relevant endpoints, compare against previous state, and trigger actions when thresholds are crossed.
Poll the primary Aksjonær i virksomhet API endpoint, compare response to last known state, and alert if changed
AI Agent Integration via Jentic
AI agents discover and call Aksjonær i virksomhet API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle bearer tokens manually.
Search Jentic for 'hent aksjonærer i en virksomhet', load the operation schema, and execute with Jentic-managed credentials
1 endpoints — tjenesten leverer informasjon om en virksomhets aksjonærer pr.
METHOD
PATH
DESCRIPTION
/{rettighetspakke}/aksjonaerer/{organisasjonsnummer}
Hent aksjonærer i en virksomhet
/{rettighetspakke}/aksjonaerer/{organisasjonsnummer}
Hent aksjonærer i en virksomhet
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Aksjonaer i virksomhet API by hand means implementing Maskinporten JWT bearer auth, choosing between the skatteetaten-test.no and production skatteetaten.no hosts, and writing your own retry handling. Through Jentic you install once, import Aksjonaer i virksomhet API from the API Directory, store the token once, and your agent calls it.
Permission scoping
This API puts the organisation number in the URL path (/{rettighetspakke}/aksjonaerer/{organisasjonsnummer}), so a rule can pin your agent to one organisation: it can read shareholders for that organisation and nothing else. You choose the operations it may call, so a lookup for a different organisation is not included unless you add it.
Credential isolation
Your Aksjonaer i virksomhet API token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'hent aksjonaerer i en virksomhet' or 'list shareholders of an organisation', and Jentic returns the matching Aksjonaer i virksomhet API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Alternatives and complements available in the Jentic catalogue.
Github
Alternative developer tools API
Choose Github when you need a different approach to developer tools operations
Specific to using Aksjonær i virksomhet API through Jentic.
What authentication does the Aksjonær i virksomhet API use?
The Aksjonær i virksomhet API uses a Bearer token in the Authorization header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.
Can I hent aksjonærer i en virksomhet with the Aksjonær i virksomhet API?
Yes. Use the GET /{rettighetspakke}/aksjonaerer/{organisasjonsnummer} endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Aksjonær i virksomhet API?
Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.
How do I hent aksjonærer i en virksomhet through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'hent aksjonærer i en virksomhet'. Jentic returns the matching Aksjonær i virksomhet API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Aksjonær i virksomhet API have?
The Aksjonær i virksomhet API exposes 1 endpoints covering aksjonaerer operations.
Can I limit what my agent is allowed to do with the Aksjonær i virksomhet API?
Yes. Because you run Jentic One yourself, your own rules decide which operations and credentials your agent may use. This API takes the organisation number in the URL path (GET /{rettighetspakke}/aksjonaerer/{organisasjonsnummer}), so you can pin the agent to a single organisation and let it read shareholders only for that one. Since you choose the operations it may call, a lookup for any other organisation is not available to the agent unless you add it.
Know of an official OpenAPI document? Contribute it →
For Agents
Programmatically hent aksjonærer i en virksomhet. Covers 1 operations with bearer authentication.
Use for: I need to hent aksjonærer i en virksomhet, Find available developer tools operations, Get the current status of Aksjonær i virksomhet API resources, List all records from Aksjonær i virksomhet API
Not supported: Does not handle payments, communications, or crm - use for developer tools only.
Tjenesten leverer informasjon om en virksomhets aksjonærer pr. 31.12 sist kalenderår. The API exposes 1 endpoints secured with bearer authentication.