Moderation API always returns 429

API
1

Hi everyone,

I’m trying to use the Moderation API with omni-moderation-latest, but even a single simple request returns 429.

Example input is just:

“hello”

Response:

{
"error": {
"message": "Too Many Requests",
"type": "invalid_request_error",
"param": null,
"code": null
}
}

In my project settings:

  • omni-moderation-latest is allowed
  • limits show 5000 TPM and 250 RPM
  • the API key is active
  • the key was used today
  • permissions are set to All

I recently added a payment method, but I have not added prepaid credit.

Can this 429 happen because the prepaid balance is 0, even if the Moderation endpoint is supposed to be free?

Thanks.

2

The moderation product is for ensuring the safety of the AI inputs and outputs you run on the API. It is “no additional charge” and meant for that filtering scope, loosely enforced.

API organizations have an “on” switch. If you do not have a credit-purchase-funded, provisioned API organization account that has been unlocked and set up to make the underlying paid API calls to all models and endpoints, even the models endpoint to list which AI models are available, then moderation API calls will also not succeed.

Prepaid API organizations will also be turned back off if the organization’s credit balance goes negative.

So you are correct: a credit purchase is expected to use the API. Some new accounts that go through the “start building” wizard will have some free use of a mini model suggested during that onboarding that doesn’t immediately require credit purchase to make some test language generative calls.