canonical: https://jentic.com/apis/textkit.ai/textkit

# TextKit API

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.

## For AI agents

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

## Scope

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

## Capabilities

- 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

## Use cases

### AI and Machine Learning Operations

Use the TextKit API to perform ai ml operations programmatically. The API provides 9 endpoints covering core functionality including health check, detect emotion in text, detect sentiment in text.

Example prompt: Call GET /ping to health check

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

Example prompt: 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.

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

## Key endpoints

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

## Key resources

- **Detection** — Operations related to Detection
- **Generation** — Operations related to Generation
- **Utility** — Operations related to Utility

## Why Jentic

- **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 handling:** 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.
- **Discovery method:** 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.

## Related APIs

- **Openai** — Alternative ai ml API
- **Anthropic** — Alternative ai ml API
- **Cohere** — Complementary ai ml API
- **Huggingface** — Complementary ai ml API

## FAQ

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