Install Jentic One Beta

Connect the Pandorabots AIaaS to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Pandorabots AIaaS, 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%2Fpandorabots.com%2Fpandorabots" | 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%2Fpandorabots.com%2Fpandorabots" | 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 Pandorabots AIaaS API.

Send a message to a chatbot and receive its reply

List the chatbots that belong to an application

Create a chatbot and compile it before use

Upload the AIML, set, map, and substitution files that define a bot

Retrieve or delete a bot's files

GET STARTED

Start building with Pandorabots AIaaS API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Pandorabots AIaaS API for, with concrete tasks.

★ Agent-Driven Chatbot Conversations

An AI agent connected through Jentic sends a user's message to a Pandorabots bot and returns the reply, so the bot's scripted responses can be surfaced inside a larger agent workflow. The agent names the application and bot on each call and passes the message text to receive an answer.

Send the user's question to my support bot and return the bot's reply

Bot Authoring and Deployment

A tool builds a chatbot by creating it, uploading the AIML and related files that define its responses, and compiling it so it is ready to answer. The workflow lists a bot's files to check what is deployed and replaces individual files as the bot's script changes.

Create a bot named 'greeter', upload its AIML file, and compile it so it is ready to talk

Conversation Debugging

A developer uses the debug talk endpoint to see how a bot arrived at a particular reply, so they can trace which pattern matched and adjust the underlying files. This shortens the loop between editing a bot's AIML and understanding its behaviour.

Run the message through the debug endpoint and show which pattern the bot matched

Key Endpoints

13 endpoints — the pandorabots aiaas api creates and runs aiml chatbots, so an application can hold a conversation with a bot and manage the files that define its responses.

METHOD

PATH

DESCRIPTION

POST

/atalk/{app_id}/{botname}

Talk to a bot

GET

/bot/{app_id}

List of bots

PUT

/bot/{app_id}/{botname}

Create a bot

GET

/bot/{app_id}/{botname}/verify

Compile a bot

PUT

/bot/{app_id}/{botname}/{file-kind}/{filename}

Upload a bot file

GET

/bot/{app_id}/{botname}

List of bot files

POST

/atalk/{app_id}/{botname}

Talk to a bot

GET

/bot/{app_id}

List of bots

PUT

/bot/{app_id}/{botname}

Create a bot

GET

/bot/{app_id}/{botname}/verify

Compile a bot

PUT

/bot/{app_id}/{botname}/{file-kind}/{filename}

Upload a bot file

GET

/bot/{app_id}/{botname}

List of bot files

Why Jentic?

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

Setup

Wiring the Pandorabots AIaaS API by hand means passing the application id and bot name on every path, keeping the API key on each query, and compiling a bot after each file change. Through Jentic you install once, import Pandorabots from the API Directory, store the key once, and your agent calls it.

Permission scoping

Pandorabots puts the application id and bot name in the URL path, so a rule can pin your agent to one bot: it can hold conversations and read that bot's files and nothing else. You choose the operations it may call, so deleting files or bots is left out unless you add it.

Credential isolation

Your Pandorabots application id and API key are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'send a message to a bot' or 'upload an AIML file', and Jentic returns the matching Pandorabots operation with its input schema so the agent calls the right endpoint without reading the reference docs.

FAQs

Specific to using Pandorabots AIaaS API through Jentic.

Is there a Pandorabots MCP server?

You don't need an MCP server to give your agent the Pandorabots AIaaS API. Jentic connects it directly from the API Directory: import it, store your key once, and your agent can talk to bots and manage their files straight away, with no extra server to run and no tool definitions to load into the agent's context.

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

Yes. Because Pandorabots puts the application id and bot name in the URL path, you can write a rule that pins your agent to one bot, so it can hold conversations with that bot and touch no others, and every call it makes is logged. You also choose which operations it may call, so file deletion need not be included.

What authentication does the Pandorabots AIaaS API use?

The Pandorabots AIaaS API authenticates with an API key passed as the user_key query parameter, together with your application id, per its OpenAPI spec. Through Jentic the key is stored encrypted by your own instance and added to each request at call time, so it never appears in the agent's prompt or logs.

Can I upload AIML files to a bot with the Pandorabots AIaaS API?

Yes. The API uploads the AIML, set, map, and substitution files that define a bot's responses, and it compiles the bot so the changes take effect. You can also list and delete a bot's files, so an agent can manage the knowledge behind a bot end to end.

What are the rate limits for the Pandorabots AIaaS API?

The OpenAPI spec does not specify rate limits for the Pandorabots AIaaS API. For current limits and plan details, see the Pandorabots documentation at https://www.pandorabots.com/docs/.

How do I talk to a Pandorabots bot through Jentic?

Import the Pandorabots AIaaS API from the Jentic API Directory, then have your agent issue a request such as 'send this message to my support bot'. Jentic matches the intent to the talk operation and returns its input schema so the agent builds the correct request, with your stored key injected at call time. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Pandorabots AIaaS

Name: Pandorabots AIaaS API
Brand: Pandorabots AIaaS
Availability: InStock

AI ReadinessFoundational (D+)49/100

See full scorecard

Community OpenAPI document · agent-readyAI/MLLanguage ModelsapiKey13 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Send messages to a Pandorabots chatbot and receive replies, create bots, upload the AIML and related files that define them, compile them, and list or delete bot files. Authenticates with an API key passed as the user_key query parameter alongside the application id.

Use for: Send a message to my chatbot and get its reply, List the bots in my application, Create a new chatbot, Upload an AIML file to my bot

Not supported: Does not handle account billing, model training beyond AIML, or analytics. Use for talking to Pandorabots bots and managing their files only.

The Pandorabots AIaaS API creates and runs AIML chatbots, so an application can hold a conversation with a bot and manage the files that define its responses. You send a message to a bot and receive its reply, and you can create a bot, upload the AIML, set, map, and substitution files that make up its knowledge, compile it, and list or delete those files. Bots are organised under an application, and each request names the application and the bot it targets. A separate debug talk endpoint returns extra detail about how a reply was produced.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

100

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

98%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

100%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: CSignals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

25%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: CSignals: 4

57%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

65%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: FSignals: 1

15%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

100

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A+Signals: 1

100%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Pandorabots AIaaS to your agent

Capabilities

Start building with Pandorabots AIaaS API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Pandorabots AIaaS

Jentic AI Readiness Score

Pandorabots AIaaS

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness