A separate, verified route for lawful 18+ platforms

Verified 18+ image infrastructure with the hard boundaries left intact.

A separately gated text-to-image API for lawful adult platforms. Access requires account review, age and business verification, jurisdiction controls, prompt screening, eligible-provider isolation, and mandatory output moderation.

ZERO TOLERANCEMinor-related sexual content · non-consensual content · explicit real-person depictions · sexual violence · illegal exploitation
REQUEST GATEFAIL CLOSED
01Approved organizationKYB / account reviewREQUIRED
02Verified adult keySeparate permission flagREQUIRED
03Jurisdiction checkDeployment allowlistREQUIRED
04Prompt moderationLocal + external controlsREQUIRED
05Output moderationMultimodal classifierREQUIRED
A missing safety dependency blocks generation.
CONTROL PLANE

Adult access is a separate product state, not a prompt flag anyone can set.

The request may contain safety_mode=adult, but four independent server-side controls decide whether that mode is even eligible.

01

Verified account

The organization, use case, operators, and age-assurance plan are reviewed before an adult-enabled API key exists.

02

Jurisdiction allowlist

Country availability is deployment configuration. Requests without an eligible location fail before inference.

03

Provider allowlist

Adult traffic can only reach separately approved providers. Standard fallbacks are not silently reused.

04

Output classifier

Adult output moderation is mandatory. A classifier outage returns a service error instead of an unreviewed image.

LAUNCH ELIGIBILITY

Designed for lawful fictional-adult text-to-image workflows.

The launch architecture intentionally excludes higher-risk inputs and identity features. Product expansion requires a new threat model and legal review, not a hidden toggle.

Eligible after reviewFictional adults; text-to-image; lawful use; verified organization; controlled distribution; visible reporting process.
×Not supported at launchImage uploads, face swap, likeness cloning, real-person sexualization, public figures, youthful appearance, or age ambiguity.
HARD PROHIBITIONS

No amount of verification makes these requests acceptable.

These categories stop immediately and never pass to another provider.

01Minors or youthful appearance

Any sexualized minor, age-ambiguous subject, “barely legal” framing, or youthful-looking adult depiction.

02Non-consensual content

Rape, coercion, unconscious or drugged subjects, hidden-camera content, revenge content, or claimed leaks.

03Real or identifiable people

Celebrity, public figure, acquaintance, coworker, former partner, deepfake, face swap, or exact-likeness requests.

04Illegal sexual categories

Sexual violence, incest, bestiality, necrophilia, exploitation, trafficking, or any illegal content.

OPERATOR REQUIREMENTS

The customer is part of the safety system.

Approved platforms must maintain age assurance, consent-aware product rules, user reporting, moderation review, content traceability, and rapid takedown operations.

01Age assurance for end users
02Clear consent and identity policy
03Pre-publication moderation where required
04Report, appeal, and takedown workflow
05Request-ID and asset provenance records
06Immediate key suspension capability
REVIEWED ACCESS ONLY

Bring the use case, jurisdictions, and safety plan.

Applications without concrete age assurance, moderation, distribution, and abuse-response controls will not be approved.

Start the access review →