Install Jentic One Beta

Connect the cvoice.ai API to your agent

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

Generate AI voice audio from text with a chosen voice ID

Search more than 20,000 characters and their metadata in the public characters dataset

Browse voice IDs grouped by character in the public voices dataset

Read the information tied to your API key

Use Cases

Patterns agents use cvoice.ai API for, with concrete tasks.

GET STARTED

Start building with cvoice.ai API

Explore with Jentic One

View OpenAPI Document

Voice discovery

Choosing the right voice means browsing what is available. The cvoice.ai API publishes a characters dataset with metadata and a voices dataset grouping voice IDs by character, so a tool can present options and let a user or agent select before any audio is generated. Both datasets are public and need no key to read.

Load the characters dataset and the voices dataset and present the matching voice IDs for a chosen character

Script-to-audio pipeline

An app that converts written scripts into audio can call the generation endpoint for each line with a consistent voice ID. Keeping the same voice ID across calls produces a continuous narration, and the key-info endpoint lets the pipeline confirm the key is active before a long run.

Generate audio for each line of a script using one voice ID to keep the narration consistent

Key Endpoints

4 endpoints — the cvoice.

METHOD

PATH

DESCRIPTION

POST

/api/tts

Generate AI voice audio from text for a chosen voice ID

GET

/api/me

Read the information tied to your API key

GET

/dataset_search.json

Public characters dataset with metadata

GET

/dataset_voices.json

Public voices dataset grouped by character

POST

/api/tts

Generate AI voice audio from text for a chosen voice ID

GET

/api/me

Read the information tied to your API key

GET

/dataset_search.json

Public characters dataset with metadata

GET

/dataset_voices.json

Public voices dataset grouped by character

Why Jentic?

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

Setup

Wiring the cvoice.ai API by hand means handling its X-API-Key header auth, resolving a voice ID from the public datasets, and distinguishing keyed generation from the open dataset reads yourself. Through Jentic you install once, import cvoice from the API Directory, store the key once, and your agent calls it.

Permission scoping

The voice ID and text travel in the request body, not the URL path, so a rule bounds which operations your agent may call rather than which voice it uses. You choose the operations it may call, such as voice generation, so reading your key information is not included unless you add it.

Credential isolation

Your cvoice 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 'generate voice audio from text' or 'find a voice ID', and Jentic returns the matching cvoice operation with its input schema so the agent calls the right endpoint without reading the reference docs.

FAQs

Specific to using cvoice.ai API through Jentic.

What authentication does the cvoice.ai API use?

The cvoice.ai API authenticates with an API key sent in the X-API-Key header, prefixed cvai_, as declared in its OpenAPI spec. The two public voice datasets need no key to read. Through Jentic the key is stored once and injected at call time, so it never appears in your agent's prompt or logs.

How do I find a voice ID for the cvoice.ai API?

Read the public datasets: the characters dataset lists more than 20,000 characters with metadata, and the voices dataset groups voice IDs by character. An agent resolves a character to a voice ID from these before calling the generation endpoint.

What are the rate limits for the cvoice.ai API?

The spec describes cvoice.ai as a free API with no usage limits, and does not state numeric rate limits. Check the vendor documentation at https://cvoice.ai for current terms before running large batches.

How do I generate voice audio through Jentic with the cvoice.ai API?

Search Jentic for 'generate voice audio from text', which returns the POST /api/tts operation with its input schema, then call it with the text and a voice ID. 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 cvoice.ai API?

Yes. Write a rule that allows only the voice-generation operation, so the agent can turn text into audio but cannot read your key information, and every call it makes is logged. The voice ID and text travel in the request body, so the rule bounds which operations run rather than which voice is used.

cvoice.ai API

AI ReadinessAI-Aware (A-)71/100

See full scorecard

Official vendor OpenAPI document · agent-readyAI/MLSpeechapiKey4 EndpointsREST

For Agents

Generate AI voice audio from text using any of 20,000+ character voices, and look up voice IDs from the public character and voice datasets.

Use for: Generate speech from text in a specific voice, Find a voice ID for a character, Search the voice catalog for a character, List the voices available for a character

Not supported: Does not handle speech-to-text, music generation, or audio hosting. Use for text-to-speech voice generation only.

The cvoice.ai API generates AI voice audio from text using a catalog of more than 20,000 character voices. A single generation call turns text into audio for a chosen voice ID, and two public datasets list the available characters and their voice IDs so callers can pick a voice before generating. An endpoint also returns the information tied to your API key.

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

99%

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

28%

Example Density

How richly the API is illustrated with examples.

90%

Example Validity

Percentage of examples that conform to their schemas.

50%

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

62%

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.

73%

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

50%

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

81%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the cvoice.ai API to your agent

Capabilities

Use Cases

Start building with cvoice.ai API

Key Endpoints

Why Jentic?

Related APIs

FAQs

cvoice.ai API

Jentic AI Readiness Score

cvoice.ai 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