Uncensored AI API

The term usually describes model access with more flexible safety controls. This collection covers image and video models with a documented configurable Safety Checker or Spicy mode through PoYo. It does not mean that the service or upstream provider has no restrictions.

The included models cover their documented text-to-image, image-editing, text-to-video or image-to-video endpoints. Check the task labels and model details before choosing. A control available for one model or operation is not automatically available for another.

Compare image quality, prompt following, reference support, output sizes and cost using the same representative inputs. Review the specific flexible control and its documented behavior. Use Text to Image or Image to Image guidance to evaluate the creative workflow as well as the control option.

Start with text-led or image-led generation, then compare duration, resolution, motion, audio and price. Confirm that the chosen endpoint exposes the control shown for that model. Test actual footage and task outcomes rather than assuming a flexible setting guarantees a successful clip.

No. These names describe model-specific controls and should not be interchanged across endpoints. Read the selected model documentation for exact field names, supported values and limitations. Do not add a generic safety parameter to an endpoint that does not document it.

Choose a documented model ID and submit its supported inputs through the generation endpoint. Save task_id and retrieve the completed result by status polling or a supported callback_url. Keep the available control within the model input structure shown in that endpoint documentation.

Yes, when the selected model supports an image-to-video endpoint. Verify image requirements, reference limits, duration, resolution and control availability. Use an appropriate source image and review the generated clip for identity, movement and unwanted changes.

Provider-side checks, unsupported inputs, service restrictions and model changes can still affect a request. Read the returned error and task status before retrying. A flexible control is not a guarantee of acceptance, and changing input parameters does not remove applicable restrictions.

Read the selected model price and billing unit. Image and video endpoints may charge per image, generation or duration, with separate tiers for quality and other settings. The control label alone does not establish one shared rate across the collection.

Retain the original task ID and query its status before resubmitting. A client timeout may occur while the task is still processing. Inspect the documented error and account usage record, then correct invalid inputs or apply an appropriate retry strategy.

Review the selected provider and PoYo terms, and the rights to prompts, source media, people and brands involved in the project. Commercial use is not established merely because an API accepts a request. Confirm the relevant permissions before publishing or monetizing output.

Generation requires PoYo and relevant providers to process submitted content. Logs or generation history may be retained under the applicable service practices. Review the PoYo Privacy Policy and provider terms for your use case, especially before submitting sensitive or third-party media.

Requests involving minors or ambiguous age, non-consensual intimate imagery, sexual deepfakes of real people, coercion, exploitation and illegal content remain prohibited. A configurable safety control does not override PoYo policies or upstream provider restrictions.

Review the applicable service requirements and design appropriate age checks, consent and real-person protections, reporting and takedown paths, and application-level moderation. Test model and provider behavior regularly, since a control or response pattern can change over time.