Account scopes, prompt checks, provider policy isolation, and output gates sit on the route — not in a PDF nobody opens. Adult mode is separate. Safety rejections never “retry elsewhere.”
Confirm an active key, allowed scope, account status, jurisdiction, and rate limit.
Reject prohibited requests before an inference provider receives them.
Use only providers and models allowed for the requested product mode.
Apply the output checks required for the account and generation mode.
The service does not permit sexual content involving minors or age ambiguity, non-consensual sexual content, sexual violence, illegal exploitation, or other categories listed in the Acceptable Use Policy.
Default generation records use a one-way prompt hash rather than storing the raw prompt. Operational metadata is limited to what is needed for routing, support, metering, security, and abuse response.
The verified 18+ service uses separate account approval, provider eligibility, jurisdiction checks, and product rules. Adult access is not enabled by a normal API key.
Automated systems are backed by a report channel and account-level enforcement. Reports can lead to an asset review, key suspension, provider coordination, or lawful escalation.
Every route remains subject to its provider, model, region, account, and commercial-use conditions. RenderRoute only selects from routes enabled for the customer and requested mode.
Read the acceptable use policy →Include the RenderRoute request ID, asset URL, reason, and contact details. Do not email illegal imagery as an attachment.
