APEX Agent Workflows

Comprehensive workflows guiding agents on how to leverage APEX domains and transactions in common 3D scene configuration scenarios.
Published: 7/10/2026

Orchestrating Multi-Domain Configurations

While APEX maintains a strictly flat schema architecture to ensure reliability, agents frequently combine multiple flat mutations sequentially to construct high-level functional features.

Rather than triggering multiple independent network requests, agents should compose atomic, multi-step transaction batches utilizing client-side temporary identifiers.

Browse the available APEX workflow guide:

Creating Custom Option Models Workflow#

Detailed workflow sequence for creating and configuring option models, sets, and material datasets in APEX.

Step-by-Step Option Model Setup Flow

To construct a fully functional 3D product configurator (such as letting users swap shoe materials or car colors), agents must coordinate three decoupled domains (OPTION_MODEL, DATASET, OPTION_SET) in a precise logical order:

Step 1: Declare the Option Model (OPTION_MODEL)

Begin by dispatching an ADD operation for the OPTION_MODEL domain to define the top-level customization envelope.

Step 2: Establish the Materials Dataset (DATASET)

Declare the structural schema for the customizable choices by dispatching an ADD operation for the DATASET domain, defining fields like materialName: STRING and textureMap: STRING.

Step 3: Populate Dataset Variant Options (DATASET_ROW)

Add individual, selectable records under the dataset by dispatching ADD operations for the DATASET_ROW domain, pointing datasetId to your dataset identifier.

Step 4: Wire the Option Set Binding (OPTION_SET)

Finally, bind the options group to the configurator container by dispatching an ADD operation for the OPTION_SET domain, linking the parent optionModelId with your datasetId.

Leveraging Atomic Temporary IDs

Because these operations depend on each other's identifiers, agents should take advantage of temporary client-generated IDs (e.g., temp_model_1, temp_dataset_1). This allows the entire four-step workflow to execute inside a single atomic transaction batch.

The engine processes the temporary IDs in order, executes the database writes, and handles internal mapping. You can review concrete sneaker payloads illustrating this pattern in the Option Model & Set APEX Payloads reference guide.