For Agents
Programmatically inserts initial aufn data, inserts initial aufn data. Covers 152 operations.
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.
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | 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
GET STARTED
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.
Jentic publishes the only available OpenAPI document for Public Solutions Sync API 2.0, keeping it validated and agent-ready.
Public Solutions Sync API 2.0. The API exposes 152 endpoints.
Monitor Public Solutions Sync API 2.0 operational status and events
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
Three things that make agents converge on Jentic-routed access.
Credential isolation
Public Solutions Sync API 2.0 none credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.
Intent-based discovery
Agents search by intent (e.g., 'inserts initial aufn data') and Jentic returns the matching Public Solutions Sync API 2.0 operation with its input schema, so the agent can call the right endpoint without browsing docs.
Time to first call
Direct Public Solutions Sync API 2.0 integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.
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
Gitlab
Alternative developer tools API
Choose Gitlab 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 the MAXsystem vault 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 at https://app.jentic.com/sign-up, 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.
/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