Install Jentic One Beta

Connect the Inworld Public API to your agent

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

Synthesize speech from text with a chosen voiceId and modelId

Stream synthesized speech for low-latency playback

List the voices available to the account

Clone a voice from reference audio

Transcribe audio to text

GET STARTED

Start building with Inworld Public API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Inworld Public API for, with concrete tasks.

★ AI agent that speaks its replies

A developer's agent connected through Jentic finds the Inworld text-to-speech operation by intent and calls it with the API key injected at execution time. It picks a voice from the voice list, sends its reply text, and returns audio, so a chat assistant can answer out loud without the key entering the agent's context.

Call GET /voices/v1/voices, pick a voice, then POST /tts/v1/voice with text 'Your order has shipped and arrives Thursday.' and that voiceId

Voice cloning for a branded character

Games and branded assistants often need a consistent custom voice. Inworld can clone a voice from reference audio, after which the cloned voice appears in the voice list and can be used for synthesis and streaming like any built-in voice.

POST /voices/v1/voices:clone with reference audio, then confirm the new voice appears in GET /voices/v1/voices

Transcribing recorded audio

Support teams and note-taking tools need text from recordings. The transcription endpoint converts audio to text, and the chat completions endpoint can then summarise or classify the transcript through the same Inworld account.

POST /stt/v1/transcribe with a recorded call, then POST /v1/chat/completions asking for a three-line summary of the transcript

Key Endpoints

7 endpoints — the inworld public api turns text into speech with inworld voices, either as a single synthesis request or as a stream, and transcribes audio back to text.

METHOD

PATH

DESCRIPTION

POST

/tts/v1/voice

Synthesize speech from text

POST

/tts/v1/voice:stream

Stream synthesized speech

GET

/voices/v1/voices

List available voices

POST

/voices/v1/voices:clone

Clone a voice

POST

/stt/v1/transcribe

Transcribe audio to text

POST

/v1/chat/completions

OpenAI-compatible chat completions

POST

/tts/v1/voice

Synthesize speech from text

POST

/tts/v1/voice:stream

Stream synthesized speech

GET

/voices/v1/voices

List available voices

POST

/voices/v1/voices:clone

Clone a voice

POST

/stt/v1/transcribe

Transcribe audio to text

POST

/v1/chat/completions

OpenAI-compatible chat completions

Why Jentic?

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

Setup

Wiring Inworld by hand means sending the API key in the Authorization header with a Basic prefix but without the usual base64 encoding, and handling separate synthesis, streaming, and transcription routes. Through Jentic you install once, import Inworld from the API Directory, store the key once, and your agent calls it.

Permission scoping

Inworld carries the text, voice, and audio in the request body, so rules bound which operations your agent may call rather than which voice it uses. You choose the operations it may call, so voice cloning or realtime session creation are not included unless you add them.

Credential isolation

Your Inworld 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 'convert text to speech' or 'transcribe audio', and Jentic returns the matching Inworld operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Inworld Public API through Jentic.

What authentication does the Inworld Public API use?

Per its OpenAPI spec, Inworld uses an API key sent in the `Authorization` header in the exact format Basic followed by the key. The key is sent as a raw value and must not be base64-encoded as username:password credentials. Through Jentic the key is stored by your own instance and attached at call time.

Can I stream text to speech with the Inworld API?

Yes. POST /tts/v1/voice returns synthesized speech for a text input, and POST /tts/v1/voice:stream streams the synthesized speech so playback can start before the whole clip is ready. GET /voices/v1/voices lists the voices you can pass as voiceId.

What are the rate limits for the Inworld Public API?

The OpenAPI spec does not specify rate limits. Check the Inworld documentation at https://docs.inworld.ai for current limits.

Is there an Inworld MCP server?

You don't need an MCP server to give your agent Inworld. Jentic connects it directly from the API Directory: import it, store your API key once, and your agent calls the speech, voice, and transcription operations it needs, discovered on demand rather than loaded into its context.

Can I limit what my agent is allowed to do with Inworld?

Yes. For example, write a rule that allows only POST /tts/v1/voice and GET /voices/v1/voices, so the agent can speak with existing voices but cannot clone new voices or open realtime sessions, and every call it makes is logged.

How do I synthesize speech through Jentic?

Import the Inworld Public API from the Jentic API Directory and store your API key once. Your agent searches for 'convert text to speech', gets POST /tts/v1/voice with its schema, and sends the required text plus a voiceId. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Inworld Public API

AI ReadinessFoundational (D+)47/100

See full scorecard

Official vendor OpenAPI document · agent-readyAI/MLSpeechapiKey7 EndpointsREST

For Agents

Synthesize or stream speech from text with Inworld voices, transcribe audio, clone a voice, call OpenAI-compatible chat completions, and open realtime WebRTC sessions.

Use for: I need to turn this paragraph into spoken audio, List all voices I can use for text to speech, Stream speech for a reply as it is generated, Clone a voice from a reference recording

Not supported: Does not handle music generation, video dubbing, or telephony call routing. Use for Inworld speech synthesis, transcription, voices, chat completions, and realtime sessions only.

The Inworld Public API turns text into speech with Inworld voices, either as a single synthesis request or as a stream, and transcribes audio back to text. It lists the voices available to an account and clones a new voice from reference audio. Alongside the speech surface it exposes an OpenAI-compatible chat completions endpoint and creates realtime WebRTC sessions for live voice conversations.

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

41%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

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

62%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Inworld Public API to your agent

Capabilities

Start building with Inworld Public API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Inworld Public API

Jentic AI Readiness Score

Inworld Public 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