CommPeak APIs for AI Agents
CommunicationsVoice TelephonySms MessagingJentic-Generated SpecsBearer tokenAPI keyAgent Ready
CommPeak API Catalog
2 APIs across 1 product group.
Communications2
CommPeak APIRun outbound dialler campaigns, send SMS, look up phone numbers via HLR, and pull billing rates and call records on CommPeak with one bearer token.~39 endpointsCommPeak SMS Streams APISend single or batched SMS messages and check delivery status on CommPeak SMS Streams with one API key.~2 endpoints
Which CommPeak API should I use?
| I want to... | Use | Why |
|---|---|---|
| Send a transactional SMS or OTP | CommPeak SMS Streams API | SMS Streams is the thin two-endpoint send-and-status surface with no dialler or billing dependencies, best for simple transactional or batch sends. |
| Send SMS alongside voice, dialler, HLR, or billing work | CommPeak API | The main API sends SMS via TextPeak in the same token scope as calls, campaigns, lookups, and rate cards, so one integration covers a full outbound motion. |
| Reconcile SMS delivery status | CommPeak SMS Streams API | messages_status returns per-id delivery state for reconciling failures without pulling the broader call and billing data of the main API. |
Install Jentic One Beta
Connect the CommPeak APIs to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the CommPeak APIs, 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.
1
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%2Fcommpeak.com" | sh2
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%2Fcommpeak.com" | 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.
Once connected, ask your agent something like: .
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring CommPeak by hand means learning two separate auth schemes, hitting distinct hosts for dialler, SMS, and HLR, and reconciling call and billing records yourself. Through Jentic you install Jentic One once, add either CommPeak API from the Jentic directory, store each credential once, and your agent calls both.
Permission scoping
CommPeak sends target numbers, campaign details, and message bodies in request bodies, so your own rules in Jentic One decide which operations each agent may call. You can allow HLR lookups, billing reads, or SMS status checks while leaving outbound dialling and message sending out unless you add them.
Credential isolation
Both the main API bearer token and the SMS Streams API key are stored encrypted by your own Jentic One instance and injected only at execution time. Neither credential enters the agent's prompt, logs, or context.
FAQs
Specific to using CommPeak APIs through Jentic.
What can an AI agent do across CommPeak's APIs?
An agent can run outbound dialler campaigns, manage leads and do-not-call lists, place click-to-call sessions, send single or batched SMS, validate phone numbers with HLR lookup, and pull call detail records and billing rate cards. The main CommPeak API covers the full voice and messaging stack, while the SMS Streams API is a focused surface for sending SMS and checking delivery status.
How are the two CommPeak APIs different?
The main CommPeak API is a broad 39-endpoint surface spanning dialler, cloud voice, SMS via TextPeak, HLR lookup, and billing. The SMS Streams API is a two-endpoint SMS-only service for sending messages and checking delivery status, meant for teams that want a thin send-and-check loop without the dialler or billing complexity.
Which API should an agent use to send an SMS?
Use SMS Streams when the task is only sending a message or an OTP and confirming delivery, since it is smaller and simpler. Use the main CommPeak API when the SMS is part of a larger flow that also touches calls, campaigns, HLR lookups, or billing, so a single integration covers the whole motion.
Do both CommPeak APIs share one credential?
BOOK A DEMO
Start Connecting APIs to Your AI Agents
Browse thousands of APIs and connect them all to your agent with Jentic One. One layer, one credential — every API your agent needs.
