face-to-many Serverless API

Turn a face into 3D, emoji, pixel art, video game, claymation or toy

~22.14s
POST /v2/face-to-many · submit + poll
 1# pip install "segmind>=1.1.0"
 2# export SEGMIND_API_KEY="YOUR_API_KEY"
 3import segmind
 4
 5# Async (v2): submit to the queue and block until COMPLETED.
 6# run() returns the final result dict (600s deadline, 1.0s poll by default).
 7result = segmind.run(
 8    "face-to-many",
 9    seed=1321321,
10    image="https://segmind-sd-models.s3.amazonaws.com/display_images/Ftm_ip.png.jpg",
11    style="3D",
12    prompt="a person",
13    lora_scale=1,
14    prompt_strength=4.5,
15    denoising_strength=0.65,
16    instant_id_strength=1,
17    control_depth_strength=0.8,
18)
19print(result["status"])                      # COMPLETED
20print(result.get("output"))                  # model output (e.g. media URL)
21print(result["metrics"]["inference_time"])   # server compute seconds
22
23# --- Or submit + poll manually (track request_id, control the cadence) ---
24from segmind import SegmindClient, InferenceFailed, InferenceTimeout
25
26client = SegmindClient()                      # reads SEGMIND_API_KEY
27payload = {
28    "seed": 1321321,
29    "image": "https://segmind-sd-models.s3.amazonaws.com/display_images/Ftm_ip.png.jpg",
30    "style": "3D",
31    "prompt": "a person",
32    "lora_scale": 1,
33    "prompt_strength": 4.5,
34    "denoising_strength": 0.65,
35    "instant_id_strength": 1,
36    "control_depth_strength": 0.8,
37}
38job = client.submit_async("face-to-many", **payload)
39print(job.request_id)                         # available immediately
40try:
41    result = job.wait(timeout=600, interval=1.0)
42except InferenceTimeout as e:
43    print("still running:", e.request_id)
44except InferenceFailed as e:
45    print("failed:", e.detail)

API Endpoint

POSThttps://api.segmind.com/v1/face-to-many

Parameters

control_depth_strengthoptional
number

Strength of depth controlnet. The bigger this is, the more controlnet affects the output.

Default: 0.8Range: 0 - 1
custom_lora_urloptional
string

URL to a Replicate custom LoRA. Must be in the format https://replicate.delivery/pbxt/[id]/trained_model.tar or https://pbxt.replicate.delivery/[id]/trained_model.tar

Default: null
denoising_strengthoptional
number

How much of the original image to keep. 1 is the complete destruction of the original image, 0 is the original image

Default: 0.65Range: 0 - 1
imageoptional
string (uri)

An image of a person to be converted

Default: "https://segmind-sd-models.s3.amazonaws.com/display_images/Ftm_ip.png.jpg"
instant_id_strengthoptional
number

How strong the InstantID will be.

Default: 1Range: 0 - 1
lora_scaleoptional
number

How strong the LoRA will be

Default: 1Range: 0 - 1
negative_promptoptional
string

Things you do not want in the image

Default: ""
promptoptional
string
Default: "a person"
prompt_strengthoptional
number

Strength of the prompt. This is the CFG scale, higher numbers lead to stronger prompt, lower numbers will keep more of a likeness to the original.

Default: 4.5Range: 0 - 20
seedoptional
integer

Fix the random seed for reproducibility

Default: -1
styleoptional
string

An enumeration.

Default: "3D"
Allowed values :
"3D""Emoji""Video game""Pixels""Clay""Toy"

Response Type

Returns: Image

Asynchronous requests (v2)

Use Async for video, long-running (>~60s), or high-concurrency workloads; Sync is simplest for fast image & LLM calls. Async submits a request and you poll it to completion.

  1. 1
    POST /v2/face-to-many

    Submitreturns request_id, status_url, response_url

  2. 2
    GET /v2/requests/{id}/status

    Polluntil COMPLETED or FAILED

  3. 3
    GET /v2/requests/{id}

    Resultfinal response body

Status states

QUEUEDAccepted, waiting for a worker
PROCESSINGRunning on a worker
COMPLETEDDone — result body is ready
FAILEDErrored (incl. content/RAI blocks)
  • A FAILED request is served as HTTP 422 — the body still carries the error detail.
  • An unknown or expired request_id returns HTTP 404.
  • Results are retained for 1 hour, then expire.
  • Content / RAI blocks surface as FAILED, not a separate state.
  • Track completion by polling the status endpoint.

Common Error Codes

The API returns standard HTTP status codes. Detailed error messages are provided in the response body.

400

Bad Request

Invalid parameters or request format

401

Unauthorized

Missing or invalid API key

403

Forbidden

Insufficient permissions

404

Not Found

Model or endpoint not found

406

Insufficient Credits

Not enough credits to process request

429

Rate Limited

Too many requests

500

Server Error

Internal server error

502

Bad Gateway

Service temporarily unavailable

504

Timeout

Request timed out