Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Public Solutions Sync API 2.0, 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.pubsol%2Fpublic-solutions-sync-api-20" | 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.pubsol%2Fpublic-solutions-sync-api-20" | 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 Public Solutions Sync API 2.0 API.
inserts initial Aufn data
fetches Aufn data
updates existing Aufn data
Deletes Data from table Aufn, either by gischl if data is from gistab or by db i
Monitor Public Solutions Sync API 2.0 operational status and events
GET STARTED
Patterns agents use Public Solutions Sync API 2.0 API for, with concrete tasks.
★ Developer Tools Operations
Use the Public Solutions Sync API 2.0 to perform developer tools operations programmatically. The API provides 152 endpoints covering core functionality including inserts initial aufn data, inserts initial aufn data, fetches aufn data.
Call POST /bd_bis/upload/{tid} to inserts initial aufn data
Automated Aufn Management
Automate aufn operations by combining multiple Public Solutions Sync API 2.0 endpoints. Agents can inserts initial aufn data and then fetches aufn data in a single workflow.
Call POST /bd_bis/init/district to inserts initial aufn data, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Public Solutions Sync API 2.0 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 none tokens manually.
Search Jentic for 'inserts initial aufn data', load the operation schema, and execute with Jentic-managed credentials
152 endpoints — public solutions sync api 2.
METHOD
PATH
DESCRIPTION
/bd_bis/upload/{tid}
inserts initial Aufn data
/bd_bis/init/district
inserts initial Aufn data
/bd_bis/get/district
fetches Aufn data
/bd_bis/insert/district
inserts Aufn data
/bd_bis/update/district
updates existing Aufn data
/bd_bis/delete/district
Deletes Data from table Aufn, either by gischl if data is from gistab or by db i
/bd_bis/get_deleted/district
fetches deleted Aufn ids
/bd_bis/init/azra
inserts initial Azra data
/bd_bis/upload/{tid}
inserts initial Aufn data
/bd_bis/init/district
inserts initial Aufn data
/bd_bis/get/district
fetches Aufn data
/bd_bis/insert/district
inserts Aufn data
/bd_bis/update/district
updates existing Aufn data
/bd_bis/delete/district
Deletes Data from table Aufn, either by gischl if data is from gistab or by db i
/bd_bis/get_deleted/district
fetches deleted Aufn ids
/bd_bis/init/azra
inserts initial Azra data
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Public Solutions Sync API 2.0 by hand means mapping its bisoffice host, coding across its many per-table sync endpoints, and handling retries yourself even though it takes no credential. Through Jentic you install once, import the Public Solutions Sync API 2.0 from the API Directory, and your agent calls it.
Permission scoping
This API groups operations by data domain, so you limit the agent to the operations it needs, such as reading district records, and leave out the delete operations unless you add them. Every operation the agent can call is one you chose to allow.
Credential isolation
The Public Solutions Sync API 2.0 needs no credential, so there is nothing to store, and any host configuration is held by your own Jentic One instance and applied at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'read district records' or 'insert initial district data', and Jentic returns the matching Public Solutions Sync API 2.0 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 Public Solutions Sync API 2.0 API through Jentic.
What authentication does the Public Solutions Sync API 2.0 use?
The Public Solutions Sync API 2.0 uses no authentication. 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 inserts initial aufn data with the Public Solutions Sync API 2.0?
Yes. Use the POST /bd_bis/upload/{tid} endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Public Solutions Sync API 2.0?
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 inserts initial aufn data through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'inserts initial aufn data'. Jentic returns the matching Public Solutions Sync API 2.0 operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Public Solutions Sync API 2.0 have?
The Public Solutions Sync API 2.0 exposes 152 endpoints covering aufn, azra, kost operations.
Can I limit what my agent is allowed to do with the Public Solutions Sync API 2.0?
Yes. Because you run Jentic One yourself, your own rules decide which of this API's operations and configuration the agent may use. Its endpoints are grouped by data domain, so you can allow only what the agent needs, such as reading district records with GET /bd_bis/get/district, while leaving out the delete operations like POST /bd_bis/delete/district unless you explicitly add them. Every operation the agent can call is one you chose to allow.
Know of an official OpenAPI document? Contribute it →
For Agents
Programmatically inserts initial aufn data, inserts initial aufn data. Covers 152 operations.
Use for: I need to inserts initial aufn data, I want to inserts initial aufn data, Search for fetches aufn data, Find all inserts aufn data
Not supported: Does not handle payments, communications, or crm - use for developer tools only.
Public Solutions Sync API 2.0. The API exposes 152 endpoints.