For Agents
Programmatically list superbots, list campaigns. Covers 6 operations with apiKey authentication.
Use for: I need to superbots, I want to campaigns, Search for queue calls in campaign, Find all contact in campaign
Not supported: Does not handle payments, communications, or developer tools - use for crm only.
Superbot voice AI platform API for managing superbots, campaigns, calling contacts, and generating TTS audio. The API exposes 6 endpoints secured with apiKey authentication.
Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Superbot 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%2Fsuperbot.one%2Fsuperbot-one" | shStep 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%2Fsuperbot.one%2Fsuperbot-one" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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.
What an agent can do with Superbot API.
List superbots
Queue calls in campaign
Update contact in campaign
Get contact records
Generate TTS audio
Patterns agents use Superbot API for, with concrete tasks.
★ CRM Operations
Use the Superbot API to perform crm operations programmatically. The API provides 6 endpoints covering core functionality including list superbots, list campaigns, queue calls in campaign.
Call GET /v2/superbot to list superbots
Automated Calls Management
Automate calls operations by combining multiple Superbot API endpoints. Agents can list campaigns and then queue calls in campaign in a single workflow.
Call GET /v2/superbot/{superbot}/campaign to list campaigns, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Superbot 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 apiKey tokens manually.
Search Jentic for 'list superbots', load the operation schema, and execute with Jentic-managed credentials
6 endpoints — superbot voice ai platform api for managing superbots, campaigns, calling contacts, and generating tts audio.
METHOD
PATH
DESCRIPTION
/v2/superbot
List superbots
/v2/superbot/{superbot}/campaign
List campaigns
/v2/superbot/{superbot}/campaign/{campaign}/call
Queue calls in campaign
/v2/superbot/{superbot}/campaign/{campaign}/contact/update
Update contact in campaign
/v2/superbot/{superbot}/campaign/{campaign}/contact/{phone}
Get contact records
/v2/tts
Generate TTS audio
/v2/superbot
List superbots
/v2/superbot/{superbot}/campaign
List campaigns
/v2/superbot/{superbot}/campaign/{campaign}/call
Queue calls in campaign
/v2/superbot/{superbot}/campaign/{campaign}/contact/update
Update contact in campaign
/v2/superbot/{superbot}/campaign/{campaign}/contact/{phone}
Get contact records
/v2/tts
Generate TTS audio
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Superbot API by hand means passing its API key as an Authorization header and handling retries yourself. Through Jentic you install once, import the Superbot API from the API Directory, store the key once, and your agent calls it.
Permission scoping
The Superbot API puts the superbot and campaign ids in the URL path (/v2/superbot/{superbot}/campaign/{campaign}/...), so a rule can pin your agent to one superbot or one campaign: it can read that campaign and nothing else. You choose the operations it may call, so ones like placing a call or updating a contact are not included unless you add them.
Credential isolation
Your Superbot API key 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 superbots' or 'read a campaign contact', and Jentic returns the matching Superbot API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Alternatives and complements available in the Jentic catalogue.
Specific to using Superbot API through Jentic.
What authentication does the Superbot API use?
The Superbot API uses an API key passed 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 list superbots with the Superbot API?
Yes. Use the GET /v2/superbot endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Superbot 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 list superbots through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'list superbots'. Jentic returns the matching Superbot API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Superbot API have?
The Superbot API exposes 6 endpoints covering calls, campaigns, contacts operations.
GET STARTED