Moderation

Stream Moderation screens text, images, audio, and video from any product. You send your own content to the API. Stream Chat, Feeds, and Video are integrations on top of that same API.

Start here

Getting started

Create a moderation policy and run your first check from your server.

SDKs

Server Side SDKs

Moderation is configured, queried and enforced from your backend.

Node
Python
Ruby
PHP
Java
.NET
Go
REST

Build with AI

Your AI agent can work with Stream from the terminal with the Stream CLI. There's also an Agent Skills pack so it can look up docs and configure your app.

curl -fsSL https://getstream.io/cli.sh | bash
getstream skills
Agent Skills
Stream CLI

Platform

Users, auth and the rest of the account-level machinery work the same in every Stream product, so they are documented once in the platform docs. Moderation setups touch these first:

Authentication and tokens

Create tokens on your server for API access.

Users

The users behind every flagged message and review action.

Webhooks

Get notified when content is flagged or actioned.

Rate limits

How limits work and how to handle 429 responses.

API error codes

Every error the API returns, with Stream codes and HTTP statuses.

FAQ

Does Moderation require Stream Chat?

No. The Chat integration is built in, but the API checks content from any platform.

What can it check?

Text, images, video and audio. A check accepts up to 30 images and 10 audio or video files, plus text.

Does AI remove content on its own?

Your policy decides. A check returns keep, flag or remove; flagged content waits in a review queue for a human.

Is there a client SDK?

Configuration and enforcement run on your server, with a server-side SDK or the REST API. Client tokens can flag, mute and appeal; they cannot upsert policies or submit moderator actions.

Can an agent read these docs?

The full Node index is the page list and the full text. Other SDKs publish the same pages under their own path. Append .md to any page URL. /llms.txt is the site overview.