AI Safety Compliance Detection

Moderation API, worked by an AI employee

Not another app for your team to learn, and not a set of rules for you to build. You hire an AI employee, you give it access to your Moderation API account, and you ask it for things in Slack or Teams the way you would ask anyone else on the team. There is nothing to map and nothing to maintain.

  • AI Safety Compliance Detection
  • Connects with a key
  • 11 ready-made tools
  • Asked in Slack or Teams
At work

An illustration of how the conversation reads, not a transcript from a client account.

What Moderation API is

Moderation API provides content detection, human review workflows, author management, and moderation actions for online platforms.

You paste in a key from your own Moderation API account. It is kept encrypted, and you can withdraw it from inside Moderation API whenever you like.

How a run works

One message in, the work done in Moderation API.

  1. 01

    You ask

    You message your AI employee in the chat your team already has open, in one sentence, in your own words.

  2. 02

    It works out the step

    It decides what the job needs in Moderation API. You do not pick anything from a menu or wire anything together.

  3. 03

    It does the work

    Signed in to your own Moderation API account, inside the access you granted it, doing the thing you asked for.

  4. 04

    It reports back

    It tells you what it did, in the same thread. If it could not do something, it says so rather than guessing.

11 tools it already has

What it can do in Moderation API

These are the ready-made tools your AI employee already has in Moderation API. It is not limited to them, but it never has to be taught these.

  • Evaluate Content Without StorageEvaluate content without retaining it or adding it to a review queue, and return policy findings and the recommended moderation action.
  • Execute Moderation ActionApply a discovered moderation action to content items or authors. Actions can reject content or block or suspend authors and may be irreversible; inspect LISTACTIONS before calling
  • Get Account and QuotaReturn the connected Moderation API account, plan, current project, and current quota values.
  • Get Review QueueReturn metadata and item counts for a review queue by ID. Requires the paid review-queue add-on; contact Moderation API sales if review queues are not enabled for the connected org
  • Get WordlistReturn one wordlist and its current words by ID.
  • List Moderation ActionsList moderation actions available to the organization, optionally restricted to a review queue.
  • List Review Queue ItemsList and filter one page of moderation items in a review queue. Requires the paid Moderation API review-queue add-on.
  • List WordlistsList the organization's wordlists and their identifiers.
  • Modify Wordlist WordsAdd words to or remove words from an existing wordlist.
  • Set Review Queue Item StatusMark a review queue item resolved or return it to pending. Requires the paid review-queue add-on.
  • Submit Content for ModerationEvaluate content and allow Moderation API to retain it and add it to a review queue according to the project's configuration.
Access, and who is in charge of it

You stay the boss of your Moderation API account.

Nothing connects until you approve it. You grant access one app at a time, you can take it back the same way, and everything your AI employee does in there is written down where you can see it.

How we handle your data
  • It signs in to your own Moderation API account. You are not moving anything into ours.
  • You grant access one app at a time, and you can take it back the same way.
  • Everything it does in Moderation API is written down, with what it did and when.
  • Anything you tell it to check with you first, it checks with you first.
Other apps in the same corner of the business

It works in Moderation API and the rest of your software in the same job

A real job rarely stays in one place. Reading a message in one app, checking a record in another and writing the result in a third is one request to your AI employee, not three.

Questions people ask about Moderation API

Can an AI employee really work inside Moderation API?
Yes. It signs in to your own Moderation API account and works in it the way a new hire would, from the chat your team already has open. Nobody installs anything, and nobody learns a new screen.
Do I have to move anything out of Moderation API?
No. Nothing moves and nothing is replaced. Your records stay in Moderation API, your team carries on in the same screens they used yesterday, and your AI employee works alongside them in there.
How does it get into my Moderation API account?
You paste in a key from your own Moderation API account. It is kept encrypted, and you can withdraw it from inside Moderation API whenever you like. You approve it before anything connects, and you can take the access back the same way you gave it.
What can it actually do in Moderation API?
It has 11 ready-made tools in Moderation API today, among them Evaluate Content Without Storage, Execute Moderation Action and Get Account and Quota. The full list is on this page. It is not limited to those, but it never has to be taught them.
Can it use Moderation API and the rest of my software in the same job?
Yes, and that is usually the point. Reading a message in one app, checking a record in Moderation API and writing the result somewhere else is one request to your AI employee, not three separate ones you stitch together.
Who decides what it is allowed to do in Moderation API?
You do. You grant access one app at a time and can withdraw it at any time, anything you ask it to check with you first it checks with you first, and everything it does in Moderation API is written down with what it did and when.