Profanity Detection
Pricing
$1.00 / 1,000 requests
Profanity Detection
Analyze text content for profanity, offensive language, and inappropriate content with Machine Learning. Detects harmful language, provides risk scoring, and helps maintain safe user environments by filtering inappropriate content.
Pricing
$1.00 / 1,000 requests
Rating
0.0
(0)
Developer
Greip
Maintained by CommunityActor stats
0
Bookmarked
8
Total users
0
Monthly active users
5 days ago
Last modified
Categories
Features
Share
Greip Profanity Detection (API v2)
Apify Actor that scores text for profanity risk using the Greip API v2 POST /score/text endpoint. Results include a risk level and a recommended action (accept, review, or reject) without echoing submitted text in the dataset.
Features
- Greip API v2: JSON
POST https://v2.greipapi.com/score/textwith Bearer authentication - Risk level:
low,medium, orhigh - Recommendation:
accept,review, orreject - Secure logging: logs text length only, never raw content
- Structured output: dataset rows with
riskLevel,recommendation, andtimestamp
Input parameters
| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
text | string | Yes | Text to score for profanity risk | |
mode | string | No | live | Greip mode: live (production) or test (sandbox) |
Set GREIP_API_KEY in Actor environment variables. Greip v2 accepts the key only in the Authorization: Bearer header.
Output format
Successful run (dataset item):
{"riskLevel": "low","recommendation": "accept","timestamp": "2026-11-15T13:00:00.000Z"}
Other Greip v2 examples:
| riskLevel | recommendation |
|---|---|
medium | review |
high | reject |
Error dataset item (no echoed text):
{"timestamp": "2026-11-15T13:00:00.000Z","error": "Greip API error 101 invalid_key","status": "error"}
Output field descriptions
riskLevel: Overall profanity risk (low,medium,high)recommendation: Suggested action from Greip (accept,review,reject)timestamp: ISO 8601 time when the row was writtenerror: Present on failures; contains only Greipcodeandtype, never Greipdescriptionstatus:erroron failed rows
BREAKING changes in 2.0
This release migrates from Greip v1 GET /scoring/profanity to v2 POST /score/text.
Removed inputs
listBadWordsscoreOnlyuserID(v2ScoreTextRequestand profanity docs documenttext,format,mode, andsourceonly; nouser_id)
Greip dashboard user attribution is no longer available.
Removed outputs
textisMLriskScoreisSafetotalBadWordsbadWords
New or changed behavior
- Optional input
mode(live|test, defaultlive), confirmed for/score/textin OpenAPIGreipServiceRequestFieldsand Greip docs - Request body always includes
source: "Apify" - Dataset success fields are only
riskLevel,recommendation,timestamp
Use cases
- Content moderation for comments, posts, and messages
- Username and display-name screening
- Chat and community guideline enforcement
Development
npm installnpm run buildnpm run lintnpm test
Feedback
Technical feedback or bugs: Apify Issues.