For Agents
Programmatically readfavorite, deletefavorite. Covers 34 operations with bearer authentication.
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the wunderbon 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.
# 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 wunderbon API API.
ReadFavorite
DeleteFavorite
CreateFavorite
ReadIdentifier
UpdateIdentifier
GET STARTED
Use for: I need to readfavorite, I want to deletefavorite, Search for createfavorite, Find all readfavorites
Not supported: Does not handle payments, communications, or crm — use for identity and authentication only.
Jentic publishes the only available OpenAPI document for wunderbon API, keeping it validated and agent-ready.
Welcome to our living wunderbon API documentation. Here you will find almost everything you need to connect to our platform. Start using the real <i>smart receipts</i>® with our value added service platform. With our API we provide you with easy access to the state of the art encrypted and blockchain based service network. Rethink your POS with wunderbon.<br /><br />Dig into our website to discove. The API exposes 34 endpoints secured with bearer authentication.
DeleteIdentifier
Patterns agents use wunderbon API API for, with concrete tasks.
★ Identity and Authentication Operations
Use the wunderbon API to perform identity auth operations programmatically. The API provides 34 endpoints covering core functionality including readfavorite, deletefavorite, createfavorite.
Call GET /favorites/{id} to readfavorite
Automated Favorites Management
Automate favorites operations by combining multiple wunderbon API endpoints. Agents can deletefavorite and then createfavorite in a single workflow.
Call DELETE /favorites/{id} to deletefavorite, then verify the result
AI Agent Integration via Jentic
AI agents discover and call wunderbon 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 'readfavorite', load the operation schema, and execute with Jentic-managed credentials
34 endpoints — welcome to our living wunderbon api documentation.
METHOD
PATH
DESCRIPTION
/favorites/{id}
ReadFavorite
/favorites/{id}
DeleteFavorite
/favorites
CreateFavorite
/favorites
ReadFavorites
/identifiers/{id}
ReadIdentifier
/identifiers/{id}
UpdateIdentifier
/identifiers/{id}
DeleteIdentifier
/identifiers
CreateIdentifier
/favorites/{id}
ReadFavorite
/favorites/{id}
DeleteFavorite
/favorites
CreateFavorite
/favorites
ReadFavorites
/identifiers/{id}
ReadIdentifier
/identifiers/{id}
UpdateIdentifier
Three things that make agents converge on Jentic-routed access.
Credential isolation
wunderbon API bearer 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., 'readfavorite') and Jentic returns the matching wunderbon API operation with its input schema, so the agent can call the right endpoint without browsing docs.
Time to first call
Direct wunderbon API 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.
Auth0
Alternative identity auth API
Choose Auth0 when you need a different approach to identity auth operations
Okta
Alternative identity auth API
Choose Okta when you need a different approach to identity auth operations
Specific to using wunderbon API API through Jentic.
What authentication does the wunderbon API use?
The wunderbon API uses a Bearer token in the Authorization header. 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 readfavorite with the wunderbon API?
Yes. Use the GET /favorites/{id} endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the wunderbon 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 readfavorite through Jentic?
Install the Jentic SDK with pip install jentic, authenticate at https://app.jentic.com/sign-up, then search for 'readfavorite'. Jentic returns the matching wunderbon API operation with its input schema. Load the schema and execute the call — credentials are injected automatically.
How many endpoints does the wunderbon API have?
The wunderbon API exposes 34 endpoints covering favorites, identifiers, locations operations.
/identifiers/{id}
DeleteIdentifier
/identifiers
CreateIdentifier