NSFW Image Detector API

POST

Catch adult images before other users see them.

NSFW Image Detector scans uploaded photos to determine whether an image contains adult content. Send a JPG, PNG, or GIF file up to 10 MB to receive safe and adult content boolean flags.

Try it — live request, no key required

Request

POSTapi.apiverve.com/v1/nsfwimagedetector

image

Click or drag a file to upload.jpg, .jpeg, .png, .gif · max 400KB for live testing

Verification

Format

No key required to try it. Get a key to use it in your app.

Example

{
  "status": "ok",
  "error": null,
  "data": {
    "isNSFW": false,
    "isSafe": true,
    "confidence": 0.987,
    "category": "neutral"
  }
}

About the NSFW Image Detector API

NSFW Detector works by analyzing the image provided and detecting NSFW content. It uses advanced algorithms to detect NSFW content and returns a boolean value indicating whether the image contains NSFW content or not.

What people use it for

Avatar Upload Filtering: Dating platforms inspect incoming profile pictures and immediately reject submissions flagged as adult content before they display publicly.
Marketplace Listing Screening: When sellers publish new product photos, e-commerce sites check each image to prevent explicit inventory from appearing in public catalog searches.
Community Chat Moderation: To keep discussion rooms family-friendly, messaging services block shared GIF and image attachments whenever the safe content check fails.
Support Ticket Attachment Triage: Route incoming helpdesk image files through screening checks so support representatives avoid unexpected exposure to explicit material while troubleshooting.

Ways to call it

One endpoint, many ways in — REST with JSON, XML, YAML and CSV, plus GraphQL and an MCP interface for AI agents.

JSON: Default REST response
XML: Markup format
YAML: Human-readable
CSV: Tabular export
GraphQL: Query language
MCP: For AI agents

View all integrations →

Questions.

Common questions about the NSFW Image Detector API.

Read the docs →

Which image file formats and sizes does the detector accept?

You can upload JPG, JPEG, PNG, and GIF files. Each uploaded file must be 10 MB or smaller.

Can I pass an image URL instead of uploading the file directly?

No, the endpoint requires a direct file upload using the image field. You need to send the image file data directly in the request rather than linking to a hosted URL.

Are the confidence score and category breakdown included on the Free plan?

No, confidence ratings and content categories are premium fields. The Free plan only returns boolean flags indicating whether an image is safe or NSFW. Upgrading to Starter or any higher paid plan unlocks the numerical confidence score and the category classification covering neutral, suggestive, and NSFW results.

What would 5,000 image checks a month cost me?

Each check takes 10 credits, which works out to about $1.50 per 1,000 checks on Starter. Running 5,000 checks uses 50,000 credits, fitting comfortably inside the 200,000 credits provided each month on the Starter plan. The Free plan includes 20 checks per month for testing.

What happens if an uploaded file exceeds the 10 MB limit?

Files exceeding 10 MB are rejected before classification. To ensure successful processing with NSFW Image Detector, every upload must be 10 MB or smaller and formatted as a JPG, PNG, or GIF.

Request parameters — POST /v1/nsfwimagedetector

Sent as JSON in the request body. Premium parameters are accepted on every plan but only take effect on plans that include them. Anything not listed here is dropped rather than passed through.

Optional

Parameter	Type	Example	Description
`image`Optional	string		Upload an image file containing the image needing classification (supported formats: JPG, PNG, GIF)

Example request

curl -X POST "https://api.apiverve.com/v1/nsfwimagedetector" \
  -H "x-api-key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{}'

Authentication

Send your key in the x-api-key header. That is the only auth step — no token exchange, and no per-endpoint scope to configure.

Header	When	Value
`x-api-key`Required	Every request	Your API key. Header names are case-insensitive, so `X-API-Key` is the same header.
`Authorization`Alternate	Instead of the above	`Bearer <key>` — for clients that only expose bearer auth. Resolves to the same account and the same billing.
`content-type`Required	POST body	`application/json`

401 is the only auth verdict

A 401 means the key is missing, invalid or expired. A 403 means the key is valid but not permitted here — blocked by a key restriction or an IP allow-list. Running out of credits is a 429.

Response — POST /v1/nsfwimagedetector

Every APIVerve endpoint returns the same three top-level keys, so one response handler covers your whole integration: status, error and data. Only data changes shape.

Sample response

{
  "status": "ok",
  "error": null,
  "data": {
    "isNSFW": false,
    "isSafe": true,
    "confidence": 0.987,
    "category": "neutral"
  }
}

Response fields

Paths are relative to data. Premium fields are absent rather than zeroed on plans that do not include them, so check for presence instead of comparing to 0.

Field	Type	Example	Description
`isNSFW`	boolean	`false`	Whether the image contains NSFW content
`isSafe`	boolean	`true`	Whether the image is safe for general audiences
`confidence`Premium	number	`0.987`	How likely the image is NSFW, from 0 to 1; 0 on a clearly safe image
`category`Premium	string	`"neutral"`	The classifier's top label for the image: sfw or nsfw

Response headers

Every response carries your balance, so your own code always knows where it stands without polling anything. All four are exposed to browsers through CORS.

Header	What it carries
`x-api-remaining-credits`	Credits left in the current cycle
`x-api-credits-used`	Credits spent in the current cycle
`x-api-max-credits`	The allowance for the cycle
`x-api-version`	Version of the endpoint that answered

Errors

Read the HTTP status first, then error for the specific reason. The body names the parameter that has to change.

Status	Meaning	What to do
`400`	Input was rejected	Read `error`; it names the parameter that has to change.
`401`	Key missing or invalid	Check the header name and the key value.
`403`	Key valid, but not permitted here	A key restriction or an IP allow-list — never a bad key.
`429`	Rate limited, or out of credits	Read `error` to tell them apart, then back off or top up.

What a call costs — 10 credits per call

Credits are shared across every APIVerve API — one balance, one key, one bill. Failed requests never count against it, so a rejected input costs nothing.

Plan	Per month	Credits	NSFW Image Detector calls	Per 1,000 calls
Free	Free	200	20	Free
Starter	$29.99	200,000	20,000	$1.50
Pro	$99.99	1,000,000	100,000	$1.00
Mega	$299.99	4,000,000	400,000	$0.75

Calls are what the credits buy at this API's rate — spend them here, on any of the other APIs, or across both. Nothing is reserved per endpoint.

Compare all pricing tiers →

Call it from cURL — POST /v1/nsfwimagedetector

No SDK to install — this is a plain HTTPS call to /v1/nsfwimagedetector with your key in the x-api-key header. Swap in a real key and it runs as-is.

cURL

1
2

curl "https://api.apiverve.com/v1/nsfwimagedetector" \
  -H "x-api-key: YOUR_API_KEY"

Resources

GitHubapiverve/nsfwimagedetector-apiSource, issues and the examples this page is built from.ReferenceNSFW Image Detector API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

@apiverve/nsfwimagedetectornpm APIVerve.API.NSFWImageDetectorNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Node.js — POST /v1/nsfwimagedetector

Install the Node.js SDK, then call the NSFW Image Detector API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.

Install — npm

npm install @apiverve/nsfwimagedetector

Node.js

const res = await fetch("https://api.apiverve.com/v1/nsfwimagedetector", {
  headers: { "x-api-key": "YOUR_API_KEY" },
});
const { data } = await res.json();
console.log(data);

Resources

npm@apiverve/nsfwimagedetectorThe published Node.js client, versioned and signed.GitHubapiverve/nsfwimagedetector-apiSource, issues and the examples this page is built from.ReferenceNSFW Image Detector API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

APIVerve.API.NSFWImageDetectorNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Python — POST /v1/nsfwimagedetector

No SDK to install — this is a plain HTTPS call to /v1/nsfwimagedetector with your key in the x-api-key header. Swap in a real key and it runs as-is.

Python

import requests

res = requests.get(
    "https://api.apiverve.com/v1/nsfwimagedetector",
    headers={"x-api-key": "YOUR_API_KEY"},
)
print(res.json()["data"])

Resources

Also published for

@apiverve/nsfwimagedetectornpm APIVerve.API.NSFWImageDetectorNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from C# / .NET — POST /v1/nsfwimagedetector

Install the C# / .NET SDK, then call the NSFW Image Detector API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.

Install — NuGet

dotnet add package APIVerve.API.NSFWImageDetector

C# / .NET

using var client = new HttpClient();
client.DefaultRequestHeaders.Add("x-api-key", "YOUR_API_KEY");

var json = await client.GetStringAsync("https://api.apiverve.com/v1/nsfwimagedetector");
Console.WriteLine(json);

Resources

NuGetAPIVerve.API.NSFWImageDetectorThe published C# / .NET client, versioned and signed.GitHubapiverve/nsfwimagedetector-apiSource, issues and the examples this page is built from.ReferenceNSFW Image Detector API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

@apiverve/nsfwimagedetectornpm

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Go — POST /v1/nsfwimagedetector

No SDK to install — this is a plain HTTPS call to /v1/nsfwimagedetector with your key in the x-api-key header. Swap in a real key and it runs as-is.

req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/nsfwimagedetector", nil)
req.Header.Set("x-api-key", "YOUR_API_KEY")

res, _ := http.DefaultClient.Do(req)
defer res.Body.Close()
body, _ := io.ReadAll(res.Body)
fmt.Println(string(body))

Resources

Also published for

@apiverve/nsfwimagedetectornpm APIVerve.API.NSFWImageDetectorNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from PHP — POST /v1/nsfwimagedetector

No SDK to install — this is a plain HTTPS call to /v1/nsfwimagedetector with your key in the x-api-key header. Swap in a real key and it runs as-is.

PHP

$ch = curl_init("https://api.apiverve.com/v1/nsfwimagedetector");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-api-key: YOUR_API_KEY"]);

$response = curl_exec($ch);
echo $response;

Resources

Also published for

@apiverve/nsfwimagedetectornpm APIVerve.API.NSFWImageDetectorNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Ruby — POST /v1/nsfwimagedetector

No SDK to install — this is a plain HTTPS call to /v1/nsfwimagedetector with your key in the x-api-key header. Swap in a real key and it runs as-is.

Ruby

require "net/http"

uri = URI("https://api.apiverve.com/v1/nsfwimagedetector")
req = Net::HTTP::Get.new(uri)
req["x-api-key"] = "YOUR_API_KEY"

res = Net::HTTP.start(uri.hostname, uri.port, use_ssl: true) { |h| h.request(req) }
puts res.body

Resources

Also published for

@apiverve/nsfwimagedetectornpm APIVerve.API.NSFWImageDetectorNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

All articles →

Content Moderation: Protect Your Platform From UGCUser-generated content is a liability until it's moderated. NSFW detection, profanity filtering, spam detection—here's how to automate it.Read

QR Codes Are Back (And This Time It's Different)Remember when QR codes were a punchline? Now they're everywhere. Here's why this time it stuck.Read

QR Codes: More Useful Than You ThinkURLs, WiFi passwords, contact cards, payment links—QR codes do more than you'd expect. Here's how to generate and read them programmatically.Read

NSFW Image Detector API

Try it — live request, no key required

About the NSFW Image Detector API

What people use it for

Ways to call it

Questions.

Request parameters — POST /v1/nsfwimagedetector

Optional

Authentication

Response — POST /v1/nsfwimagedetector

Response fields

Response headers

Errors

What a call costs — 10 credits per call

Call it from cURL — POST /v1/nsfwimagedetector

Resources

Also published for

Call it from Node.js — POST /v1/nsfwimagedetector

Resources

Also published for

Call it from Python — POST /v1/nsfwimagedetector

Resources

Also published for

Call it from C# / .NET — POST /v1/nsfwimagedetector

Resources

Also published for

Call it from Go — POST /v1/nsfwimagedetector

Resources

Also published for

Call it from PHP — POST /v1/nsfwimagedetector

Resources

Also published for

Call it from Ruby — POST /v1/nsfwimagedetector

Resources

Also published for

Zero-code embed — one snippet, no backend

Changelog — NSFW Image Detector API

Images

Related articles

Ready to build with NSFW Image Detector? Start with 200 free credits — one key unlocks all 300+ APIs.

Explore the catalog