youcutai

An Image and Video API You Can Integrate in an Afternoon

Every tool on the site is available over the same REST interface: upload an asset, create a job, poll it. Switching from background removal to upscaling or video generation means changing one string in the request body. Background removal costs $0.02 per image against $0.20 at remove.bg and roughly $0.056 at cutout.pro, and API usage draws on the same credit wallet as the web app, so there is no separate developer plan or invoice. Every response reports the credits actually charged and which model served the request, so your unit economics are measured rather than estimated.

Challenges we solve

  • Per-image API pricing at incumbent vendors makes volume uneconomic
  • Each capability usually means another vendor, another key, another bill
  • Upstream model outages break pipelines with no fallback
  • Opaque billing makes it hard to know the true cost per unit

Recommended workflow

  1. Step 1

    Create a key

    Generate a yk_live_ key in the dashboard. It is shown once and stored as a hash; scope and usage are visible per key.

  2. Step 2

    Upload and create a job

    POST the file to /uploads, then POST a job with the tool slug, mode, input asset ids and params. The response includes the credits it will cost.

  3. Step 3

    Poll and collect outputs

    GET the job until status is succeeded, then read outputs[].url. Failed chains refund automatically and report the error.

Tools for An Image and Video API You Can Integrate in an Afternoon

Frequently asked questions

Do I need an SDK?+

No. Three HTTP calls cover every tool. We publish OpenAPI plus thin JS and Python helpers, but nothing requires them.

What happens when an upstream model fails?+

Each scene has a primary model and ordered fallbacks. The job retries down the chain automatically, and credits are refunded only if every model fails.

Is there a free tier?+

100 calls a month with a card on file, which is enough to build and test an integration end to end.

Are webhooks supported?+

Polling is the default because it is simple and works everywhere. Webhooks are available for long video jobs where polling is wasteful.