aisplice

By capability

Images

Pick a model, copy the request, get the image. Everything below follows the model you pick.

#1. Pick a model

The model list could not be loaded

Refresh the page, or open Models & Pricing to see what is online.

#3. Get the result

The submit call answers with a task_id at once. Check the task every few seconds until status is completed, or pass webhook_url and we call you when it is done.

GET https://www.aisplice.store/v1/images/tasks/{task_id}

GET https://www.aisplice.store/v1/images/tasks/{task_id}/content

Charged only when it succeeds

A failed or cancelled task is refunded automatically. The request log shows each task’s final cost.

Status values and polling →Get a callback instead of checking →

#When it goes wrong

  • 400 with a field name: that option is not accepted by this model; use the values listed in step 2.
  • Content refused by the model: rephrase the prompt; refused requests are not charged.
  • 402: the balance cannot cover this request; top up in Wallet, then retry.
  • 429: slow down and retry after the Retry-After seconds.
  • 503 model_not_found: the model name is wrong or the model is offline; pick one from step 1.

Look up any other error →

#Reference images

Pass public image URLs in the reference-image field listed in step 2. For a local file, upload it first and use the URL you get back.

How to upload a local file →

Building it into your productWhich options to show your users first, and which to leave for later.
Which options to show your users firstStart with the prompt and one price knob; add the rest once the basic flow works.+

Creative intent

Fields like prompt belong in the UI because the user directly understands the outcome they change.

Cost multiplier

Fields like duration, resolution, size, and count should be introduced only when pricing is already explainable.

Mode switch

Fields like image, mask, or continuation IDs change the workflow itself and should appear only in dedicated modes.

System plumbing

Fields like webhook_secret are for integrators, not for everyday creators, so keep them out of default UI.

  • prompt
    Expose when
    Always. It is the primary creative input for image tasks.
    Recommended default
    Required in UI.
    Why it matters
    It controls the outcome directly; hiding it makes the feature unusable.
  • size
    Expose when
    Expose in the first release if billing changes by output dimensions.
    Recommended default
    Start with one recommended aspect ratio such as 1:1.
    Why it matters
    It affects both cost and output composition, so users need a simple size choice early.
  • quality
    Expose when
    Expose only after users clearly ask for a higher or cheaper tier.
    Recommended default
    Keep server-side at the model default.
    Why it matters
    It changes price and latency but usually does not need to be a day-one control.
  • n
    Expose when
    Expose only when batch generation is a core workflow.
    Recommended default
    Default to 1.
    Why it matters
    It multiplies cost immediately and can create noisy first-run UX.
  • mask / image
    Expose when
    Expose only for edit or reference-image products.
    Recommended default
    Hide in text-to-image mode.
    Why it matters
    These fields change the product from generation into editing, so they should not leak into the basic flow.
recommended-rollout.txt
Phase 1
- prompt
- one size or one duration default
- submit -> poll -> content

Phase 2
- one quality or resolution selector
- clear pricing hint

Phase 3
- advanced controls such as reference media, continuation, webhook, or vendor-specific tuning

Keep one source of truth for results

When a task finishes, normalize your app around the platform URL returned by /content. That keeps upstream vendor details hidden and makes historical playback stable.

Still stuck?

Send us the request ID or the error message and we will look into it.

PreviousChatNextVideos