Architect

When to use Architect: hard-surface and structured objects - props, furniture, buildings, mechanical parts - where you want an editable, multi-part result. The output is a part hierarchy you can later Edit part-by-part or Auto-fix. For organic or photoreal forms (characters, creatures), use Sculptor instead.

Start a new generation from a text prompt, a reference image, or up to six images. The call returns a submission_id you track via Job Status.

Create a model

POST /api/v1/architect/submit

Requires API key.

At least one of task, image, or images is required.

Request Body

Name	Type	Description
`task`	string	Natural-language description of the model to create.
`image`	string	Single reference image — base64 data URL or HTTPS URL.
`images`	string[]	Up to 6 reference images (base64 or HTTPS URLs). Mutually exclusive with `image`.
`style_reference_submission_id`	string	UUID of a completed submission whose look (palette, materials, finish, level of wear) this one should match. Contributes appearance only - the subject still comes from `task` / `image`. Pass the same id across a set to keep it visually consistent.
`project_id`	string	Group the submission under a project.
`model`	string	Architect tier: `architect-plus` (most capable, default) or `architect-balanced`. Omit to use the default. `architect-lite` was retired on 2026-08-04 and now returns `400`.
`adaptive_thinking`	boolean	Enable extended thinking. Slower but higher quality. Default: `true`.
`effort`	string	Thinking effort: `high`, `medium`, or `low`. Only applies when `adaptive_thinking` is on. Default: `high`.

Style reference: what it does and does not do

style_reference_submission_id contributes appearance only - materials, palette, finish, how worn the object looks. The subject always comes from your task or your image; pointing at a wooden boat and asking for a barrel gives you a barrel, finished like that boat.

It must be a completed submission of yours that still has its artefacts. Otherwise: 404 unknown id, 400 not completed or no artefacts, 403 it belongs to another account.

For rules rather than looks - polycount budgets, naming, real-world sizes - attach a project source instead. Text states constraints well, a finished model shows appearance well, and they combine.

Example Request

curl -X POST https://api.thrixel.com/api/v1/architect/submit \
  -H "Authorization: Bearer sk-thrixel-<YOUR_KEY>" \
  -H "Content-Type: application/json" \
  -d '{"task": "a small stone gargoyle holding a lantern"}'

Example Response

{
  "submission_id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
  "status": "queued",
  "created_at": "2026-04-20T14:32:11Z"
}

Next steps

Once the job completes, chain refinement onto its submission_id: Auto-fix to auto-improve it, Edit to change specific parts, or Detailer & Texture for a high-resolution textured pass.