---
title: AI Image Explicit Content Detection API
slug: detect-explicit-or-sensitive-content
url: https://apyhub.com/apyhub/service/detect-explicit-or-sensitive-content
provider: ApyHub
categories: [Artificial Intelligence, File Security, Image Processing]
tags: [content-moderation, explicit-content, image-safety, nsfw-detection, vision-classification]
auth: api_key
---

# AI Image Explicit Content Detection API

Scan image files or URLs for explicit or sensitive content. Returns provider-specific results from ApyHub, Azure, or Google for moderation workflows.

## Endpoints

| Method | Path | Description | Atoms |
| --- | --- | --- | --- |
| POST | `/ai/image/detect/explicit-content/file` | What it does Uploads a file to detect explicit or sensitive content and returns provider-specific r… | 500 |
| POST | `/ai/image/detect/explicit-content/url` | What it does Detects explicit or sensitive content from a URL. You send a url in the request body a… | 500 |

## About

## What it does
Explicit Content Detection checks an image file or image URL for explicit or sensitive content and returns provider-specific results from ApyHub, Azure, or Google.

Send a binary file to `POST /file`, or send a `url` to `POST /url`. Both endpoints accept an optional `requested_service` value of `azure`, `google`, or `apyhub`, so you can route the request to the detector you want to use. The file endpoint also accepts Azure credentials such as `azure_key`, `azure_region`, `azure_endpoint`, `azure_account_id`, and `azure_access_token`. The URL endpoint supports nested `azure` and `google` credential objects when you need to supply your own provider settings.

The response contains a `data` object with provider keys for `azure`, `apyhub`, and `google`. Each provider entry is returned as that provider’s own response object, so you can inspect the scan result in the format that matches the backend you chose.

Use Explicit Content Detection to screen uploaded user images, moderate public listings, or flag unsafe media before it reaches a feed, checkout flow, or review queue.

| Provider (requested_service) | Atoms |
|------------------------------|------:|
| Azure                        |   500 |
| Google                       |  500 |
| ApyHub                       |  2000 |

## Usage

Authenticate with an ApyHub API key in the `apy-token` header.
Full docs and a live playground: https://apyhub.com/apyhub/service/detect-explicit-or-sensitive-content