Ruwana Developer Documentation

Create, save and reuse private Custom Models.

Custom Models let an authenticated Platform organization create its own private adult synthetic model identity through API and reuse that identity across later PRO productions.

Canonical workflow

POST /v1/models/generate      # portrait candidate · $0.12
POST /v1/models/full-body     # derived full-body view · $0.15
POST /v1/models/save          # returns mdl_... · $0.00
GET  /v1/models               # organization-owned private library
DELETE /v1/models/{model_id}  # remove saved identity

POST /v1/pro/generate
custom_model_id = mdl_...

Portrait identity anchor

The portrait candidate is the canonical identity source. The full-body request derives a complete casting/library view from that same identity.

Save before reuse

Only a saved model receives the stable mdl_... ID used by later PRO requests. Saved identities remain private to the owning organization until deleted.

PRO handoff: standard customer-created identities use custom_model_id. Separately licensed Ruwana roster identities use model_id; the two identity sources are mutually exclusive.

Need the product overview?

The Custom Models API page explains the identity workflow in product terms; PRO docs define the photographic production request that consumes the saved model.