P-Image LoRA · Text to Image
Text to image
Current price
$0.006 / image
Product use cases · Studio pipelines · Images and video
Give creators a private workspace for images and video.
Use a portrait of a fictional adult in an evening dress. Plan a daylight version and a balcony-at-night version, keeping the original as the starting point for each.
- Best for
- Creator platforms and internal studios building private image editing and video generation workflows.
- What you get
- A creator workspace with protected uploads, clear model choices and controlled storage for source files and results.
Concept illustration
A creative brief to try
Make private portrait variants from one original
- 01
Keep a local copy of the original portrait. Make the daylight variant by changing only the lighting and setting.
- 02
Return to the original for the night balcony. Keep the dress and pose while changing the surroundings and light.
- 03
Animate only a still you are happy with, using a small head turn or fabric movement. Choose which originals and outputs to save or delete.
Before you keep the result
Inspect the face, dress seams, hands, and balcony edges. Review the full animation before deciding what to keep.
Start with your own reference images, follow the scene plan and review each result.
Open this scene in the Playground →Recommended models
133 matching models
Matches use the tasks and required capabilities published in the catalogue. Availability and current prices come from each model page.
FLUX.1 Schnell LoRA · Image Editing
Image editing
Current price
$0.006 / image
FLUX.1 Schnell LoRA · Text to Image
Text to image
Current price
$0.006 / image
Current price
$0.0093 / image
Z-Image · Text to Image
Text to image
Current price
$0.01 / image
Current price
$0.011 / image
Current price
$0.011 / output second
Current price
$0.012 / image
What one run costs
Worked out from the live catalogue, at the settings named under each figure.
Catalog estimates refresh hourly. Check the estimate for your settings before running; final charges follow the model’s usage and billing policy.
How to build it
Keep API keys and task creation on your server. Let the creator upload through a short-lived signed URL, then verify the callback before marking the result ready. Protect media links and move selected originals and outputs into storage with a clear retention and deletion policy.
- 01
Ask for an upload ticket
POST
/api/v1/common/upload-urlThe ticket is valid only for the byte count you declared: JPEG, PNG, WebP and GIF up to 10 MiB each. Media that already has a public HTTPS URL skips this step entirely.
- 02
Commit the uploaded file
POST
/api/v1/files/{fileId}/commitThe commit checks the bytes and hands back a spicy:// reference, which is what a model's media fields accept. Committing the same file again changes nothing.
- 03
Price the run before it exists
POST
/api/v1/jobs/quoteThe same validation and admission rules as creating the task, except nothing is created and no money is held. The signed quote lasts five minutes.
- 04
Create the task
POST
/api/v1/jobs/createTask202 means accepted, not finished. Send an Idempotency-Key, and if the price must not move, send the jobs/quote result together with the amount you agreed to.
- 05
Or let the result come to you
POST
{callBackUrl}Leave a callBackUrl and the finished record is delivered there. Verify the signature before you trust the body, and assume the same delivery will arrive twice.
- 06
Move the file into your own storage
POST
/api/v1/common/download-urlMint a short-lived download URL for the output and copy it into your own bucket within the same job. Results stay on our CDN for 14 days.
Copy a request
This example starts with the scene described on this page. Fields come from the selected endpoint’s schema. Replace any example.com reference URL with your own image or committed file URI before sending.
P-Image LoRA · Text to Image →
Where this usually snags
Platform behaviour that is cheaper to design around than to discover in production.
Verify the callback before you read it
Check the HMAC over task ID, timestamp and body hash in constant time, and reject stale timestamps. Deliveries repeat, so the receiver has to be idempotent.
Give the key a ceiling before it ships
Every API key carries a daily, a monthly and a lifetime spend cap. Set them when you create the key: a leaked key without one spends the balance, not the budget.
Inline images are the narrow path
A data URI is capped at 1 MiB decoded per image, 16 images per request and 2 MiB for the whole JSON body. Anything larger goes through an upload ticket or a public HTTPS URL.
Launch checklist
- 01Keep API keys and content decisions on a trusted server, never in browser storage.
- 02Use signed uploads limited by file type, size, object prefix and expiry.
- 03Show the selected model and run estimate before submission; an accepted task cannot be canceled.
- 04Delete source files and results according to a retention schedule users can understand.
Models that match this workflow
Explore model families for this workflow. Open a model page to review its inputs, pricing and current availability.
Frequently asked questions
133 published models match the listed tasks and required capabilities. Compare their inputs, examples, availability and current prices before choosing one.
The catalogue identifies uncensored models, including dedicated Spicy families. There is no content-mode switch, per-request declaration or platform content approval queue. Follow the model page’s current availability and input requirements.
Review the selected model’s licence, SpicyAPI’s terms and any third-party rights in your inputs and outputs. Whether a paid product is permitted depends on the actual use; a family name alone does not establish commercial rights.
Keep API keys on your server, never in a client app. Uploads are retained for 1 day and generated media for 14 days. Protect result links too: anyone with a valid link may be able to access the file. Copy anything you need to keep into your own storage.
All content must meet age, consent and applicable legal requirements. Sexualised depictions of minors or age-ambiguous people, non-consensual use of real people and other unlawful content are prohibited. See the terms and content policy for the full requirements.
About this workflow
SpicyAPI supports server-side access to uncensored image and video models without adding a platform content classifier, per-request declaration or approval queue. Each model page shows its input schema, pricing and availability. Protect API keys and result links, and define user access, consent and content-use rules in your product. Capabilities depend on the selected model.
