Discover / content-moderation-api-hhy1.onrender.com

Content Moderation API

□ No challenge detected

Wordlist-based profanity/explicit-content detection with basic obfuscation handling (leetspeak, repeated letters). Returns a flag, matched terms, and a redacted version.

x402
Base
USDC
Content

Challenge detected: 0 of the last 3 checks
Last checked: 16 Oct, 21:16 UTC
In our index since: 14 Oct 2026

Endpoint

curl -i https://content-moderation-api-hhy1.onrender.com
# 402 Payment Required: pay with an x402 client (USDC on Base),
# then send the same request again with the payment attached.

Agents can find it through the Superstables MCP server and JSON API: GET /api/v1/services/content-moderation-api-hhy1.onrender.com

Recent checks

14 Oct 2026One bar per check, showing up to 20 recent checks. Coloured bars show relative response time, with a minimum visible height; full-height grey bars mean no challenge was detected. “Challenge detected” means HTTP 402 or another detected payment-challenge signal.16 Oct 2026

All 3 checks

When (UTC)	Result	HTTP	Response
16 Oct, 21:16 UTC	No challenge detected	503	263ms
15 Oct, 14:11 UTC	No challenge detected	503	279ms
14 Oct, 08:45 UTC	No challenge detected	503	139ms

Questions

Did our last probe detect a payment challenge?

No. At our last probe on 16 Oct, 21:16 UTC, we detected no payment challenge.

What payment terms does Content Moderation API advertise?

The listing advertises x402, Base and USDC. Check the seller's current payment challenge and authentication requirements before paying.

Where is Content Moderation API listed?

In x402-list.com. Superstables first indexed it on 14 Oct 2026.

Something wrong on this page? Tell us.