Install Jentic One Beta

Connect the Loket.nl API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Loket.nl 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%2Floket.nl%2Floket" | sh

Step 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%2Floket.nl%2Floket" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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.

Capabilities

What an agent can do with Loket.nl API.

Acquire employer and employee directory data including chamber-of-commerce company information and address lookups by postal code

Manage employments, contracts, and wage components per employee with versioned payroll periods

Administer leave policies, leave requests, leave balances, and collective leave events for an employer

Track absences and absence progress including return-to-work milestones and Achmea insurance contracts

GET STARTED

Start building with Loket.nl API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Loket.nl API for, with concrete tasks.

★ Dutch payroll provider onboarding

Partner software that runs payroll for Dutch SMEs uses the Loket.nl API to enrol new employers, sync the employee directory, and post wage components to the correct payroll periods. The API exposes 641 endpoints covering employments, contracts, and statutory reporting, so a partner can replace manual data entry between their HR product and Loket. Most integrations stand up the read flow first, then add write operations once acceptance-environment validation passes.

List employments for employer X, then post a new wage component for employee 12345 in the current payroll period and confirm the entry appears under that employment.

Leave and absence self-service

HR portals built on top of Loket use the leave and absence endpoints to let employees submit leave requests, see their accrued balance, and track open absences. The API distinguishes leave policies, leave balances, leave requests, and collective leave so a portal can render the right view per employer policy. Integration is typically a few days because the leave domain is well-tagged and uses consistent identifiers.

Get the leave balance for employee 12345 as of today, submit a leave request for 3 days next month, and confirm the request status changes to pending.

HR data warehouse extract

Analytics teams use the directory, employment, and payroll endpoints to extract a daily snapshot of headcount, contract types, and payroll movements into a warehouse. Because Loket exposes provider authorisation and application sets, the extract job can run with a scoped partner identity rather than a user session. The volume of endpoints (641) means agents typically iterate by tag rather than path-by-path.

Pull the list of providers and application sets for an employer, then iterate through employees and pull each active employment record into a flat structure.

Agent-driven leave assistant via Jentic

An AI assistant in a workplace chat answers questions like 'how much leave do I have left?' and 'submit a sick day for me' by calling Loket through Jentic. Jentic loads the employee, leave-balance, and leave-request endpoints into the agent's tool list and isolates the OAuth tokens, so the assistant never sees raw credentials. Going from prompt to working assistant takes under an hour with Jentic versus several days handling Loket's OAuth flow directly.

Use Jentic to search 'submit a leave request', load the Loket leave-request operation, and execute it with employee, start date, end date, and leave-type values from the conversation.

Key Endpoints

641 endpoints — loket.

METHOD

PATH

DESCRIPTION

GET

/providers

List partner providers configured for an employer

PUT

/providers/applicationsets/{applicationSetId}

Edit an application set's details

GET

/applications/{applicationId}/authorizations

List authorisations for a partner application

GET

/aowDate

Acquire the Dutch state pension (AOW) date for a person

GET

/chamberofcommerce/{chamberOfCommerceNumber}/companyinformation

Look up company information by KvK number

GET

/locationservices/address

Resolve a postal code and house number to a Dutch address

GET

/achmeainsurancecontracts

List Achmea insurance contracts for an employer

GET

/providers

List partner providers configured for an employer

PUT

/providers/applicationsets/{applicationSetId}

Edit an application set's details

GET

/applications/{applicationId}/authorizations

List authorisations for a partner application

GET

/aowDate

Acquire the Dutch state pension (AOW) date for a person

GET

/chamberofcommerce/{chamberOfCommerceNumber}/companyinformation

Look up company information by KvK number

GET

/locationservices/address

Resolve a postal code and house number to a Dutch address

GET

/achmeainsurancecontracts

List Achmea insurance contracts for an employer

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the Loket.nl API by hand means running its OAuth2 flow for access tokens, choosing between the acceptance and production hosts, refreshing tokens, and shaping employer and employment request bodies yourself. Through Jentic you install once, import Loket.nl from the API Directory, store the OAuth credentials once, and your agent calls it.

Permission scoping

Loket.nl spreads its large payroll surface across many operations, so scoping is by operation: limit the agent to the operations it needs, such as listing providers or reading company information, and leave out application-set updates or authorization changes if the agent only reads administration data.

Credential isolation

Your Loket OAuth client secret and refresh token are stored once, encrypted, by your own Jentic One instance and exchanged for a scoped access token at execution time. They never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'list employments' or 'look up company information', and Jentic returns the matching Loket operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Loket.nl API through Jentic.

What authentication does the Loket.nl API use?

The Loket.nl API uses OAuth 2.0 - partners receive client credentials and individual users complete a user-credential flow against the Loket OAuth server. Through Jentic, refresh tokens stay in the credential vault and the agent only ever receives a short-lived scoped access token, so raw client secrets never enter agent context.

Can I submit a leave request through the Loket.nl API?

Yes. The leave domain exposes leave-request operations under endpoints tagged Leave, Leave request, and Leave balance, so you can create a request, query its status, and pull the resulting balance change. Use Jentic search 'submit a leave request' to load the operation directly.

What are the rate limits for the Loket.nl API?

Loket does not publish a public rate limit number; partners are expected to validate against the acceptance environment (api.loket-acc.nl) before pointing production traffic at api.loket.nl. If a request is throttled, Loket returns standard HTTP 429 - Jentic's executor surfaces that response unchanged so the agent can back off.

How do I look up Dutch company information through Loket via Jentic?

Loket exposes a chamber-of-commerce lookup at /chamberofcommerce/{chamberOfCommerceNumber}/companyinformation. Search Jentic for 'chamber of commerce company information', load the operation, and execute it with the KvK number to receive the registered company record.

Does the Loket.nl API cover Dutch state pension (AOW) calculations?

It exposes the AOW date for a given person via /aowDate but does not run the wider state pension calculation itself - combine it with the employment and wage endpoints if you need to derive expected retirement-related payroll changes.

How many endpoints does the Loket.nl API have?

641 unique path-and-method combinations across employments, leave, absence, providers, payroll, and reference data. Tag-based discovery is the fastest path: ask Jentic for the area you need (for example 'leave balance') rather than browsing the full path list.

Can I limit what my agent is allowed to do with the Loket.nl API?

Yes. Because you run Jentic One yourself, your own rules decide which of the 641 Loket.nl operations and which OAuth credentials the agent may use, and scoping is done per operation. You can allow only the calls the agent needs, such as listing providers or reading chamber-of-commerce company information, while leaving out write operations like editing an application set or changing partner authorizations. That way an agent built for read-only administration never gets the ability to alter provider or authorization records.

Loket.nl API

AI ReadinessFoundational (C+)58/100

See full scorecard

Community OpenAPI document · agent-readyHR recruitingPayrolloauth2641 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Read and update Dutch employer payroll, employee, leave, and absence records on Loket.nl across 641 endpoints scoped to employments, payroll runs, leave policies, and chamber-of-commerce lookups.

Use for: I need to list all employees for a Loket employer, Retrieve the leave balance for an employee on a given date, Submit a new leave request on behalf of an employee, Find absences that are still open for an employer

Not supported: Does not handle Dutch tax filing submissions, banking transfers to employees, or non-Dutch payroll jurisdictions - use for Loket.nl employer, employment, leave, and absence administration only.

Loket.nl is a Dutch HR and payroll platform whose REST API exposes the full employer record - employees, employments, payroll runs, leave balances, absence tracking, insurance contracts, and provider relationships. The API covers 641 operations across employer onboarding, contract administration, leave policies, payroll calculations, and statutory reporting for the Netherlands. Integrations require client and user credentials issued by Loket and run against an acceptance environment before going live.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: DSignals: 4

74%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: A-Signals: 4

46%

Example Density

How richly the API is illustrated with examples.

91%

Example Validity

Percentage of examples that conform to their schemas.

75%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: CSignals: 4

62%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

59%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: D-Signals: 1

43%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

100

Security

Trust, risk posture, and security compliance.

Grade: A+Signals: 1

100%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

100

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A+Signals: 1

100%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Loket.nl API to your agent

Capabilities

Start building with Loket.nl API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Loket.nl API

Jentic AI Readiness Score

Loket.nl API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness