Install Jentic One Beta

Connect the Tisane API Documentation to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Tisane API Documentation, 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%2Ftisane.ai%2Ftisane-api-documentation" | 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%2Ftisane.ai%2Ftisane-api-documentation" | 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 Tisane API Documentation API.

List hypernyms

Get family details

Integrate Tisane API Documentation into automated workflows

Query and filter Tisane API Documentation records by parameters

Monitor Tisane API Documentation operational status and events

GET STARTED

Start building with Tisane API Documentation API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Tisane API Documentation API for, with concrete tasks.

★ AI and Machine Learning Operations

Use the Tisane API Documentation to perform ai ml operations programmatically. The API provides 6 endpoints covering core functionality including list hypernyms, list hyponyms, list inflected forms.

Call GET /hypernyms to list hypernyms

Automated NLU / NLP Methods Management

Automate nlu / nlp methods operations by combining multiple Tisane API Documentation endpoints. Agents can list hyponyms and then list inflected forms in a single workflow.

Call GET /hyponyms to list hyponyms, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Tisane API Documentation 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 none tokens manually.

Search Jentic for 'list hypernyms', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

6 endpoints — tisane is a natural language processing library, providing: * standard nlp functionality * special functions for detection of problematic or abusive content * low-level nlp like morphological analysis and tokenization of no-space languages (chinese, japanese, thai) tisane has monolithic architecture.

METHOD

PATH

DESCRIPTION

GET

/hypernyms

List hypernyms

GET

/hyponyms

List hyponyms

GET

/inflections

List inflected forms

GET

/lm/family

Get family details

GET

/senses

List word senses

GET

/values

List feature values

GET

/hypernyms

List hypernyms

GET

/hyponyms

List hyponyms

GET

/inflections

List inflected forms

GET

/lm/family

Get family details

GET

/senses

List word senses

GET

/values

List feature values

Why Jentic?

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

Setup

Wiring the Tisane API by hand means reading its language and lexical endpoints, shaping each query, and handling retries yourself. Through Jentic you install once, import Tisane from the API Directory, and your agent calls it.

Permission scoping

Tisane serves read-only lexical lookups selected by query parameters rather than a resource id in the URL path, so scope the agent by the operations it needs, such as hypernyms or inflections. You choose that set, so lookups you do not name stay unavailable.

Credential isolation

Tisane exposes these endpoints without a credential, so there is nothing for Jentic One to store; any account key you add later is held encrypted by your own instance and injected at execution time, never in the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'find hypernyms for a word' or 'get word inflections', and Jentic returns the matching Tisane operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Tisane API Documentation API through Jentic.

What authentication does the Tisane API Documentation use?

The Tisane API Documentation uses no authentication. 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 list hypernyms with the Tisane API Documentation?

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

What are the rate limits for the Tisane API Documentation?

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 list hypernyms through Jentic?

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

How many endpoints does the Tisane API Documentation have?

The Tisane API Documentation exposes 6 endpoints covering nlu / nlp methods, language model direct access operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which Tisane operations and credentials the agent can use. Tisane offers read-only lexical lookups chosen by query parameters, so you can allow only the operations the agent needs, such as GET /hypernyms or GET /inflections, and leave the rest, like GET /senses or GET /values, unavailable. Any lookup you do not grant stays out of the agent's reach.

Tisane API Documentation

Name: Tisane API Documentation API
Brand: Tisane API Documentation
Availability: InStock

Browse all Tisane APIs

Community OpenAPI document · agent-readyAI/MLLanguage Modelsnone6 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Programmatically list hypernyms, list hyponyms. Covers 6 operations.

Use for: I need to hypernyms, I want to hyponyms, Search for inflected forms, Find all family details

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

Tisane is a natural language processing library, providing: * standard NLP functionality * special functions for detection of problematic or abusive content * low-level NLP like morphological analysis and tokenization of no-space languages (Chinese, Japanese, Thai) Tisane has monolithic architecture. All the functions are exposed using the same language models and the same analysis process invoked. The API exposes 6 endpoints.

Jentic One on Github View OpenAPI Document

Connect the Tisane API Documentation to your agent

Capabilities

Start building with Tisane API Documentation API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Tisane API Documentation