Install Jentic One Beta

Connect the WeGA API to your agent

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

Create a new WeGA ID

Get status information about the running WeGA-WebApp

Finds code samples by XML element

Lists all documents

Monitor WeGA API operational status and events

GET STARTED

Start building with WeGA API

Explore with Jentic One

View OpenAPI Document

Automated Documents Management

Automate documents operations by combining multiple WeGA API endpoints. Agents can get status information about the running wega-webapp and then finds code samples by xml element in a single workflow.

Call GET /application/status to get status information about the running wega-webapp, then verify the result

AI Agent Integration via Jentic

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

Search Jentic for 'create a new wega id', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

10 endpoints — ⚠️deprecation warning⚠️ this version of the wega api specification is outdated and superseded by [version 1.

METHOD

PATH

DESCRIPTION

GET

/application/newID

Create a new WeGA ID

GET

/application/status

Get status information about the running WeGA-WebApp

GET

/code/findByElement/{element}

Finds code samples by XML element

GET

/documents

Lists all documents

GET

/documents/findByAuthor/{authorID}

Finds documents by author

GET

/documents/findByDate

Finds documents by date

GET

/documents/findByMention/{docID}

Finds documents by reference

GET

/documents/{docID}

Returns documents by ID

GET

/application/newID

Create a new WeGA ID

GET

/application/status

Get status information about the running WeGA-WebApp

GET

/code/findByElement/{element}

Finds code samples by XML element

GET

/documents

Lists all documents

GET

/documents/findByAuthor/{authorID}

Finds documents by author

GET

/documents/findByDate

Finds documents by date

GET

/documents/findByMention/{docID}

Finds documents by reference

GET

/documents/{docID}

Returns documents by ID

Why Jentic?

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

Setup

Wiring the WeGA API by hand means pointing at its host, tracking its document lookup paths, and handling responses yourself. Through Jentic you install once, import the WeGA API from the API Directory, configure it once, and your agent calls it.

Permission scoping

WeGA puts the document id in the URL path (/documents/{docID}), so a rule can pin your agent to reading one document and nothing else. You choose the operations it may call, so anything beyond the reads you enable is not available.

Credential isolation

This read-only API needs no credential, so there is no secret to store. Any host value you configure stays in your own Jentic One instance and is injected at execution time, never entering the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'find documents by author' or 'get a document by id', and Jentic returns the matching WeGA operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using WeGA API through Jentic.

What authentication does the WeGA API use?

The WeGA API 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 create a new wega id with the WeGA API?

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

What are the rate limits for the WeGA 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 create a new wega id through Jentic?

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

How many endpoints does the WeGA API have?

The WeGA API exposes 10 endpoints covering documents, search, code samples operations.

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

Yes. Jentic One is self-hosted, so your own rules decide which WeGA operations the agent may call and which it may not. Because WeGA is read-only and puts the document ID in the URL path (GET /documents/{docID}), you can pin the agent to reading a single document, or allow only broader lookups such as listing documents or finding them by author, date, or reference. Anything you do not enable, including creating a new WeGA ID or reading application status, stays off limits to the agent.

Weber Gesamtausgabe De WeGA API

AI ReadinessFoundational (C)54/100

See full scorecard

CRMContact Managementnone10 EndpointsREST

For Agents

Programmatically create a new wega id, get status information about the running wega-webapp. Covers 10 operations.

Use for: I need to a new wega id, I want to status information about the running wega-webapp, Search for finds code samples by xml element, Find all lists all documents

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

⚠️DEPRECATION WARNING⚠️ This version of the WeGA API specification is outdated and superseded by [version 1.1.0](https://weber-gesamtausgabe.de/api/v1/openapi.json). For feedback or requests about this API please contact stadler@weber-gesamtausgabe.de or start the discussion at https://github.com/Edirom/WeGA-WebApp. The API exposes 10 endpoints.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

100

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

98%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

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

100%

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: BSignals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

55%

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: FSignals: 4

54%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

OperationId Quality

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

50%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

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

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: BSignals: 1

64%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the WeGA API to your agent

Capabilities

Start building with WeGA API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Weber Gesamtausgabe De WeGA API

Jentic AI Readiness Score

WeGA 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