canonical: https://jentic.com/apis/purgomalum.com/purgomalum

# PurgoMalum

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.

## For AI agents

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

## Scope

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

## Capabilities

- Filter profanity from text and return JSON response
- Check if text contains profanity
- Access PurgoMalum resources via REST API

## Use cases

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

Example prompt: Call GET /json to filter profanity from text and return json response

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

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

Example prompt: Search Jentic for 'filter profanity from text and return json response', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

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

## Key resources

- **Filter** — Text filtering endpoints
- **Check** — Profanity detection endpoints

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 70 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 100 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 49 / 100
  - Agent Usability: 94 / 100
  - Security: 100 / 100
  - AI Discoverability: 63 / 100
- **View full report:** https://jentic.com/apis/purgomalum.com/purgomalum/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

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

## Related APIs

- **Clearbit** — Alternative data enrichment API
- **Fullcontact** — Alternative data enrichment API
- **Hunter** — Complementary data enrichment API

## FAQ

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