Install Jentic One Beta

Connect the PurgoMalum to your agent

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

Filter profanity from text and return JSON response

Check if text contains profanity

Access PurgoMalum resources via REST API

Use Cases

Patterns agents use PurgoMalum API for, with concrete tasks.

★ Data Enrichment Operations

Use the PurgoMalum to perform data enrichment operations programmatically. The API provides 4 endpoints covering core functionality including filter profanity from text and return json response, filter profanity from text and return xml response, filter profanity from text and return plain text response.

GET STARTED

Start building with PurgoMalum API

Explore with Jentic One

View OpenAPI Document

Automated Filter Management

Automate filter operations by combining multiple PurgoMalum endpoints. Agents can filter profanity from text and return xml response and then filter profanity from text and return plain text response in a single workflow.

Call GET /xml to filter profanity from text and return xml response, then verify the result

AI Agent Integration via Jentic

AI agents discover and call PurgoMalum 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 'filter profanity from text and return json response', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

4 endpoints — purgomalum is a free profanity filter web service for filtering and detecting profane content in text.

METHOD

PATH

DESCRIPTION

GET

/json

Filter profanity from text and return JSON response

GET

/xml

Filter profanity from text and return XML response

GET

/plain

Filter profanity from text and return plain text response

GET

/containsprofanity

Check if text contains profanity

GET

/json

Filter profanity from text and return JSON response

GET

/xml

Filter profanity from text and return XML response

GET

/plain

Filter profanity from text and return plain text response

GET

/containsprofanity

Check if text contains profanity

Why Jentic?

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

Setup

Wiring PurgoMalum by hand means picking the right json, xml, or plain response endpoint and parsing each format yourself. Through Jentic you install once, import PurgoMalum from the API Directory, and your agent calls it with no key to manage.

Permission scoping

PurgoMalum takes the text to filter as a query parameter rather than as a path resource, so scope the agent to the operations it needs, such as filtering profanity or checking whether text contains profanity. You choose that allowed set, so only the response formats you enable are reachable.

Credential isolation

PurgoMalum needs no credential, and Jentic One runs it the same way as any imported operation, so nothing secret ever enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'filter profanity and return json' or 'check if text contains profanity', and Jentic returns the matching PurgoMalum operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using PurgoMalum API through Jentic.

What authentication does the PurgoMalum use?

The PurgoMalum 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 filter profanity from text and return json response with the PurgoMalum?

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

What are the rate limits for the PurgoMalum?

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 filter profanity from text and return json response through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'filter profanity from text and return json response'. Jentic returns the matching PurgoMalum operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the PurgoMalum have?

The PurgoMalum exposes 4 endpoints covering filter, check operations.

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

Yes. Because Jentic One is self-hosted, you set the rules that decide which PurgoMalum operations your agent may call, so you can allow only profanity filtering or only the check for whether text contains profanity. PurgoMalum takes the text as a query parameter rather than a path resource, so you scope the agent by the operations and response formats you enable, meaning only the JSON, XML, or plain endpoints you turn on are reachable. Since the API needs no credential, this operation allowlist is what defines exactly what your agent can do.

PurgoMalum

Name: PurgoMalum API
Brand: PurgoMalum
Availability: InStock

AI ReadinessAI-Aware (B+)70/100

See full scorecard

Official vendor OpenAPI document · agent-readyData EnrichmentData Transformationnone4 EndpointsREST

For Agents

Programmatically filter profanity from text and return json response, filter profanity from text and return xml response. Covers 4 operations.

Use for: I need to filter profanity from text and return json response, I want to filter profanity from text and return xml response, Search for filter profanity from text and return plain text response, Find all check if text contains profanity

Not supported: Does not handle payments, communications, or crm - use for data enrichment only.

PurgoMalum is a free profanity filter web service for filtering and detecting profane content in text. It supports multiple response formats and custom word lists. The API exposes 4 endpoints.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

100

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

99%

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

47%

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.

100

Security

Trust, risk posture, and security compliance.

Grade: A+Signals: 1

100%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: B-Signals: 1

62%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the PurgoMalum to your agent

Capabilities

Use Cases

Start building with PurgoMalum API

Key Endpoints

Why Jentic?

Related APIs

FAQs

PurgoMalum

Jentic AI Readiness Score

PurgoMalum

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