Install Jentic One Beta

Connect the Systembolaget API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Systembolaget 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%2Fsystembolaget.se%2Fsystembolaget-se" | 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%2Fsystembolaget.se%2Fsystembolaget-se" | 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 Systembolaget API.

Search products

Get product details

Integrate Systembolaget API into automated workflows

Query and filter Systembolaget API records by parameters

Monitor Systembolaget API operational status and events

GET STARTED

Start building with Systembolaget API

Explore with Jentic One

View OpenAPI Document

Automated Inventory Management

Automate inventory operations by combining multiple Systembolaget API endpoints. Agents can get product details and then search stores in a single workflow.

Call GET /products/v1/product/{productNumber} to get product details, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Systembolaget 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 apiKey tokens manually.

Search Jentic for 'search products', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

5 endpoints — api for accessing systembolaget's product catalog and store information.

METHOD

PATH

DESCRIPTION

GET

/products/v1/product

Search products

GET

/products/v1/product/{productNumber}

Get product details

GET

/stores/v1/store

Search stores

GET

/stores/v1/store/{siteId}

Get store details

GET

/inventory/v1/store/{siteId}/product/{productNumber}

Get product inventory at specific store

GET

/products/v1/product

Search products

GET

/products/v1/product/{productNumber}

Get product details

GET

/stores/v1/store

Search stores

GET

/stores/v1/store/{siteId}

Get store details

GET

/inventory/v1/store/{siteId}/product/{productNumber}

Get product inventory at specific store

Why Jentic?

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

Setup

Wiring the Systembolaget API by hand means sending the Ocp-Apim-Subscription-Key header to the Azure API Management host and shaping the product, store, and inventory requests yourself. Through Jentic you install once, import Systembolaget from the API Directory, store the subscription key once, and your agent calls it.

Permission scoping

Systembolaget puts the store and product ids in the URL path (/stores/v1/store/{siteId}, /products/v1/product/{productNumber}), so a rule can pin your agent to one store or product: it can read that record and its inventory and nothing else. You choose the operations it may call, and these operations are read-only.

Credential isolation

Your Systembolaget subscription key 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 'search products' or 'check store inventory for a product', and Jentic returns the matching Systembolaget operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Shopify

Alternative e commerce API

Choose Shopify when you need a different approach to e commerce operations

Alternative

Stripe

Alternative e commerce API

Choose Stripe when you need a different approach to e commerce operations

FAQs

Specific to using Systembolaget API through Jentic.

What authentication does the Systembolaget API use?

The Systembolaget API uses an API key passed in the `Ocp-Apim-Subscription-Key` 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 search products with the Systembolaget API?

Yes. Use the GET /products/v1/product endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the Systembolaget 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 search products through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'search products'. Jentic returns the matching Systembolaget API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the Systembolaget API have?

The Systembolaget API exposes 5 endpoints covering inventory, products, stores operations.

Can I limit what my agent is allowed to do with the Systembolaget API?

Yes. Because you run Jentic One yourself, your own rules decide which of the five read-only Systembolaget operations the agent may call and which credentials it may use. Since the store and product ids sit in the URL path (/stores/v1/store/{siteId}, /products/v1/product/{productNumber}), a rule can pin the agent to a single store or product so it reads only that record and its inventory. You can also allow just product or store search while blocking everything else, and the subscription key is injected at execution time rather than exposed to the agent.

Systembolaget Se Systembolaget API

Name: Systembolaget API
Brand: Systembolaget API
Availability: InStock

Official vendor OpenAPI document · agent-readyE CommerceStorefrontapiKey5 EndpointsREST

For Agents

Programmatically search products, get product details. Covers 5 operations with apiKey authentication.

Use for: I need to products, I want to product details, Search for stores, Find all store details

Not supported: Does not handle payments, communications, or crm - use for e-commerce only.

API for accessing Systembolaget's product catalog and store information. Systembolaget is the government-owned chain of liquor stores in Sweden. The API exposes 5 endpoints secured with apiKey authentication.

Jentic One on Github View OpenAPI Document

Connect the Systembolaget API to your agent

Capabilities

Start building with Systembolaget API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Systembolaget Se Systembolaget API