Install Jentic One Beta

Connect the NLP Cloud API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the NLP Cloud 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%2Fnlpcloud.io%2Fnlp-cloud" | 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%2Fnlpcloud.io%2Fnlp-cloud" | 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 NLP Cloud API.

Generate completions or chat responses from any selected model via /{model}/generation or /{model}/chatbot

Classify text into custom labels and detect intents through /{model}/classification and /{model}/intent-classification

Extract named entities, keywords, and dependencies from a passage in a single call

Produce embeddings for semantic search and retrieve top-k matches from an in-request corpus

GET STARTED

Start building with NLP Cloud API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use NLP Cloud API for, with concrete tasks.

★ Multilingual Content Pipeline

Marketing and support teams need to translate, summarize, and rewrite content across languages without standing up a separate model stack for each task. The NLP Cloud per-model endpoints expose translation, summarization, paraphrasing, and grammar correction as parallel calls so a single workflow can transform an English brief into French ad copy with a localized summary. EU-hosted models keep the data within GDPR boundaries.

Call /{model}/translation with source 'en', target 'fr' and the input text, then pass the result to /{model}/summarization to produce a 2-sentence French summary

Semantic Search over Internal Docs

Building retrieval-augmented agents requires reliable embeddings and a fast classification step to route queries. The /{model}/embeddings endpoint produces vectors for documents and queries, while /{model}/semantic-search returns ranked matches over a passed-in corpus. Combined with /{model}/intent-classification, a customer-support agent can route a question to the right knowledge base before fetching the top passages.

Generate embeddings for a list of FAQ entries via /{model}/embeddings, then call /{model}/semantic-search with the user query and the corpus to return the top 3 matches

Voice-Enabled Assistant

Voice-driven agents need both accurate transcription and natural-sounding playback. NLP Cloud's /{model}/asr endpoint transcribes audio and /{model}/speech-synthesis renders text to speech using selectable voice models. With the same auth and request shape, a single agent can capture user audio, transcribe, reason over the text, and reply in voice without integrating two vendors.

Send an audio URL to /{model}/asr, take the transcript and pass it to /{model}/generation to draft a reply, then call /{model}/speech-synthesis to render the reply

AI Agent NLP Toolbelt

An LLM-powered agent often needs lightweight NLP tasks - entity extraction, language detection, classification - without invoking a full LLM call for each. Through Jentic, the agent searches for 'extract named entities from text', receives the NLP Cloud operation schema, and runs it as a fast, deterministic step in its toolchain. The bearer token stays in your Jentic One instance and never enters the agent's context.

Use Jentic to call /{model}/entities with a customer email body and parse the returned entity spans into a structured ticket

Key Endpoints

23 endpoints — jentic publishes the only available openapi specification for nlp cloud api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/{model}/generation

Generate text from a prompt with the selected model

POST

/{model}/chatbot

Run a chat-style turn with conversation history

POST

/{model}/embeddings

Generate vector embeddings for input text

POST

/{model}/semantic-search

Rank a passed-in corpus against a query

POST

/{model}/entities

Extract named entities from text

POST

/{model}/translation

Translate text between supported languages

POST

/{model}/asr

Transcribe audio to text

POST

/{model}/speech-synthesis

Synthesize speech audio from text

POST

/{model}/generation

Generate text from a prompt with the selected model

POST

/{model}/chatbot

Run a chat-style turn with conversation history

POST

/{model}/embeddings

Generate vector embeddings for input text

POST

/{model}/semantic-search

Rank a passed-in corpus against a query

POST

/{model}/entities

Extract named entities from text

POST

/{model}/translation

Translate text between supported languages

POST

/{model}/asr

Transcribe audio to text

POST

/{model}/speech-synthesis

Synthesize speech audio from text

Why Jentic?

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

Setup

Wiring NLP Cloud by hand means handling its bearer auth, selecting the model in each path (https://api.nlpcloud.io/v1/{model}/...), and shaping each inference request yourself. Through Jentic you install once, import the NLP Cloud API from the API Directory, store the token once, and your agent calls it.

Permission scoping

NLP Cloud selects the model in the path but sends the work through the request body, so scope by operation: limit the agent to the operations it needs, such as text generation, embeddings, or translation, and leave out speech synthesis or transcription unless you add them. You choose the operations it may call.

Credential isolation

Your NLP Cloud 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 'generate text with a model' or 'create embeddings for a passage', and Jentic returns the matching NLP Cloud operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using NLP Cloud API through Jentic.

Why is there no official OpenAPI spec for NLP Cloud API?

NLP Cloud does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call NLP Cloud API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does the NLP Cloud API use?

NLP Cloud uses HTTP bearer authentication. Pass your API token from the NLP Cloud dashboard in the Authorization header as 'Bearer <token>'. Through Jentic the token sits encrypted in the vault and the agent receives only a scoped reference.

Can I run a custom fine-tuned model with the NLP Cloud API?

Yes. Every endpoint is parameterized by a {model} path segment. Pass the slug of your fine-tuned model (for example a custom LLaMA variant) and the request shape stays identical to the pretrained equivalent.

What are the rate limits for the NLP Cloud API?

Limits depend on the subscribed plan and selected model - typically tens to hundreds of requests per minute. The spec does not declare hard limits; check the NLP Cloud pricing page for current per-plan numbers, and Jentic will surface 429 responses with backoff.

How do I generate text with the NLP Cloud API through Jentic?

Run pip install jentic, then search Jentic for 'generate text from a prompt'. Jentic returns the /{model}/generation operation; load the schema, fill in the model slug and prompt, and execute. The bearer token is injected by Jentic at call time.

Does NLP Cloud support image generation?

Yes. The /{model}/image-generation endpoint accepts a prompt and returns generated images using the selected image model. Use it alongside text-to-text endpoints in the same workflow without changing auth or request structure.

Can I limit what my agent is allowed to do with the NLP Cloud API?

Yes. Because you self-host Jentic One, your own rules decide which NLP Cloud operations and credentials the agent may use. Since NLP Cloud selects the model in the path but carries the actual work in the request body, you scope by operation: allow only the endpoints the agent needs, such as text generation, embeddings, or translation, and leave out speech synthesis or transcription unless you add them. The agent can call only the operations you have permitted.

NLP Cloud API

Name: NLP Cloud API
Brand: NLP Cloud API
Availability: InStock

Agent-ready OpenAPI document · curated by JenticAI/MLLanguage Modelsbearer23 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Run NLP and generative AI inference - text generation, classification, summarization, embeddings, ASR, and image generation - through a uniform per-model REST surface.

Use for: I need to generate a paragraph of text from a prompt, Summarize a long document into a short paragraph, Extract named entities from a news article, Translate a passage from English to French

Not supported: Does not handle model training infrastructure, vector database hosting, or LLM evaluation tooling - use for hosted NLP and generative inference only.

Jentic publishes the only available OpenAPI specification for NLP Cloud API, keeping it validated and agent-ready. NLP Cloud serves pretrained and custom models for text generation, classification, summarization, paraphrasing, named entity recognition, embeddings, semantic search, speech-to-text, and image generation behind a uniform per-model REST surface. Each operation is parameterized by a model slug, so an agent can swap between models like dolphin, fine-tuned LLaMA variants, or custom fine-tunes without changing the call shape. Both general-purpose and language-specific models are exposed, with GDPR-compliant inference hosted in the EU and US.

Jentic One on Github View OpenAPI Document

Connect the NLP Cloud API to your agent

Capabilities

Start building with NLP Cloud API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

NLP Cloud API