Install Jentic One Beta

Connect the WSO2 API Manager - Store to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the WSO2 API Manager - Store, 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---store" | 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---store" | 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 - Store API.

Retrieve/Search APIs

Generate SDK for an API

Get details of an API

Query and filter WSO2 API Manager - Store records by parameters

Monitor WSO2 API Manager - Store operational status and events

GET STARTED

Start building with WSO2 API Manager - Store API

Explore with Jentic One

View OpenAPI Document

Automated Apis Management

Automate apis operations by combining multiple WSO2 API Manager - Store endpoints. Agents can generate sdk for an API and then get details of an API in a single workflow.

Call POST /apis/generate-sdk/ to generate sdk for an API , then verify the result

AI Agent Integration via Jentic

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

Key Endpoints

21 endpoints — this specifies a **restful api** for wso2 **api manager** - store.

METHOD

PATH

DESCRIPTION

GET

/apis

Retrieve/Search APIs

POST

/apis/generate-sdk/

Generate SDK for an API

GET

/apis/{apiId}

Get details of an API

GET

/apis/{apiId}/documents

Get a list of documents of an API

GET

/apis/{apiId}/documents/{documentId}

Get a document of an API

GET

/apis/{apiId}/documents/{documentId}/content

Get the content of an API document

GET

/apis/{apiId}/swagger

Get swagger definition

GET

/apis/{apiId}/thumbnail

Get thumbnail image

GET

/apis

Retrieve/Search APIs

POST

/apis/generate-sdk/

Generate SDK for an API

GET

/apis/{apiId}

Get details of an API

GET

/apis/{apiId}/documents

Get a list of documents of an API

GET

/apis/{apiId}/documents/{documentId}

Get a document of an API

GET

/apis/{apiId}/documents/{documentId}/content

Get the content of an API document

GET

/apis/{apiId}/swagger

Get swagger definition

GET

/apis/{apiId}/thumbnail

Get thumbnail image

Why Jentic?

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

Setup

Wiring the WSO2 API Manager Store API by hand means pointing at its wso2.com store host, coding the API search and document-retrieval calls, and handling retries yourself even though it takes no credential here. Through Jentic you install once, import the WSO2 API Manager Store 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 published API: it can read that API, its documents, and its swagger and nothing else. You choose the operations it may call, so SDK generation is not included unless you add it.

Credential isolation

The WSO2 API Manager Store 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 'search published APIs' or 'read an API's documentation', and Jentic returns the matching WSO2 API Manager Store operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

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

What authentication does the WSO2 API Manager - Store use?

The WSO2 API Manager - Store 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 retrieve/search apis with the WSO2 API Manager - Store?

Yes. Use the GET /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 - Store?

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 retrieve/search apis through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'retrieve/search apis '. Jentic returns the matching WSO2 API Manager - Store operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

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

The WSO2 API Manager - Store exposes 21 endpoints covering apis, applications, subscriptions operations.

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

Yes. Jentic One is self-hosted, so your own rules decide which WSO2 API Manager - Store operations the agent may call. Because the API puts the API id in the URL path (/apis/{apiId}/...), you can pin the agent to a single published API and let it only read that API, its documents, and its swagger definition. You choose the operations it is permitted to use, so SDK generation via POST /apis/generate-sdk/ is not available to the agent unless you explicitly add it.

Ram Grandhi WSO2 API Manager - Store

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

Browse all Swaggerhub Ram Grandhi APIs

Community OpenAPI document · agent-readyDeveloper ToolsSource Controlnone21 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Programmatically retrieve/search apis , generate sdk for an API . Covers 21 operations.

Use for: I need to retrieve/search apis , I want to generate sdk for an API , Search for details of an API , Find all a list of documents of an API

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

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

Jentic One on Github View OpenAPI Document

Connect the WSO2 API Manager - Store to your agent

Capabilities

Start building with WSO2 API Manager - Store API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Ram Grandhi WSO2 API Manager - Store