Moderation API

View saved version →

---
name: moderation-api-setup
description: Set up Moderation API (moderationapi.com) content moderation in an existing codebase - link or create the project with the modapi CLI, find where users create content, add the moderation call, act on the result, and verify webhooks. Use when the user asks to add content moderation, set up or integrate Moderation API, moderate user-generated content (messages, posts, comments, profiles, uploads), or block spam, scams or abuse in their app.
metadata:
  openclaw:
    emoji: "🛡️"
    homepage: https://docs.moderationapi.com/ai/skill
    envVars:
      - name: MODAPI_SECRET_KEY
        required: false
        description: Project API key. `modapi init` writes it to the app's env file; the SDKs read it from there.
      - name: MODAPI_WEBHOOK_SECRET
        required: false
        description: Webhook signing secret. `modapi init` writes it to the app's env file; the SDKs read it to verify webhooks.
---

# Set up Moderation API

You add Moderation API to the user's existing app. The `modapi` CLI does the
account work (sign-in, project, keys). You do the code: find where users create
content, moderate it on the server, and act on the result.

Work in this order. Ask before each change to the user's code or account.

## Which tool does which job

Moderation API has three tools for agents. Use each one for its own job:

| Tool | Job |
|------|-----|
| This skill | Write the integration in the user's code. |
| `modapi` CLI | Sign in, create or link the project, write the keys, check the setup (`init`, `doctor`). |
| MCP server (`https://mcp.moderationapi.com/mcp`) | Operate the account: review queues, authors, policies (channels), wordlists, webhooks, stats. |

Do not do account work with hand-written API calls when the CLI or the MCP
server does it. Do not ask for keys in the chat: the CLI writes them.

## Use the docs

This skill gives the steps and the decisions. The docs give the details, and
they change with the API. Before you use a field, event or option that this
skill does not show, read its page:

- Index of all pages: `https://docs.moderationapi.com/llms.txt`. Add `.md` to
  any docs URL to get the page as Markdown.
- Exact request and response fields: the API reference pages listed there, or
  `modapi <command> --schema` for a request body.
- If the docs and the SDK types disagree, follow the SDK types and tell the
  user.

## 1. Check the starting point

- Run `modapi --version`. If it is missing or older than 0.4.0, install it:
  `brew install moderation-api/tap/modapi` (`brew upgrade modapi` to update),
  or `go install github.com/moderation-api/cli/cmd/modapi@latest`.
  Without Homebrew or Go, ask the user to download the binary for their system
  from https://github.com/moderation-api/cli/releases and put it on their PATH.
- Run `modapi doctor -o json` in the project root. It tells you if a project
  key exists, if it works, if the SDK is installed, and if the env file is in
  `.gitignore`. Each check that is not `ok` has a `remedy`.
- If `doctor` says the user is not signed in, ask them to run `modapi login`
  now (it opens their browser; `modapi login --device` over SSH). The next
  steps need it.
- Search the code for an existing integration (`@moderation-api/sdk`,
  `moderation_api`, `moderation-api/sdk-php`, `moderationapi.com`). If one
  exists, do not set up a second one: fill the gaps doctor reports.
- Check if a ready-made integration fits better than code. Tell the user and
  ask before you write code:
  - **WordPress site**: install the
    [Moderation API plugin](https://wordpress.org/plugins/moderation-api-automated-content-moderation/),
    then connect the site under **Integrate → Platforms** in the dashboard.
  - **Discord server** or **Slack workspace** that the user wants moderated:
    connect it under **Integrate → Platforms** in the dashboard. No code.
  - Other platforms: see https://moderationapi.com/integrations.

  A custom app that has its own Discord

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 1 — file references are metadata, not package contents.