Install Jentic One Beta

Connect the TextKit API to your agent

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

Health check

Detect emotion in text

Integrate TextKit API into automated workflows

Query and filter TextKit API records by parameters

Monitor TextKit API operational status and events

GET STARTED

Start building with TextKit API

Explore with Jentic One

View OpenAPI Document

Automated Detection Management

Automate detection operations by combining multiple TextKit API endpoints. Agents can detect emotion in text and then detect sentiment in text in a single workflow.

Call GET /detect/emotion to detect emotion in text, then verify the result

AI Agent Integration via Jentic

AI agents discover and call TextKit 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 tokens manually.

Search Jentic for 'health check', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

9 endpoints — textkit is a text analysis api offering natural language processing endpoints including emotion detection, sentiment analysis, language detection, gender prediction, gibberish detection, name recognition, sentence similarity, and word cloud generation.

METHOD

PATH

DESCRIPTION

GET

/ping

Health check

GET

/detect/emotion

Detect emotion in text

GET

/detect/sentiment

Detect sentiment in text

GET

/detect/language

Detect language of text

GET

/detect/gender

Detect gender from name

GET

/detect/gibberish

Detect gibberish in text

GET

/detect/names

Detect names in text

GET

/detect/similarity

Compute sentence similarity

GET

/ping

Health check

GET

/detect/emotion

Detect emotion in text

GET

/detect/sentiment

Detect sentiment in text

GET

/detect/language

Detect language of text

GET

/detect/gender

Detect gender from name

GET

/detect/gibberish

Detect gibberish in text

GET

/detect/names

Detect names in text

GET

/detect/similarity

Compute sentence similarity

Why Jentic?

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

Setup

Wiring TextKit by hand means setting up its API-key auth against api.textkit.ai and wiring each text-detection endpoint yourself. Through Jentic you install once, import TextKit from the API Directory, store the key once, and your agent calls it.

Permission scoping

TextKit passes the text to analyse as a request parameter on read-only detection endpoints like /detect/sentiment and /detect/language, so limit the agent to the operations it needs, such as sentiment or language detection. You choose that set, so an operation is only reachable if you include it.

Credential isolation

Your TextKit 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 'detect the sentiment of this text' or 'identify the language', and Jentic returns the matching TextKit operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using TextKit API through Jentic.

What authentication does the TextKit API use?

The TextKit API uses an API key passed in the `X-API-Key` header. 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 health check with the TextKit API?

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

What are the rate limits for the TextKit 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 health check through Jentic?

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

How many endpoints does the TextKit API have?

The TextKit API exposes 9 endpoints covering detection, generation, utility operations.

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

Yes. Because you run Jentic One yourself, you decide which TextKit operations your agent can reach, and an endpoint is only callable if you include it in that set. TextKit exposes read-only detection endpoints such as /detect/sentiment and /detect/language, so you can restrict the agent to just the operations it needs, like sentiment or language detection, while leaving the rest unavailable. Your own rules govern which operations and which stored credentials the agent may use.

TextKit API

Name: TextKit API
Brand: TextKit API
Availability: InStock

Official vendor OpenAPI document · agent-readyAI/MLLanguage ModelsapiKey9 EndpointsREST

For Agents

Programmatically health check, detect emotion in text. Covers 9 operations with apiKey authentication.

Use for: I need to health check, I want to detect emotion in text, Search for detect sentiment in text, Find all detect language of text

Not supported: Does not handle payments, communications, or crm - use for ai and machine learning only.

TextKit is a text analysis API offering natural language processing endpoints including emotion detection, sentiment analysis, language detection, gender prediction, gibberish detection, name recognition, sentence similarity, and word cloud generation. The API exposes 9 endpoints secured with apiKey authentication.

Jentic One on Github View OpenAPI Document

Connect the TextKit API to your agent

Capabilities

Start building with TextKit API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

TextKit API