English Français العربية

Content Moderation API

Registre officiel IA et agents

Pay-per-call profanity/explicit-content detection for AI agents. $0.005 USDC per call, no signup.

Code source Documentation

Que pouvez-vous faire avec Content Moderation API ?

  • One narrow problem, solved well. No platforms, no suites — a single job
  • x402 for payment. HTTP-native, stablecoin
  • Discoverable by agents, not just humans — each API declares an
  • A sample automation client included with every project, showing an
  • Where it adds real reach, also sold as an MCP tool

Installation

Ajoutez ceci à la configuration MCP de votre client (Claude Desktop : claude_desktop_config.json ; Cursor : .cursor/mcp.json ; VS Code et les autres utilisent la même forme « mcpServers »).

Remote (streamable-http)
Claude Code 
claude mcp add --transport http content-moderation-api 'https://content-moderation-api-hhy1.onrender.com/mcp'
Configuration JSON (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "content-moderation-api": {
            "type": "http",
            "url": "https://content-moderation-api-hhy1.onrender.com/mcp"
        }
    }
}

Documentation

Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent GitHub.

tools

A portfolio of small, single-purpose paid services sold directly to AI agents — no human checkout flow, no dashboard login, no subscription. An agent calls the API, gets an HTTP 402 Payment Required quote, pays a few cents in USDC, and gets its answer. Fully automatic on both sides.

Each service lives in its own self-contained folder under projects/ and follows the same pattern:

  • One narrow problem, solved well. No platforms, no suites — a single job an agent needs done.
  • x402 for payment. HTTP-native, stablecoin micropayments, no merchant account or KYC required on the seller side — just a wallet address. This is the emerging standard for agent-to-API payments (backed by Coinbase, adopted by AWS Bedrock AgentCore, Cloudflare, and others as of 2026).
  • Discoverable by agents, not just humans — each API declares an x402 Bazaar discovery schema so agents can find and call it without a human ever reading the docs.
  • A sample automation client included with every project, showing an agent discovering, paying for, and consuming the service end-to-end.
  • Where it adds real reach, also sold as an MCP tool (api/app/mcp_server.py) — the same product, the same price, a second interface for coding agents that discover tools over MCP rather than raw HTTP.

Projects

ProjectWhat it sellsStatus
link-preview-apiPay-per-call URL metadata (Open Graph/title/description/image) extractionLive on Base mainnet, earning real USDC: https://link-preview-api-z4nf.onrender.com
content-moderation-apiPay-per-call profanity/explicit-content detection with redaction, sold over both HTTP and MCPLive on Base mainnet, earning real USDC: https://content-moderation-api-hhy1.onrender.com
link-preview-cache-apiSame product as link-preview-api, ~⅓ the price — backed by a shared cache. First instance of a general "x402 cache" patternLive on Base mainnet, earning real USDC: https://link-preview-cache-api.onrender.com

Repo conventions

  • Every project is fully self-contained in projects/<project-slug>/: its own code, tests, Dockerfile, deploy config, and README. Nothing product-specific is shared between projects.
  • Every project ships with:
    • api/ — the paid service itself
    • automation-client/ — a sample agent that pays for and consumes it
    • deploy/ — ready-to-use deploy configs (Render/Fly/etc.)
    • README.md — the business case, architecture, and exact steps to take it from "runs on my machine" to "earning money"
    • LISTING.md — the marketplace/directory listing copy, ready to publish
  • New projects get added the same way: a clean new folder, same skeleton, linked in the table above.
  • One deliberate exception to "nothing shared": scripts/ holds portfolio-level publishing tooling — not product code, reused across every project the same way (e.g. submitting a new tool to x402-list.com's API). See PUBLISHING.md for the full playbook: what's genuinely automatic, what's scripted, and what stays a deliberate manual step and why.

Questions fréquentes

Qu'est-ce que Content Moderation API ?

Pay-per-call profanity/explicit-content detection for AI agents. $0.005 USDC per call, no signup.

Comment installer Content Moderation API ?

Il fonctionne comme serveur distant. Dans Claude Code : claude mcp add --transport http content-moderation-api 'https://content-moderation-api-hhy1.onrender.com/mcp'. Pour les autres clients, collez la configuration JSON de cette page dans leurs réglages MCP.

Faut-il une clé API pour Content Moderation API ?

Son entrée au registre n'indique aucune clé ni secret obligatoire. Certaines fonctions peuvent tout de même demander un compte auprès du service auquel il se connecte.

Content Moderation API est-il open source ?

Son code est public sur GitHub, mais le dépôt ne déclare pas de licence standard.

Qui maintient Content Moderation API ?

Il est publié par cmondillo. AI.tn le référence sans le maintenir ni le recommander.

Issu du registre MCP officiel. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.