Two AI media APIs can look identical on paper — same modalities, similar models, comparable prices — and behave completely differently the moment your prompt touches an adult or edgy topic. The deciding factor is whether the API is filtered or uncensored. Here is what that difference actually is and when each one is the right tool.

What a filtered API does to your request#

A filtered API runs a moderation classifier before the model. The classifier scores your prompt across categories (sexual content, violence, and so on) and, above a threshold, rejects the request — usually with a 400 and a policy error. The model never runs. On top of that, the provider’s terms of service prohibit adult output, so even a prompt that slips through can get an account flagged later.

  • Before runtime: prompt classifier blocks the request.
  • In policy: ToS bans adult/NSFW use.
  • After the fact: output classifiers and review can revoke access.

What an uncensored API does instead#

An uncensored API such as Api18.dev does not run a prompt-moderation classifier and does not ban adult use in its terms (illegal content excepted). Your prompt is passed to the model and you receive the output. The request you send is the request that runs.

Uncensored is about removing the filter, not removing the law. Illegal content is prohibited on any reputable platform, including uncensored ones.

When to choose which#

  • Choose filtered when your product is strictly safe-for-work, ships in app stores with strict policies, and you want the provider to enforce that for you.
  • Choose uncensored when your product needs adult/NSFW output, creative freedom, or simply can’t afford to have valid prompts silently rejected — AI companion apps, adult creators, art tools, and research are common cases.

Trade-offs to plan for#

Removing the filter shifts responsibility to you. With an uncensored API you should:

  • Apply your own age-gating and consent rules at the product layer.
  • Moderate user-supplied prompts if you expose generation to end users.
  • Keep generation server-side so your key and your policy stay enforced.

If uncensored is the right call, the practical next steps are in How to generate adult content with an API and the best uncensored image API comparison.