Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Aksjebeholdning 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%2Faksjebeholdning-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%2Faksjebeholdning-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 Aksjebeholdning API.
Hent aksjebeholdning for en virksomhet
Manage developer tools data programmatically
Integrate Aksjebeholdning API into automated workflows
Query and filter Aksjebeholdning API records by parameters
Monitor Aksjebeholdning API operational status and events
GET STARTED
Patterns agents use Aksjebeholdning API for, with concrete tasks.
★ Developer Tools Operations
Use the Aksjebeholdning API to perform developer tools operations programmatically. The API provides 2 endpoints covering core functionality including hent aksjebeholdning for en virksomhet, hent aksjebeholdning for en person.
Call GET /virksomhet/{rettighetspakke}/{kalenderaar}/{organisasjonsnummer} to hent aksjebeholdning for en virksomhet
Data Retrieval and Monitoring
Query Aksjebeholdning 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 Aksjebeholdning API endpoint, compare response to last known state, and alert if changed
AI Agent Integration via Jentic
AI agents discover and call Aksjebeholdning 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 aksjebeholdning for en virksomhet', load the operation schema, and execute with Jentic-managed credentials
2 endpoints — tjenesten leverer informasjon en person eller en virksomhet sin aksjebeholdning pr.
METHOD
PATH
DESCRIPTION
/virksomhet/{rettighetspakke}/{kalenderaar}/{organisasjonsnummer}
Hent aksjebeholdning for en virksomhet
/person/{rettighetspakke}/{kalenderaar}/{personidentifikator}
Hent aksjebeholdning for en person
/virksomhet/{rettighetspakke}/{kalenderaar}/{organisasjonsnummer}
Hent aksjebeholdning for en virksomhet
/person/{rettighetspakke}/{kalenderaar}/{personidentifikator}
Hent aksjebeholdning for en person
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Aksjebeholdning 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 Aksjebeholdning API from the API Directory, store the token once, and your agent calls it.
Permission scoping
This API puts the organisation number or person identifier in the URL path (/virksomhet/{rettighetspakke}/{kalenderaar}/{organisasjonsnummer}, /person/.../{personidentifikator}), so a rule can pin your agent to reads for one subject: it can fetch share holdings for that organisation or person and nothing else. You choose the operations it may call, so a lookup for a different subject is not included unless you add it.
Credential isolation
Your Aksjebeholdning 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 aksjebeholdning for en virksomhet' or 'read share holdings for a person', and Jentic returns the matching Aksjebeholdning 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 Aksjebeholdning API through Jentic.
What authentication does the Aksjebeholdning API use?
The Aksjebeholdning 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 aksjebeholdning for en virksomhet with the Aksjebeholdning API?
Yes. Use the GET /virksomhet/{rettighetspakke}/{kalenderaar}/{organisasjonsnummer} endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Aksjebeholdning 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 aksjebeholdning for 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 aksjebeholdning for en virksomhet'. Jentic returns the matching Aksjebeholdning API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Aksjebeholdning API have?
The Aksjebeholdning API exposes 2 endpoints covering person, virksomhet operations.
Can I limit what my agent is allowed to do with the Aksjebeholdning API?
Yes. Because you run Jentic One yourself, your own rules decide which operations and credentials the agent may use, and you pick from just the two read calls this API offers: GET /virksomhet/{rettighetspakke}/{kalenderaar}/{organisasjonsnummer} and GET /person/{rettighetspakke}/{kalenderaar}/{personidentifikator}. Since the organisation number or person identifier sits in the URL path, a rule can pin the agent to reading share holdings for one subject and nothing else. A lookup for a different organisation or person is not included unless you add it.
Know of an official OpenAPI document? Contribute it →
For Agents
Programmatically hent aksjebeholdning for en virksomhet, hent aksjebeholdning for en person. Covers 2 operations with bearer authentication.
Use for: I need to hent aksjebeholdning for en virksomhet, I want to hent aksjebeholdning for en person, Get the current status of Aksjebeholdning API resources, List all records from Aksjebeholdning API
Not supported: Does not handle payments, communications, or crm - use for developer tools only.
Tjenesten leverer informasjon en person eller en virksomhet sin aksjebeholdning pr. 31.12 sist kalenderår. The API exposes 2 endpoints secured with bearer authentication.