Install Jentic One Beta

Connect the HMS Sovereign API to your agent

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

Create and configure AI voice assistants and update their settings

Place outbound calls and list call records with their status

Send control commands to an active call

Run outbound campaigns and manage the leads attached to them

GET STARTED

Start building with HMS Sovereign API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use HMS Sovereign API for, with concrete tasks.

★ Outbound Voice Campaign

Run an automated calling campaign against a list of leads so each one is dialed by a configured voice assistant. The API creates a campaign, attaches leads to it, and places outbound calls from registered numbers. Sales and support teams use this to drive outbound phone outreach without a human dialing each number.

Create a campaign with POST /campaigns, add leads with POST /campaigns/{id}/leads, then place calls with POST /calls/outbound.

Live Call Control

Act on a call while it is in progress, for example transferring or ending it based on what the conversation needs. The API lists calls and sends control commands to a specific active call by id. Operations teams use this to steer live calls from an external system rather than only reviewing them afterward.

List active calls with GET /calls, then POST /calls/{id}/control to transfer or end a specific call.

Voice Assistant Provisioning

Stand up a new voice assistant and the phone number it answers on in one flow, instead of configuring them in separate places. The API creates an assistant with its settings and registers a phone number for the organization. Builders use this to provision calling capacity programmatically as they onboard new use cases.

POST /assistants to create a voice assistant, then POST /numbers to register a phone number for the organization.

Agent-Orchestrated Calling

An AI agent sets up and places a phone call without a hand-built telephony client. Through Jentic the agent discovers the assistant, number, and call operations, loads their schemas, and chains them to dial a target. This lets an assistant initiate and track outbound calls directly from a higher-level task.

Search Jentic for 'place an outbound call', create an assistant with POST /assistants, register a number with POST /numbers, and dial with POST /calls/outbound.

Key Endpoints

74 endpoints — the hms sovereign api manages ai voice agents end to end: it creates and configures assistants, registers phone numbers, places and controls outbound calls, and runs lead campaigns across them.

METHOD

PATH

DESCRIPTION

GET

/assistants

List all assistants

POST

/assistants

Create a new assistant

POST

/calls/outbound

Initiate an outbound call

GET

/calls

List calls

POST

/calls/{id}/control

Send a control command to an active call

GET

/numbers

List all phone numbers

POST

/numbers

GET

/campaigns

List all campaigns

GET

/assistants

List all assistants

POST

/assistants

Create a new assistant

POST

/calls/outbound

Initiate an outbound call

GET

/calls

List calls

POST

/calls/{id}/control

Send a control command to an active call

GET

/numbers

List all phone numbers

POST

/numbers

GET

/campaigns

List all campaigns

Why Jentic?

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

Setup

Wiring HMS Sovereign by hand means handling its bearer auth, provisioning numbers, and sequencing the assistant, number, and call operations yourself. Through Jentic you install once, import HMS Sovereign from the API Directory, store the token once, and your agent calls those operations in order.

Permission scoping

HMS Sovereign puts the assistant and call id in the URL path, such as /assistants/{id} and /calls/{id}/control, so a rule can pin your agent to one assistant's operations. You choose the operations it may call, so destructive ones like deleting a number or ending a call are not included unless you add them.

Credential isolation

Your HMS Sovereign bearer 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 'place an outbound call' or 'create a voice assistant', and Jentic returns the matching HMS Sovereign operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using HMS Sovereign API through Jentic.

Is there an HMS Sovereign MCP server?

You do not need an MCP server to give your agent the HMS Sovereign API. Jentic connects it directly from the API Directory: import HMS Sovereign, store your bearer token once, and your agent calls the assistant, number, and call endpoints. Operations are discovered on demand, so no extra server's tool definitions load into the agent's context.

What authentication does the HMS Sovereign API use?

The HMS Sovereign API authenticates with a bearer token in the Authorization header, per its OpenAPI spec, and each key is scoped to a specific organization. Through Jentic the token is stored encrypted by your own Jentic One instance and injected at call time, so it never enters the agent's prompt or logs.

Can I place and control calls with the HMS Sovereign API?

Yes. POST /calls/outbound initiates an outbound call, GET /calls lists call records, and POST /calls/{id}/control sends a control command to an active call. Each call is tied to an assistant you configure through the assistants endpoints.

What are the rate limits for the HMS Sovereign API?

The HMS Sovereign spec documents 100 requests per minute per API key, with call control commands limited to 10 per minute per active call. The API returns standard HTTP status codes, so treat a 429 response as the signal to back off.

How do I place an outbound call through Jentic?

Search Jentic with the query 'place an outbound call', load the schema for POST /calls/outbound, and execute it with the assistant and number to dial from. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Can I limit what my agent is allowed to do with the HMS Sovereign API?

Yes. Write a rule that allows only the read and outbound-call operations you need, such as GET /calls and POST /calls/outbound, so the agent can place and inspect calls but cannot delete assistants or numbers, and every call it makes is logged. Because assistant and call ids live in the URL path, you can confine the agent to one assistant's operations.

Hmsovereign HMS Sovereign API

AI ReadinessAI-Aware (B-)62/100

See full scorecard

Official vendor OpenAPI document · agent-readyCommunicationsVoice Telephonybearer74 EndpointsREST

For Agents

Create and configure AI voice assistants, register phone numbers, place and control outbound calls, and run lead campaigns for an organization.

Use for: Create a new voice assistant with a custom prompt, Place an outbound call from one of my numbers, Send a control command to an active call, List the calls made in the last day

Not supported: Does not send email, process payments, or host a help desk. Use for AI voice assistants, phone numbers, calls, and outbound campaigns only.

The HMS Sovereign API manages AI voice agents end to end: it creates and configures assistants, registers phone numbers, places and controls outbound calls, and runs lead campaigns across them. It also exposes SIP trunks, usage logs, and per-organization settings so a voice program can be driven programmatically. Use it to stand up and operate automated phone calling without wiring each telephony piece by hand.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: DSignals: 4

74%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

Specification Validity

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

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: BSignals: 4

17%

Example Density

How richly the API is illustrated with examples.

98%

Example Validity

Percentage of examples that conform to their schemas.

52%

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

56%

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.

68%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

90%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: B-Signals: 1

60%

Authentication Strength

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

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A-Signals: 1

79%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the HMS Sovereign API to your agent

Capabilities

Start building with HMS Sovereign API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Hmsovereign HMS Sovereign API

Jentic AI Readiness Score

HMS Sovereign API

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