Compliant, consent-verified · SDXL-class quality · NDA on request

AI Undress API
inpainting-based clothing removal, built compliant

Production REST endpoint for AI-powered clothing-removal inpainting on consented input images. SDXL + ControlNet + custom NSFW LoRAs. Built with mandatory age-gate, consent verification, CSAM screening, watermarking and audit logging — the only compliant way to ship an undress tool. Used by 15+ adult-AI platforms.

Get API AccessWhat is this API?
TL;DR

NSFW Coders’ AI Undress API is a production inpainting endpoint for clothing-removal on consented input images. Built on SDXL + ControlNet + custom NSFW LoRAs. Ships with mandatory consent verification, age-gate, CSAM screening, output watermarking and full audit log — the only compliant way to operate this kind of tool. Starting at $6,000/month for 25K generations. We refuse to build for misuse: input must be of the user themselves with verified consent. Used responsibly by 15+ adult-AI platforms.

On this page
Definition

What is a AI Undress API?

An AI Undress API is an inpainting endpoint that uses diffusion models to generate a nude rendering from a clothed input image. Technically it is a masked-inpainting workflow — the API detects clothing regions, masks them, and re-paints those regions using SDXL + ControlNet conditioned on body pose, lighting, and skin tone for realistic, consistent output.

We will not deploy this API for anything other than the user themselves with verified consent. Every input image must pass our consent-verification flow (selfie + government ID match, signed consent record, age verification). Every output is watermarked, logged, and traceable. Inputs that fail consent or CSAM screening are refused at the API layer — no exceptions, no overrides.

This is the only commercially viable way to ship an undress tool in 2026. Generic undress sites are getting shut down weekly by payment processors, hosts, and regulators because they let users upload any image. Our API exists for the legitimate use cases — consenting adult creators experimenting with their own content, OnlyFans-style platforms with creator-verified accounts, adult game studios with character-design pipelines.

Who uses AI Undress APIs?

  • Adult creators with own content — OnlyFans / Fansly creators experimenting with their own consented images for content production
  • Creator-verified platforms — Sites that require KYC + selfie-match before allowing any image upload — not anonymous uploads
  • Adult game / character studios — Character-design pipelines where AI variants are generated from concept art with full provenance
  • AI companion apps (own avatar) — Apps where users design their own AI companion avatar — consented synthetic identity

How is NSFW Coders’ API different?

  • Mandatory consent verification — Selfie + ID match + signed consent record before any upload — not a click-through checkbox
  • CSAM screening — Every input passes age-estimation + CSAM hash matching (PhotoDNA) before processing
  • Output watermarking — Invisible + visible watermark on every output, traceable back to consent record and timestamp
  • Full audit log — Every generation logged with consent record, input hash, output hash, user ID, IP, timestamp
  • No anonymous uploads — API rejects all requests without a verified-consent token. No exceptions, no overrides
  • Refusal of misuse intent — We will not deploy for sites that allow uploading arbitrary photos of other people
15+
Compliant platforms in production
100%
Outputs carry consent + watermark
<5s
Average generation latency
Yes
CSAM screening on every input
Features & capabilities

8 capabilities (with safety baked in) — inpainting, pose-aware, compliant by design

Every capability runs through the mandatory consent + safety pipeline before reaching the diffusion model.

01

Consent Verification

Selfie + government-ID match required before image upload. Verified-consent token attached to every generation request.

02

CSAM & Age Screening

Every input runs age-estimation (must be 18+) and CSAM hash matching (PhotoDNA + in-house). Hard fail on edge cases.

03

SDXL Inpainting

Masked-inpainting on detected clothing regions. SDXL + ControlNet-Pose for body-anatomy realism.

04

Custom NSFW LoRAs

Style LoRAs for photoreal, anime, stylised output. Loaded per-request without re-training.

05

Body Anatomy Lock

Pose + skin-tone + lighting inferred from the consented input image — output looks like the same person.

06

Output Watermarking

Invisible (SteganoGAN) + visible watermark on every output. Watermark links to consent record.

07

Audit Log API

Every generation logged with consent ID, input hash, output hash, user ID, IP, timestamp. Queryable for legal.

08

Output Resolution

Native 1024x1024 SDXL output. Optional Real-ESRGAN upscale to 2K / 4K (adds ~3s per image).

Why clients trust us

Production-ready AI Undress API deployment

Scalable infrastructure, predictable cost, guaranteed uptime — your API runs the way production needs it to.

01

Compliance-First Architecture

Consent + CSAM + watermark + audit log are mandatory, not optional. We refuse to ship for misuse.

02

Verified-User Only

API rejects all requests without verified-consent token. No anonymous uploads. No exceptions.

03

GPU Cost Engineering

Spot-instance routing, request batching cut GPU cost 40% vs naive deployments at scale.

04

Region-Aware Compliance

Geo-restriction support. EU / UK / specific US states have stricter rules — baked into the API layer.

Quick start

Integrate in 3 lines of code

Standard REST API — works with any language. Below: cURL, Python, and Node.js.

cURL
curl -X POST https://api.nsfwcoders.com/v1/undress/generate \
  -H 'Authorization: Bearer YOUR_API_KEY' \
  -H 'Content-Type: application/json' \
  -d '{
    "consent_token": "ct_verified_user_42_abc123",
    "input_image_url": "https://your-cdn.com/inputs/user42-clothed.jpg",
    "style": "photoreal",
    "output_resolution": "1024"
  }'
Python
from nsfwcoders import Client

client = Client(api_key='YOUR_API_KEY')

# consent_token MUST come from your verified-consent flow.
# API rejects requests without it.
result = client.undress.generate(
    consent_token='ct_verified_user_42_abc123',
    input_image_url='https://your-cdn.com/inputs/user42-clothed.jpg',
    style='photoreal',
    output_resolution='1024',
)

print(result.output_url)
print(result.audit_record_id)
Node.js
import { NSFWCoders } from '@nsfwcoders/sdk';

const client = new NSFWCoders({ apiKey: process.env.NSFW_API_KEY });

// consent_token MUST come from your verified-consent flow.
const result = await client.undress.generate({
  consent_token: 'ct_verified_user_42_abc123',
  input_image_url: 'https://your-cdn.com/inputs/user42-clothed.jpg',
  style: 'photoreal',
  output_resolution: '1024',
});

console.log(result.output_url, result.audit_record_id);
Use cases

Where this API drives revenue

Common production patterns where the AI Undress API ships measurable ROI.

Use case 1

Creator Self-Content Tools

OnlyFans / Fansly creators producing variants of their own consented content for higher publishing throughput.

Use case 2

KYC-Verified Creator Platforms

Platforms that already require KYC + selfie-match for account creation. We integrate as a permitted feature.

Use case 3

Adult Game Character Pipelines

Studios designing characters from concept art with controlled variant generation and full provenance.

Use case 4

AI Companion Avatar Design

Users design their own AI companion synthetic avatar — consent is to a synthetic identity, not a real person.

Use case 5

Cam-Model Wardrobe Variants

Verified cam models generating outfit / no-outfit variants of their own consented promo shots.

Use case 6

Brand Photoshoot Variants

Adult brands generating wardrobe variants of their own consented model shoots with signed model releases.

Hosting & deployment

Pick the GPU platform that fits your budget

RunPod

GPU pods with autoscaling — ideal for verified-user undress traffic patterns.

Lambda Labs

H100 instances for higher-volume platforms with batched inpainting.

AWS / GCP private

Deploy inside your account for compliance-heavy clients. Required for some EU deployments.

Dedicated GPU Cluster

Multi-region pools for 100K+ generations/month with priority queue.

On-Premise

Air-gapped deploy for regulated markets (some EU jurisdictions). We ship hardware spec + setup.

Other NSFW APIs we ship

Build the full adult-AI stack

Combine endpoints into one pipeline — image generation, voice, video, chat, moderation, more.

NSFW Image Generation API

Pure text-to-image generation (no input photo required). Pair for outfit-variant pipelines.

Explore the API →

NSFW Face Swap API

Compliant face swap on consented inputs — same safety architecture.

Explore the API →

NSFW Moderation API

The CSAM + age + consent screening layer we use ourselves — available standalone.

Explore the API →

NSFW Video Generation API

Animate the output image into a short clip with character lock.

Explore the API →

NSFW Content Generation API

Generate captions, post copy, DM text alongside the image output.

Explore the API →
Build with this API

Live products that already use it

Pre-built clones, companion apps and white-label platforms you can launch in 30–60 days.

AI Companion App Development

Build a synthetic-avatar companion app where consent is to the AI identity, not a real person.

See the page →

AI OnlyFans Clone

Creator-verified platform with KYC + this API as a permitted creator-tool feature.

See the page →

Adult Business Registration

Get the right legal entity + compliance setup before launching anything that uses this API.

See the page →
Pricing

Fixed monthly cost, no surprise GPU bills

Pick the tier that fits your launch — we handle GPU pool, scaling, monitoring, uptime SLA.

Compliant Starter
$6,000
per month · 25K generations
  • Mandatory consent verification flow
  • CSAM + age screening
  • Output watermarking + audit log
  • SDXL + 3 style LoRAs
  • 1024x1024 output
Most picked
Compliant Pro
$15k
per month · 100K generations
  • All starter tier features
  • Custom LoRAs (your style)
  • 2K / 4K upscale
  • Multi-region deployment
  • Priority queue + dedicated SLA
Enterprise
Custom
per month · unlimited
  • On-premise / air-gapped option
  • Custom consent-flow integration
  • White-glove compliance review
  • Dedicated GPU cluster
  • NDA + DPA + on-call engineering

Every tier ships with: NDA before kickoff · 100% source-code ownership · 99.9% uptime SLA · 90 days post-launch support

FAQ

Questions about the AI Undress API

What is an AI Undress API?
An AI Undress API is an inpainting endpoint that uses diffusion models (SDXL + ControlNet + NSFW LoRAs) to generate a nude rendering from a clothed input image of a consented user. Technically it detects clothing regions, masks them, and re-paints those regions conditioned on body pose, skin tone, and lighting for realistic output. Our implementation requires mandatory consent verification, CSAM screening, watermarking, and audit logging on every request.
Will you deploy this for any platform?
No. We will not deploy for sites that allow anonymous image uploads, uploads of arbitrary other people, or any non-consenting subject. Every deployment requires a verified-consent flow at the platform layer (selfie + ID match + signed consent) before the API will accept the request. Sites that try to bypass this get terminated at the API layer.
What consent and safety controls are mandatory?
Five non-negotiable controls. (1) Consent token from a verified-user flow before any upload. (2) CSAM hash matching + age estimation on every input. (3) Invisible + visible watermark on every output. (4) Full audit log: consent ID, input hash, output hash, user ID, IP, timestamp. (5) Refusal of any request without all four. No bypass options.
How does the consent verification flow work?
Your platform performs KYC: user uploads a government ID + a selfie. Our consent service matches them (face match + ID document verification + age check). A consent_token is issued and stored. Every subsequent undress request must carry that token. Token expires after a configurable period (default 90 days). All consent records are auditable.
How much does the AI Undress API cost?
Compliant Starter is $6,000/month for 25K generations, including the mandatory consent verification flow, CSAM/age screening, output watermarking, audit log, SDXL + 3 style LoRAs at 1024x1024 output. Compliant Pro is $15,000/month for 100K generations with custom LoRAs, 2K/4K upscale, multi-region. Enterprise is custom — on-premise, air-gapped, white-glove compliance.
What is the output quality?
SDXL-class. Native 1024x1024 output with realistic skin tone, body anatomy, and lighting matched to the input photo. Optional Real-ESRGAN upscale to 2K / 4K adds ~3 seconds per generation. Style LoRAs available for photoreal, anime, stylised output.
Is this legal where I operate?
It depends on jurisdiction. Many EU states (UK Online Safety Act, Germany, France) have explicit rules on non-consensual intimate imagery. Several US states (Texas, Virginia, California) have similar laws. Our compliance architecture (verified consent only) is designed to satisfy these. We strongly recommend pairing this API with our Adult Business Registration consulting to get the right legal entity + counsel.
What happens if a user tries to upload a non-consenting image?
Three layers of refusal. (1) Your platform’s upload flow should require selfie-match against the consent record. (2) Our API rejects any request without a valid consent_token. (3) CSAM + age screening runs on every input regardless — even with a valid token, an image that fails CSAM or age estimation is refused. Every refusal is logged.
How is this different from generic undress sites?
Generic undress sites accept any uploaded photo, generate output, and offer no consent or audit trail — which is why they are getting shut down weekly by payment processors and regulators. Our API is the opposite: consent + screening + watermark + audit are mandatory on every request. The user experience is different (you must verify yourself first), but the platform is sustainable.
Do you sign NDAs?
Always. NDA before discovery call. For Enterprise tier we sign DPAs, offer source-code escrow, and provide compliance attestations for legal review. Your consent flow architecture, user data, monetisation model stay inside the engagement.

Ready to integrate the AI Undress API?

Free 30-min API walkthrough. NDA on request. Average reply under 4 hours.

Get API Access