1

Send the prompt to your agent

Your agent will handle the migration setup

Copy agent prompt

# Task: build on the Sume API

Sume serves image and video models (Seedance, Kling, Veo, Wan, MiniMax, Nano Banana, GPT Image, Flux and more) behind one REST API, priced in dollars per second or per image.

## Keys
Create a key in Sume → Sume API → API keys. Keep it server-side as SUME_API_KEY and send it as `Authorization: Bearer <key>`. Never put it in browser code, logs or commits.

## How the API works
1. Pick a model: GET https://api.sume.com/v1/open/catalog lists every model with its id, modes, capabilities and dollar prices.
2. Price it: POST https://api.sume.com/v1/open/estimate with {"model": "<id>", "input": {...}} returns the exact dollars for that input.
3. Submit: POST https://api.sume.com/v1/video-router/generate (video, lipsync, captions) or https://api.sume.com/v1/image-router/generate (images) with {"model": "<id>", ...input}. The 202 holds the job id, status_url and result_url.
4. Poll: GET https://api.sume.com/v1/jobs/<id>/status until completed, failed or canceled; then GET https://api.sume.com/v1/jobs/<id>/result for media URLs. POST https://api.sume.com/v1/jobs/<id>/cancel cancels.
5. Failed and canceled jobs are refunded; you pay only for completed ones.

## Example
```bash
curl -X POST https://api.sume.com/v1/video-router/generate \
  -H "Authorization: Bearer $SUME_API_KEY" -H "Content-Type: application/json" \
  -d '{"model":"kling-3","prompt":"A cinematic tracking shot along a sunlit coastal road","duration":5}'
```

Read https://docs.sume.com/llms.txt for webhooks, uploads and errors before you change the request shape. Store each job id with the user who made it and check ownership before returning results.

## Migrating from fal.ai, Higgsfield, Kie
If this app already calls one of those providers, move it to Sume without changing what the user sees:
1. Find every place the app submits a generation, polls it, cancels it, uploads a reference or reads its result. List them before you edit.
2. Map each provider model to a Sume model id from https://api.sume.com/v1/open/catalog (match on the model family, mode and resolution, for example a Kling 3.0 text-to-video route maps to `kling-3`). Report any model with no Sume match instead of substituting one silently.
3. Replace the provider's SDK or REST calls with the Sume endpoints above. Rename the provider's input fields to the Sume parameter names the catalog row lists, keep defaults explicit, and keep the provider's queue semantics: submit returns a job, poll the status until it ends, then read the result.
4. Swap the provider key for SUME_API_KEY on the server and remove the old key from the environment once nothing reads it.
5. Before switching traffic, price each mapped request with https://api.sume.com/v1/open/estimate and show the dollars next to the old price so the owner can compare.
6. Keep the old integration behind a flag until a real request on each mapped model has completed on Sume.