Install Jentic One Beta

Connect the Cloudmersive Natural Language Processing API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Cloudmersive Natural Language Processing 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%2Fapi.cloudmersive.com%2Fcloudmersive" | 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%2Fapi.cloudmersive.com%2Fcloudmersive" | 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 Cloudmersive Natural Language Processing API.

Score sentiment, profanity, hate speech, and subjectivity for arbitrary input text

Extract named entities (people, organisations, places) and detect language from text

Translate text between English and German, French, Russian, and other major languages

Compare two strings for semantic similarity to power deduplication or matching workflows

GET STARTED

Start building with Cloudmersive Natural Language Processing API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Cloudmersive Natural Language Processing API for, with concrete tasks.

★ User-Generated Content Moderation

Filter user comments, reviews, or chat messages for profanity and hate speech before they reach other users. The agent calls POST /nlp-v2/analytics/profanity and POST /nlp-v2/analytics/hate-speech with the message body and inspects the boolean and score fields. Combine with a sentiment call to flag unusually negative content for human review.

Call POST /nlp-v2/analytics/profanity with a comment body and reject the post when the returned score exceeds 0.5.

Multilingual Customer Support Triage

When tickets arrive in mixed languages, detect each ticket's language and translate it to the support team's working language. The agent first calls POST /nlp-v2/language/detect, then routes English/German/French content to the matching translate endpoint such as /nlp-v2/translate/language/deu/to/eng. Sentiment scoring on the translated text helps escalate angry customers first.

Call POST /nlp-v2/language/detect on the ticket body, then POST /nlp-v2/translate/language/{src}/to/eng to translate it before assigning to the English queue.

Review Sentiment Aggregation

Score customer reviews in bulk to produce a sentiment trend by product or service. The agent posts each review to /nlp-v2/analytics/sentiment, stores the score and label, and rolls up the daily averages into a dashboard. Pair with /nlp-v2/extract-entities to break out which features are mentioned most often.

Call POST /nlp-v2/analytics/sentiment for each new review and write the score plus product ID to BigQuery.

Agent-Driven Text Analysis via Jentic

Connect Cloudmersive NLP to an AI agent through Jentic so a workflow can ask 'is this comment offensive?' or 'what language is this?' as a single tool call. The agent searches Jentic for the right Cloudmersive operation, loads the schema, and posts the text with the API key kept in your Jentic One instance. The Apikey header value never enters the agent's prompt.

Use the Jentic Python SDK to search for 'detect profanity in text', load POST /nlp-v2/analytics/profanity, and execute it on a candidate comment.

Key Endpoints

25 endpoints — jentic publishes the only available openapi specification for cloudmersive natural language processing api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/nlp-v2/analytics/sentiment

Analyse sentiment of text

POST

/nlp-v2/analytics/profanity

Detect profanity in text

POST

/nlp-v2/analytics/hate-speech

Detect hate speech in text

POST

/nlp-v2/analytics/similarity

Compare semantic similarity of two texts

POST

/nlp-v2/extract-entities

Extract named entities from text

POST

/nlp-v2/language/detect

Detect the language of input text

POST

/nlp-v2/translate/language/eng/to/deu

Translate English to German

POST

/nlp-v2/analytics/sentiment

Analyse sentiment of text

POST

/nlp-v2/analytics/profanity

Detect profanity in text

POST

/nlp-v2/analytics/hate-speech

Detect hate speech in text

POST

/nlp-v2/analytics/similarity

Compare semantic similarity of two texts

POST

/nlp-v2/extract-entities

Extract named entities from text

POST

/nlp-v2/language/detect

Detect the language of input text

POST

/nlp-v2/translate/language/eng/to/deu

Translate English to German

Why Jentic?

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

Setup

Wiring the Cloudmersive NLP API by hand means handling its Apikey header and mapping the sentiment, entity, language, and translation routes yourself. Through Jentic you install once, import Cloudmersive NLP from the API Directory, store the key once, and your agent calls it.

Permission scoping

Cloudmersive NLP addresses each analysis through the request body rather than resource ids in the URL path, so you limit the agent to the operations it needs, such as sentiment scoring or language detection. Operations like translation are separate and are only available if you include them in the allowed set.

Credential isolation

Your Cloudmersive Apikey is stored once, encrypted, by your own Jentic One instance and injected as the header at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'detect profanity' or 'translate text', and Jentic returns the matching Cloudmersive operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Cloudmersive Natural Language Processing API through Jentic.

Why is there no official OpenAPI spec for Cloudmersive Natural Language Processing API?

Cloudmersive publishes interactive HTML reference docs but does not host a single canonical OpenAPI specification for the NLP v2 product. Jentic generates and maintains this spec so that AI agents and developers can call Cloudmersive Natural Language Processing 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 Cloudmersive NLP API use?

The API uses an API key in the Apikey header on every request. You generate the key from the Cloudmersive account dashboard. Through Jentic, the Apikey value is stored encrypted in the vault and only scoped tokens reach the agent's context.

Can I detect hate speech in text with Cloudmersive NLP?

Yes. POST the text to /nlp-v2/analytics/hate-speech and Cloudmersive returns a hate-speech probability and a boolean classification. Pair it with /nlp-v2/analytics/profanity for layered comment moderation.

What are the rate limits for the Cloudmersive NLP API?

Cloudmersive applies a per-account monthly quota that depends on your plan; free tiers cap at a few hundred calls per month, paid tiers scale into the millions. Per-second throttling is in place to prevent burst overload - when running through Jentic, watch 429 responses.

How do I translate text between English and German via Jentic?

Search Jentic for 'translate text english to german' and the POST /nlp-v2/translate/language/eng/to/deu Cloudmersive operation is returned with its body schema. Load the operation, then execute it with the source string. The standard quickstart is pip install jentic, search, load, execute.

Is the Cloudmersive NLP API free?

Cloudmersive offers a free tier with a monthly call quota suitable for evaluation; paid plans raise the quota and unlock higher concurrency. There is no trial expiry on the free tier as long as you stay within the monthly cap.

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

Yes. Because Cloudmersive NLP selects each analysis through the request body rather than resource ids in the URL path, your self-hosted Jentic One instance lets you allow only the operations the agent actually needs, such as sentiment scoring at /nlp-v2/analytics/sentiment or language detection at /nlp-v2/language/detect. Separate operations like translation at /nlp-v2/translate/language/eng/to/deu are reachable only when you add them to the allowed set. Your own rules decide which endpoints and which Apikey credential the agent may use, so it cannot call anything outside that scope.

Cloudmersive Natural Language Processing API

AI ReadinessAI-Aware (B+)67/100

See full scorecard

Agent-ready OpenAPI document · curated by JenticAI/MLMl InferenceapiKey25 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Run sentiment, profanity, hate-speech, similarity, entity-extraction, language-detection, translation, and spell-check operations on text via simple POST endpoints.

Use for: Score the sentiment of a customer review, Detect profanity in a user-submitted comment, Detect hate speech in a forum post, Find the language of a piece of text

Not supported: Does not handle large language model chat completion, embeddings, or speech-to-text - use for fixed-purpose NLP scoring, translation, and text-cleanup endpoints only.

Jentic publishes the only available OpenAPI specification for Cloudmersive Natural Language Processing API, keeping it validated and agent-ready. Cloudmersive's NLP v2 API provides ready-made text analysis endpoints - sentiment analysis, profanity and hate-speech detection, subjectivity scoring, semantic similarity, named-entity extraction, language detection, machine translation between English and several major languages, parsing, part-of-speech tagging, rephrasing, segmentation, and spell checking. Each endpoint is a simple POST that accepts a JSON body of text and returns a structured result, with no model training or hosting required by the caller.

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

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

Example Density

How richly the API is illustrated with examples.

100%

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: D+Signals: 4

48%

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.

50%

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

100

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A+Signals: 1

100%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Cloudmersive Natural Language Processing API to your agent

Capabilities

Start building with Cloudmersive Natural Language Processing API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Cloudmersive Natural Language Processing API

Jentic AI Readiness Score

Cloudmersive Natural Language Processing 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