Exude API Service

Name: Exude API Service API
Brand: Exude API Service
Availability: InStock

★ Only Publicly Available OpenAPI DocumentAI/MLMl Inferencenone2 EndpointsREST

For Agents

Strip stop words and apply stemming to English text payloads or uploaded files, returning normalised tokens for downstream NLP tasks.

Connect the Exude API Service to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Exude API Service, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | 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 Exude API Service API.

Strip stop words from a JSON-submitted English text payload via /exude/{type}/data

Apply Porter-style stemming to inline text and return the reduced token list

Process an uploaded text file through /exude/{type}/file and receive cleaned output

Switch between stop-word filtering and stemming modes by changing the {type} path parameter

GET STARTED

Start building with Exude API Service API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Exude API Service, keeping it validated and agent-ready.

Exude API Service is an open-source text preprocessing API focused on filtering stop words and applying stemming to raw text submitted as JSON or as a file. The service exposes two endpoints that accept English text input and return cleaned, normalised tokens suitable for downstream natural language processing pipelines. It is positioned as a lightweight utility for early-stage NLP experimentation rather than a full linguistic toolkit.

Use Cases

Patterns agents use Exude API Service API for, with concrete tasks.

★ Search Index Preprocessing

Clean up English documents before adding them to a search index by removing stop words and reducing inflected forms to their stems. Send each document to /exude/{type}/data with the appropriate type parameter and store the returned tokens in your inverted index. The service is open-source and intended for lightweight preprocessing rather than enterprise NLP workloads.

POST a JSON document with the text 'The quick brown foxes are running quickly' to /exude/stemming/data and store the returned stems in the search index.

Bulk File Cleanup

Process an uploaded plain-text file through /exude/{type}/file to receive a cleaned version with stop words stripped. Useful for batch preparation of small corpora before downstream processing such as topic modelling or keyword extraction. The endpoint accepts a single file per request and returns the processed text in the response body.

Upload a .txt file containing a product review corpus to /exude/stopword/file and save the cleaned response for downstream keyword extraction.

Agent Text Normalisation Step

Use Exude as a normalisation tool inside an AI agent's text-handling chain. Through Jentic, an agent can search for 'remove stop words from English text', load the operation schema, and invoke /exude/stopword/data on user-supplied content before passing the cleaned text to a language model or vector store. The integration removes the need for the agent to bundle a local NLP library.

Through Jentic, search for 'remove stop words from English text', load the /exude/stopword/data operation, and clean a user message before forwarding it to a downstream summariser.

Key Endpoints

2 endpoints — exude api service is an open-source text preprocessing api focused on filtering stop words and applying stemming to raw text submitted as json or as a file.

METHOD

PATH

DESCRIPTION

POST

/exude/{type}/data

Process inline JSON text with stop-word removal or stemming

POST

/exude/{type}/file

Process an uploaded file with stop-word removal or stemming

POST

/exude/{type}/data

Process inline JSON text with stop-word removal or stemming

POST

/exude/{type}/file

Process an uploaded file with stop-word removal or stemming

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

The Exude API Service has no declared authentication, so no secret is stored in the Jentic vault; the agent simply receives the cleaned tokens in the response.

Intent-based discovery

Agents search Jentic for intents like 'remove stop words from English text' or 'stem an English sentence' and Jentic returns the matching /exude/{type}/data operation with its input schema.

Time to first call

Direct integration: under an hour given only two endpoints and no auth. Through Jentic: a few minutes to search, load, and execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

EyePop WebAPI

EyePop handles vision inference; Exude handles light text preprocessing — pair them when an agent processes both images and captions.

Choose EyePop when the task is image or video inference and reach for Exude only for the accompanying caption or transcript text cleanup.

Alternative

ezBookkeeping API

Both are lightweight open-source self-hosted utility APIs in the Jentic catalogue, though they cover different domains.

Pick ezBookkeeping when the agent needs personal-finance data; pick Exude when the agent needs English text token cleanup.

FAQs

Specific to using Exude API Service API through Jentic.

What authentication does the Exude API Service use?

The OpenAPI specification declares no security schemes, so requests to /exude/{type}/data and /exude/{type}/file can be sent without credentials. When called through Jentic, no secret needs to be stored in the vault for this API and the agent receives the response directly.

Can I process an uploaded file with the Exude API Service?

Yes. Send the file as a multipart upload to /exude/{type}/file with the {type} path parameter set to the desired mode (stop-word removal or stemming) and the response body will contain the cleaned text.

What are the rate limits for the Exude API Service?

The OpenAPI specification does not declare rate limits and the project documentation describes the service as an early-stage open-source experiment hosted on Heroku, so production-grade throughput is not guaranteed; throttle client traffic and add retry logic for any 5xx responses.

How do I run stop-word removal through Jentic?

Install the SDK with pip install jentic, search for 'remove stop words from English text', load the /exude/stopword/data operation schema, then execute it with your text payload. Jentic returns the cleaned token list directly to the agent.

Does the Exude API Service support languages other than English?

The two endpoints in the spec describe English stop-word and stemming behaviour and do not document a language parameter, so treat the service as English-only and route non-English text to a different preprocessing API.

Is the Exude API Service free to use?

The project is open-source and the public Heroku endpoint has no documented pricing, but availability and response times are best-effort; for production workloads consider self-hosting the project or running an alternative NLP preprocessing API.