Wunderbon Io wunderbon API

Name: wunderbon API
Brand: wunderbon API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentIdentity AuthIdentity Verificationbearer34 Endpoints

Install Jentic One Beta

Connect the wunderbon API to your agent

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.

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.wunderbon-io%2Fwunderbon-api" | 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%2Fswaggerhub.wunderbon-io%2Fwunderbon-api" | 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 wunderbon API.

ReadFavorite

DeleteFavorite

CreateFavorite

ReadIdentifier

GET STARTED

Start building with wunderbon API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use wunderbon 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

Key Endpoints

34 endpoints — welcome to our living wunderbon api documentation.

METHOD

PATH

DESCRIPTION

GET

/favorites/{id}

ReadFavorite

DELETE

/favorites/{id}

DeleteFavorite

POST

/favorites

CreateFavorite

GET

/favorites

ReadFavorites

GET

/identifiers/{id}

ReadIdentifier

PATCH

/identifiers/{id}

UpdateIdentifier

DELETE

/identifiers/{id}

DeleteIdentifier

POST

/identifiers

CreateIdentifier

GET

/favorites/{id}

ReadFavorite

DELETE

/favorites/{id}

DeleteFavorite

POST

/favorites

CreateFavorite

GET

/favorites

ReadFavorites

GET

/identifiers/{id}

ReadIdentifier

PATCH

/identifiers/{id}

UpdateIdentifier

Why Jentic?

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

Setup

Wiring the wunderbon API by hand means minting its bearer tokens through the /tokens endpoints, attaching them to every request, and managing its resource routes yourself. Through Jentic you install once, import the wunderbon API from the API Directory, store the token once, and your agent calls it.

Permission scoping

The wunderbon API puts each resource id in the URL path (/favorites/{id}, /identifiers/{id}), so a rule can pin your agent to one resource: it can read and update that record and nothing else. You choose the operations it may call, so destructive ones like deleting a favorite or an identifier are not included unless you add them.

Credential isolation

Your wunderbon API bearer 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 'read a favorite' or 'create an identifier', and Jentic returns the matching wunderbon API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using wunderbon 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 your Jentic One instance 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 through Jentic One, the self-hosted execution layer, 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.

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

Yes. Because you run Jentic One yourself, your own rules decide which wunderbon API operations and credentials the agent may use. The wunderbon API puts each resource id in the URL path, such as /favorites/{id} and /identifiers/{id}, so a rule can pin the agent to a single record and let it only read or update that one. You also choose the exact operations it may call, so destructive ones like DeleteFavorite or DeleteIdentifier stay off the list unless you add them.

Wunderbon Io wunderbon API

Connect the wunderbon API to your agent

Capabilities

Start building with wunderbon API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs