Install Jentic One Beta

Connect the Voiso Contact Center API to your agent

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

List users

Initiate outbound call

Stop outbound call

Schedule callback

Send SMS message

Use Cases

GET STARTED

Start building with Voiso Contact Center API

Explore with Jentic One

View OpenAPI Document

Automated Campaigns Management

Automate campaigns operations by combining multiple Voiso Contact Center API endpoints. Agents can list deleted users and then list teams in a single workflow.

Call GET /users/deleted to list deleted users, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Voiso Contact Center 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, bearer tokens manually.

Search Jentic for 'list users', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

24 endpoints — voiso api for contact center operations including voice, messaging, campaigns, and monitoring.

METHOD

PATH

DESCRIPTION

GET

/users

List users

GET

/users/deleted

List deleted users

GET

/teams

List teams

POST

/click2call/start

Initiate outbound call

POST

/click2call/stop

Stop outbound call

POST

/callback/schedule

Schedule callback

POST

/sms/send

Send SMS message

GET

/sms/templates

Retrieve SMS templates

GET

/users

List users

GET

/users/deleted

List deleted users

GET

/teams

List teams

POST

/click2call/start

Initiate outbound call

POST

/click2call/stop

Stop outbound call

POST

/callback/schedule

Schedule callback

POST

/sms/send

Send SMS message

GET

/sms/templates

Retrieve SMS templates

Why Jentic?

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

Setup

Wiring Voiso by hand means choosing the right per-cluster host ({cluster_id}.voiso.com), setting its X-API-Key or JWT bearer token, and managing the calls yourself. Through Jentic you install once, import Voiso Contact Center from the API Directory, store the credential once, and your agent calls it.

Permission scoping

Voiso carries its targets in request parameters and bodies rather than the URL path, so limit the agent to the operations it needs, such as listing users or sending an SMS. You choose the allowed set, so operations like stopping a click-to-call are not included unless you add them.

Credential isolation

Your Voiso API key or 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 'list users' or 'send an SMS', and Jentic returns the matching Voiso operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Voiso Contact Center API through Jentic.

What authentication does the Voiso Contact Center API use?

The Voiso Contact Center API uses apiKey, bearer authentication. 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 users with the Voiso Contact Center API?

Yes. Use the GET /users endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the Voiso Contact Center 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 users through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'list users'. Jentic returns the matching Voiso Contact Center API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the Voiso Contact Center API have?

The Voiso Contact Center API exposes 24 endpoints covering campaigns, contact center operations, messaging operations.

Can I limit what my agent is allowed to do with the Voiso Contact Center API?

Yes. Jentic One is self-hosted by you, so your own rules decide which Voiso operations and credentials the agent may use. Because Voiso carries its targets in request parameters and bodies rather than the URL path, you scope the agent to just the operations it needs, such as listing users or sending an SMS. Operations like initiating or stopping a click-to-call outbound call are not available to the agent unless you add them to the allowed set.

Voiso Contact Center API

AI ReadinessAI-Aware (B)65/100

See full scorecard

Official vendor OpenAPI document · agent-readyCRMContact ManagementapiKey, bearer24 EndpointsREST

For Agents

Programmatically list users, list deleted users. Covers 24 operations with apiKey, bearer authentication.

Use for: I need to users, I want to deleted users, Search for teams, Find all initiate outbound call

Not supported: Does not handle payments, communications, or developer tools - use for crm only.

Voiso API for contact center operations including voice, messaging, campaigns, and monitoring. The API exposes 24 endpoints secured with apiKey, bearer authentication.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

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).

21%

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: C-Signals: 4

51%

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.

53%

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

65%

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

63%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Voiso Contact Center API to your agent

Capabilities

Use Cases

Start building with Voiso Contact Center API

Key Endpoints

Why Jentic?

Related APIs

FAQs

Voiso Contact Center API

Jentic AI Readiness Score

Voiso Contact Center 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