What the Grok Imagine policy says
Source: xAI Acceptable Use Policy.
“Undressing or nudifying real persons, or otherwise altering a real person's image or likeness to depict them in an intimate or sexual context”
“Depicting likenesses of persons in a pornographic manner”
“Sexualizing or exploiting children”
What that means if you are building on it
- The policy is written around real people and minors. It does not say fictional adult content is allowed through the API, and xAI publishes no list of what the Imagine endpoint will refuse beyond the policy.
- What the consumer app permits behind its 18+ setting is not a promise about the API. Developers on r/grok document the toggle changing and refusals varying between the app, the web and the API.
- Building a product on behaviour that is not in writing is the risk: a model update can turn an allowed prompt into a refusal overnight, and your users see it before you do.
The workarounds, and why they break
- Prompt phrasing tricks work until the classifier is retrained, which xAI does without notice.
- Routing through the consumer app is against the terms and cannot be automated at product scale.
- Switching to an open model means renting GPUs and running the pipeline yourself.
The API alternative for fictional adult content
SpicyAPI is a REST API built for adult products: uncensored text to image, image editing, image to video, text to video and chat behind one key, pay per generation from a prepaid balance, OpenAI SDK compatible. Every prompt is moderated before billing and every request is steered to depict adults only; real people without consent and minors are blocked, and image inputs must be images your account generated.
Grok Imagine is used mostly for stills, so the closest SpicyAPI call is text to image on spicy-image-1 ($0.06 per image), with spicy-motion-2 for animating a result.
curl https://api.spicyapi.com/v1/images/generations \
-H "Authorization: Bearer $SPICYAPI_KEY" \
-H "Content-Type: application/json" \
-d '{"model": "spicy-image-1", "prompt": "a woman on a beach at golden hour, photorealistic", "size": "832*1216", "n": 1}'Full reference in the API docs, prices on the pricing page, runnable curl, Python and Node examples in the porn-api repo. See also the porn AI API overview.
FAQ
Does the Grok API allow NSFW images?
xAI's acceptable use policy bans sexual content involving real people or minors and does not state that fictional adult content is permitted. In practice API behaviour differs from the consumer app's 18+ setting and is not documented, so it cannot be relied on for a product.
Is there a Grok Imagine alternative with an API for adult content?
SpicyAPI is an OpenAI-compatible REST API built for fictional adult image and video generation. Point the OpenAI SDK at https://api.spicyapi.com/v1 and call images.generate.
Does SpicyAPI allow real people or deepfakes?
No. SpicyAPI generates fictional adults only. Real people without consent, minors in any form and image inputs you did not generate yourself are blocked before billing, the same lines the mainstream platforms draw. What changes is that fictional adult content is allowed instead of refused.
Can I test it without spending money?
Yes. Create a key with Sandbox ticked and every endpoint answers with sample output at no cost, so you can build the whole integration first. Real generations are billed per call from a prepaid balance with a $50 minimum top-up by card or crypto.
Other platforms
- Kling AI NSFW policy
- Higgsfield NSFW policy
- Sora NSFW policy
- Wan 2.2 NSFW policy
- Seedance NSFW policy
- Gemini and Nano Banana NSFW policy
- Midjourney NSFW policy
- OpenAI image generation (gpt-image and DALL-E) NSFW policy
- Veo 3 NSFW policy
- FLUX NSFW policy
- ComfyUI NSFW policy
- Runway NSFW policy
- Seedream NSFW policy