Install Jentic One Beta

Connect the starbuero.de External API to your agent

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

Create new contact

Retrieve all contacts

Fetch specific contact

Update contact

Remove contact

GET STARTED

Start building with starbuero.de External API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use starbuero.de External API for, with concrete tasks.

★ Developer Tools Operations

Use the starbuero.de External API to perform developer tools operations programmatically. The API provides 25 endpoints covering core functionality including create new contact, retrieve all contacts, fetch specific contact.

Call POST /external/api/v1/addon_contact/contact to create new contact

Automated Additional Resources Management

Automate additional resources operations by combining multiple starbuero.de External API endpoints. Agents can retrieve all contacts and then fetch specific contact in a single workflow.

Call GET /external/api/v1/addon_contact/contact to retrieve all contacts, then verify the result

AI Agent Integration via Jentic

AI agents discover and call starbuero.de External 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 bearer tokens manually.

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

Key Endpoints

25 endpoints — external api - beta for starbuero.

METHOD

PATH

DESCRIPTION

POST

/external/api/v1/addon_contact/contact

Create new contact

GET

/external/api/v1/addon_contact/contact

Retrieve all contacts

GET

/external/api/v1/addon_contact/contact/{contact}

Fetch specific contact

PUT

/external/api/v1/addon_contact/contact/{contact}

Update contact

DELETE

/external/api/v1/addon_contact/contact/{contact}

Remove contact

POST

/external/api/v1/appointment

Create appointment

GET

/external/api/v1/appointment

List all appointments

GET

/external/api/v1/appointment/{appointment}

Retrieve specific appointment

POST

/external/api/v1/addon_contact/contact

Create new contact

GET

/external/api/v1/addon_contact/contact

Retrieve all contacts

GET

/external/api/v1/addon_contact/contact/{contact}

Fetch specific contact

PUT

/external/api/v1/addon_contact/contact/{contact}

Update contact

DELETE

/external/api/v1/addon_contact/contact/{contact}

Remove contact

POST

/external/api/v1/appointment

Create appointment

GET

/external/api/v1/appointment

List all appointments

GET

/external/api/v1/appointment/{appointment}

Why Jentic?

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

Setup

Wiring the starbuero.de External API by hand means setting up its bearer token, mapping the contact and appointment endpoints, and threading the contact and appointment ids through reads and updates yourself. Through Jentic you install once, import the starbuero.de External API from the API Directory, store the token once, and your agent calls it.

Permission scoping

The API puts the contact id in the URL path (/external/api/v1/addon_contact/contact/{contact}), so a rule can pin your agent to one contact: it can read and update that contact and nothing else. You choose the operations it may call, so destructive ones like deleting a contact are not included unless you add them.

Credential isolation

Your starbuero.de token 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 'create a new contact' or 'book an appointment', and Jentic returns the matching starbuero.de External API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using starbuero.de External API through Jentic.

What authentication does the starbuero.de External API use?

The starbuero.de External API uses a Bearer token in the Authorization 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 create new contact with the starbuero.de External API?

Yes. Use the POST /external/api/v1/addon_contact/contact endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the starbuero.de External 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 new contact through Jentic?

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

How many endpoints does the starbuero.de External API have?

The starbuero.de External API exposes 25 endpoints covering additional resources, addon contact management, appointment management operations.

Can I limit what my agent is allowed to do with the starbuero.de External API?

Yes. Jentic One is self-hosted by you, so your own rules decide which starbuero.de operations and credentials the agent may use. Because the contact id sits in the URL path (/external/api/v1/addon_contact/contact/{contact}), you can pin the agent to a single contact so it only reads and updates that one and nothing else. You also choose which operations are exposed, so destructive calls like DELETE on a contact stay out of reach unless you explicitly add them.

starbuero.de External API

AI ReadinessAI-Aware (B+)68/100

See full scorecard

Official vendor OpenAPI document · agent-readyDeveloper ToolsSource Controlbearer25 EndpointsREST

For Agents

Programmatically create new contact, retrieve all contacts. Covers 25 operations with bearer authentication.

Use for: I need to new contact, I want to all contacts, Search for fetch specific contact, Find all contact

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

External API - BETA for starbuero.de office management platform. The API exposes 25 endpoints secured with bearer authentication.

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: C+Signals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

29%

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: D+Signals: 4

28%

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.

68%

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.

Security

Trust, risk posture, and security compliance.

Grade: B-Signals: 1

60%

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 starbuero.de External API to your agent

Capabilities

Start building with starbuero.de External API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

starbuero.de External API

Jentic AI Readiness Score

starbuero.de External 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