Install Jentic One Beta

Connect the WSO2 API Manager - Publisher API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the WSO2 API Manager - Publisher 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.ram.grandhi%2Fwso2-api-manager---publisher-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.ram.grandhi%2Fwso2-api-manager---publisher-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 WSO2 API Manager - Publisher API.

Create a new API

Retrieve/Search APIs

Change API Status

Get details of an API

Update an API

GET STARTED

Start building with WSO2 API Manager - Publisher API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use WSO2 API Manager - Publisher API for, with concrete tasks.

★ Developer Tools Operations

Use the WSO2 API Manager - Publisher API to perform developer tools operations programmatically. The API provides 39 endpoints covering core functionality including create a new API, retrieve/search apis , change API status.

Call POST /apis to create a new API

Automated API (Collection) Management

Automate API (collection) operations by combining multiple WSO2 API Manager - Publisher API endpoints. Agents can retrieve/search apis and then change API status in a single workflow.

Call GET /apis to retrieve/search apis , then verify the result

AI Agent Integration via Jentic

AI agents discover and call WSO2 API Manager - Publisher 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 API', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

39 endpoints — this specifies a **restful api** for wso2 **api manager** - publisher.

METHOD

PATH

DESCRIPTION

POST

/apis

Create a new API

GET

/apis

Retrieve/Search APIs

POST

/apis/change-lifecycle

Change API Status

POST

/apis/copy-api

Create a new API version

GET

/apis/{apiId}

Get details of an API

PUT

/apis/{apiId}

Update an API

DELETE

/apis/{apiId}

Delete an API

POST

/apis/{apiId}/documents

Add a new document to an API

POST

/apis

Create a new API

GET

/apis

Retrieve/Search APIs

POST

/apis/change-lifecycle

Change API Status

POST

/apis/copy-api

Create a new API version

GET

/apis/{apiId}

Get details of an API

PUT

/apis/{apiId}

Update an API

DELETE

/apis/{apiId}

Delete an API

POST

/apis/{apiId}/documents

Add a new document to an API

Why Jentic?

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

Setup

Wiring the WSO2 API Manager Publisher API by hand means pointing at its wso2.com publisher host, coding the API lifecycle and document calls, and handling retries yourself even though it takes no credential here. Through Jentic you install once, import the WSO2 API Manager Publisher API from the API Directory, and your agent calls it.

Permission scoping

This API puts the API id in the URL path (/apis/{apiId}/...), so a rule can pin your agent to one managed API: it can read that API and its documents and nothing else. You choose the operations it may call, so deletion or lifecycle changes are not included unless you add them.

Credential isolation

The WSO2 API Manager Publisher API needs no credential in this spec, so there is nothing to store, and any host configuration is held by your own Jentic One instance and applied 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 managed API' or 'attach a document to an API', and Jentic returns the matching WSO2 API Manager Publisher operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Github

Alternative developer tools API

Choose Github when you need a different approach to developer tools operations

Alternative

Gitlab

Alternative developer tools API

Choose Gitlab when you need a different approach to developer tools operations

FAQs

Specific to using WSO2 API Manager - Publisher API through Jentic.

What authentication does the WSO2 API Manager - Publisher API use?

The WSO2 API Manager - Publisher 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 API with the WSO2 API Manager - Publisher API?

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

What are the rate limits for the WSO2 API Manager - Publisher 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 API 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 API'. Jentic returns the matching WSO2 API Manager - Publisher API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the WSO2 API Manager - Publisher API have?

The WSO2 API Manager - Publisher API exposes 39 endpoints covering API (collection), API (individual), application (individual) operations.

Can I limit what my agent is allowed to do with the WSO2 API Manager Publisher API?

Yes. Because you run Jentic One yourself, your own rules decide which operations and hosts the agent may use, and this API puts the managed API id in the URL path (/apis/{apiId}/...), so a rule can pin the agent to a single managed API and let it only read that API and its documents. You choose the exact operations it can call, so destructive actions like DELETE /apis/{apiId} or lifecycle changes through POST /apis/change-lifecycle stay off unless you explicitly allow them. Anything you do not grant, such as creating a new API with POST /apis, the agent cannot invoke.

Ram Grandhi WSO2 API Manager - Publisher API

Name: WSO2 API Manager - Publisher API
Brand: WSO2 API Manager - Publisher API
Availability: InStock

Browse all Swaggerhub Ram Grandhi APIs

Community OpenAPI document · agent-readyDeveloper ToolsSource Controlnone39 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Programmatically create a new API, retrieve/search apis . Covers 39 operations.

Use for: I need to a new API, I want to retrieve/search apis , Search for change API status, Find all a new API version

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

This specifies a **RESTful API** for WSO2 **API Manager** - Publisher. Please see [full swagger definition](https://raw.githubusercontent.com/wso2/carbon-apimgt/v6.0.4/components/apimgt/org.wso2.carbon.apimgt.rest.api.publisher/src/main/resources/publisher-api.yaml) of the API which is written using [swagger 2.0](http://swagger.io/) specification. The API exposes 39 endpoints.

Jentic One on Github View OpenAPI Document