Install Jentic One Beta

Connect the IBM MQ Cloud API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the IBM MQ Cloud 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%2Fibm.com%2Fmq-cloud-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%2Fibm.com%2Fmq-cloud-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 IBM MQ Cloud API.

Provision and tear down queue managers via /{serviceInstanceGuid}/queue_managers

Inspect queue manager status via /{serviceInstanceGuid}/queue_managers/{queueManagerId}/status

Manage users on a service instance via /{serviceInstanceGuid}/users

Manage applications attached to a service instance via /{serviceInstanceGuid}/applications

GET STARTED

Start building with IBM MQ Cloud API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use IBM MQ Cloud API for, with concrete tasks.

★ Environment Provisioning

Stand up a queue manager per environment (dev, staging, prod) on IBM MQ on Cloud as part of a broader infrastructure pipeline. POST to /{serviceInstanceGuid}/queue_managers to create the queue manager, then poll /{serviceInstanceGuid}/queue_managers/{queueManagerId}/status until it reaches a running state. Tear it down with DELETE on the same resource at the end of the environment lifecycle.

POST a new queue manager named QM_DEV to /{serviceInstanceGuid}/queue_managers, then poll /status every 30 seconds until it returns running.

Queue Manager User Management

Provision queue manager users with the right role for an application or human operator. POST to /{serviceInstanceGuid}/users to add a user, then list /{serviceInstanceGuid}/users to confirm membership. This is the auth surface that pairs with downstream IBM MQ REST API messaging calls against the same queue manager.

Create a user named app_orders on /{serviceInstanceGuid}/users with the messaging role and confirm by listing the users on the service instance.

Application Registration

Register an application with a service instance so it can connect to the queue manager with a known identity. The /{serviceInstanceGuid}/applications endpoint covers create and list operations, which makes it possible to script application onboarding alongside the queue manager itself rather than configuring it manually after provisioning.

POST a new application named order-service to /{serviceInstanceGuid}/applications and verify it is listed for the service instance.

AI Agent Cloud MQ Operator

An AI agent uses Jentic to provision queue managers on demand for short-lived test environments, then tears them down when the test completes. Through Jentic, the agent searches by intent, loads the queue manager creation schema, and executes calls without holding the raw IAM bearer token. Typical agent integration is under one hour because the provisioning surface has only a handful of resources.

Search Jentic for 'create a queue manager on IBM MQ Cloud', load the schema, and create a queue manager named QM_TEST_RUN_42.

Key Endpoints

11 endpoints — ibm mq on cloud is the managed offering of ibm mq that runs queue managers as a service on ibm cloud, removing the need to operate the underlying virtual machines or storage.

METHOD

PATH

DESCRIPTION

GET

/{serviceInstanceGuid}/queue_managers

List queue managers on a service instance

POST

/{serviceInstanceGuid}/queue_managers

Provision a new queue manager

GET

/{serviceInstanceGuid}/queue_managers/{queueManagerId}

Get a queue manager by ID

GET

/{serviceInstanceGuid}/queue_managers/{queueManagerId}/status

Get queue manager status

GET

/{serviceInstanceGuid}/users

List service instance users

GET

/{serviceInstanceGuid}/applications

List service instance applications

GET

/{serviceInstanceGuid}/queue_managers

List queue managers on a service instance

POST

/{serviceInstanceGuid}/queue_managers

Provision a new queue manager

GET

/{serviceInstanceGuid}/queue_managers/{queueManagerId}

Get a queue manager by ID

GET

/{serviceInstanceGuid}/queue_managers/{queueManagerId}/status

Get queue manager status

GET

/{serviceInstanceGuid}/users

List service instance users

GET

/{serviceInstanceGuid}/applications

List service instance applications

Why Jentic?

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

Setup

Wiring the IBM MQ Cloud API by hand means handling its bearer-token auth, choosing the right regional mq2.cloud.ibm.com host, and mapping its queue-manager provisioning routes yourself. Through Jentic you install once, import the IBM MQ Cloud API from the API Directory, store the token once, and your agent calls it.

Permission scoping

MQ Cloud puts the service instance and queue manager ids in the URL path (/{serviceInstanceGuid}/queue_managers/{queueManagerId}), so a rule can pin your agent to one service instance: it can read queue managers, users, and applications there. You choose the operations it may call, so provisioning a new queue manager is not included unless you add it.

Credential isolation

Your MQ Cloud 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 'list queue managers for a service instance' or 'check a queue manager's status', and Jentic returns the matching operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using IBM MQ Cloud API through Jentic.

What authentication does the IBM MQ Cloud API use?

The MQ Cloud API uses HTTP bearer authentication with an IBM Cloud IAM token. Through Jentic, the IAM credential is stored in your Jentic One instance and the agent calls MQ Cloud via a scoped Jentic credential, never the raw IAM token.

Can I provision a queue manager with this API?

Yes. POST to /{serviceInstanceGuid}/queue_managers to create a queue manager on a given service instance, then poll /{serviceInstanceGuid}/queue_managers/{queueManagerId}/status until the queue manager reaches a running state.

How do I manage queue manager users and applications?

Use /{serviceInstanceGuid}/users to manage the human and service users on a queue manager and /{serviceInstanceGuid}/applications to register applications. The two together cover the identity surface the runtime MQ REST API expects.

How do I provision MQ Cloud through Jentic?

Search Jentic for 'create a queue manager on IBM MQ Cloud', load the /{serviceInstanceGuid}/queue_managers schema, and execute. Install the SDK with pip install jentic and run the async search, load, execute pattern.

Is the IBM MQ Cloud API the same as the IBM MQ REST API?

No. The MQ Cloud API provisions and manages queue managers as a managed service, while the IBM MQ REST API operates on a queue manager that already exists - administering queues and channels, and putting or getting messages.

What are the rate limits for the IBM MQ Cloud API?

IBM Cloud applies account-level IAM-protected rate limits rather than a published per-endpoint limit. Treat 429 responses as backpressure and retry with exponential backoff, particularly when polling status endpoints during provisioning.

Can I limit what my agent is allowed to do with the IBM MQ Cloud API?

Yes. Because you self-host Jentic One, your own rules decide which MQ Cloud operations and which stored credential the agent may use. Since the service instance and queue manager ids sit in the URL path (/{serviceInstanceGuid}/queue_managers/{queueManagerId}), you can pin the agent to a single service instance and grant only read access to its queue managers, users, and applications. Provisioning a new queue manager or tearing one down stays out of reach unless you explicitly add those operations.

IBM MQ Cloud API

Name: IBM MQ Cloud API
Brand: IBM MQ Cloud API
Availability: InStock

Browse all Ibm APIs

Official vendor OpenAPI document · agent-readyCloud InfrastructureComputebearer11 EndpointsREST

For Agents

Provision and manage IBM MQ queue managers on IBM Cloud - create, configure, monitor, and tear down queue managers and their attached users and applications.

Use for: I need to provision a new queue manager on IBM MQ on Cloud, Get the status of a specific queue manager, List all queue managers on a service instance, Create a queue manager user with a specific role

Not supported: Does not handle messaging itself, queue or channel administration, or MQTT - use for provisioning and managing IBM MQ on Cloud queue managers, users, and applications only.

IBM MQ on Cloud is the managed offering of IBM MQ that runs queue managers as a service on IBM Cloud, removing the need to operate the underlying virtual machines or storage. The MQ Cloud API exposes provisioning and management operations for queue managers, queue manager users, and applications attached to a service instance, so platform teams can spin up and tear down MQ environments through automation rather than the IBM Cloud console. It is suited to teams treating MQ as ephemeral or environment-scoped infrastructure.

Jentic One on Github View OpenAPI Document

Connect the IBM MQ Cloud API to your agent

Capabilities

Start building with IBM MQ Cloud API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

IBM MQ Cloud API