Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Avregning 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%2Favregning-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%2Favregning-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 Avregning API.
Hent avregning for person
Manage developer tools data programmatically
Integrate Avregning API into automated workflows
Query and filter Avregning API records by parameters
GET STARTED
For Agents
Programmatically hent avregning for person. Covers 1 operations with bearer authentication.
Use for: I need to hent avregning for person, Find available developer tools operations, Get the current status of Avregning API resources, List all records from Avregning API
Not supported: Does not handle payments, communications, or crm - use for developer tools only.
Tjenesten leverer informasjon om forskuddstrekk og restskatt eller beløp til gode i skatteoppgjøret. The API exposes 1 endpoints secured with bearer authentication.
Monitor Avregning API operational status and events
Patterns agents use Avregning API for, with concrete tasks.
★ Developer Tools Operations
Use the Avregning API to perform developer tools operations programmatically. The API provides 1 endpoints covering core functionality including hent avregning for person.
Call GET /{rettighetspakke}/{inntektsaar}/{personidentifikator} to hent avregning for person
Data Retrieval and Monitoring
Query Avregning 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 Avregning API endpoint, compare response to last known state, and alert if changed
AI Agent Integration via Jentic
AI agents discover and call Avregning 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 avregning for person', load the operation schema, and execute with Jentic-managed credentials
1 endpoints — tjenesten leverer informasjon om forskuddstrekk og restskatt eller beløp til gode i skatteoppgjøret.
METHOD
PATH
DESCRIPTION
/{rettighetspakke}/{inntektsaar}/{personidentifikator}
Hent avregning for person
/{rettighetspakke}/{inntektsaar}/{personidentifikator}
Hent avregning for person
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Avregning 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 Avregning API from the API Directory, store the token once, and your agent calls it.
Permission scoping
This API puts the person identifier in the URL path (/{rettighetspakke}/{inntektsaar}/{personidentifikator}), so a rule can pin your agent to one person: it can read the tax settlement for that person and year and nothing else. You choose the operations it may call, so a lookup for a different person is not included unless you add it.
Credential isolation
Your Avregning 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 avregning for person' or 'read a tax settlement for a person and year', and Jentic returns the matching Avregning 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 Avregning API through Jentic.
What authentication does the Avregning API use?
The Avregning 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 avregning for person with the Avregning API?
Yes. Use the GET /{rettighetspakke}/{inntektsaar}/{personidentifikator} endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Avregning 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 avregning for person through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'hent avregning for person'. Jentic returns the matching Avregning API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Avregning API have?
The Avregning API exposes 1 endpoints for developer tools operations.
Can I limit what my agent is allowed to do with the Avregning API?
Yes. Because you run Jentic One yourself, your own rules decide which operations and credentials the agent may use, and the Avregning API exposes a single read operation, GET /{rettighetspakke}/{inntektsaar}/{personidentifikator}. Since the person identifier, rights package, and income year all sit in the URL path, you can pin the agent to reading the tax settlement for one person and year and nothing else. A lookup for a different person is not available to the agent unless you explicitly add it.