Modelry is a 3D visualization platform for eCommerce that creates custom 3D product models, AR experiences, and digital asset management.
Modelry is a 3D visualization platform for eCommerce that creates custom 3D product models, AR experiences, and digital asset management. On Nagent, Modelry is exposed as a fully-configurable ecommerce integration that any agent can call — 14 actions, and API key authentication. No code is required to wire Modelry into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Modelry to automate the kinds of tasks ecommerce teams previously handled manually. Concrete examples — each one is a single agent step in Nagent — include:
Every action and trigger is paired with a structured input/output schema (visible in the sections below), so when you wire Modelry into Helix — our agentic agent builder — the editor knows exactly what each step expects and produces. Configure once, deploy anywhere across your Nagent agents.
Every operation an agent can call against Modelry, with input parameters and output schema. Drop these into any step of an agent built in Helix.
MODELRY_CREATE_WORKSPACECreate a new workspace or return an existing one with the same name. Workspaces are used to organize products and embeds in Modelry. If workspace creation is not supported by the API, this tool will return an existing workspace matching the requested name.
Input parameters
Human-readable name for the workspace. If a workspace with this name already exists, it will be returned instead of creating a duplicate.
Optional description or purpose of the workspace. Note: The Modelry API may not support setting descriptions during creation.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MODELRY_DELETE_EMBEDTool to delete an embed. Tries multiple common endpoint patterns and treats 404 as idempotent success after exhausting candidates (embed already deleted or not found).
Input parameters
ID of the embed to delete
Optional workspace scope to try workspace-scoped deletion endpoints as well.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MODELRY_DELETE_PRODUCTPermanently deletes a product from Modelry by its ID. Use this action to remove a product that is no longer needed. This operation is idempotent - deleting an already-deleted product will succeed without error. Prerequisites: - Obtain the product ID using MODELRY_LIST_PRODUCTS first - Ensure you have delete permissions for the product WARNING: This action is destructive and cannot be undone.
Input parameters
The unique identifier of the product to delete. Obtain this ID from MODELRY_LIST_PRODUCTS.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MODELRY_DELETE_PRODUCT_REPOSITORYPermanently delete a product repository from Modelry. This action is idempotent - deleting a non-existent repository returns success. Use the list product repositories action first to get valid repository IDs.
Input parameters
The unique identifier of the product repository to delete. Can be obtained from the list product repositories action.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MODELRY_DELETE_WORKSPACEPermanently deletes a Modelry workspace. This action is idempotent - deleting a non-existent workspace will return success. Use the list workspaces action first to get valid workspace IDs. WARNING: This is a destructive action that cannot be undone.
Input parameters
The unique identifier of the workspace to delete. Can be obtained from the list workspaces action.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MODELRY_GET_EMBEDRetrieve details of a specific Modelry embed (3D viewer or AR experience for eCommerce). Use MODELRY_LIST_EMBEDS first to obtain valid embed IDs. Returns embed metadata including status, workspace, and configuration details.
Input parameters
Unique identifier of the Modelry embed (3D viewer/AR experience) to retrieve. Obtain valid IDs from MODELRY_LIST_EMBEDS first.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MODELRY_GET_WORKSPACERetrieves details for a specific Modelry workspace by its ID or name. The workspace ID can be obtained from the List Workspaces action. This action fetches all workspaces and returns the matching one.
Input parameters
The unique identifier (ID) or name of the workspace to retrieve. Get this from the List Workspaces action.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MODELRY_LIST_EMBEDSList embeds in Modelry. Embeds are 3D viewer/AR embed codes for products. Use to retrieve embed IDs for downstream actions (e.g., MODELRY_GET_EMBED, MODELRY_DELETE_EMBED). Returns empty list if no embeds exist. Supports pagination and optional workspace filtering.
Input parameters
Page number for pagination, must be >= 1
Number of items per page for pagination, between 1 and 100
Optional workspace identifier to scope the embeds listing
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MODELRY_LIST_MODELING_REQUESTSList all 3D modeling requests in a workspace. Requires workspace_id to scope the request. Returns modeling requests with their status and metadata.
Input parameters
Page number for pagination (starts at 1)
Number of items per page (1-100)
Unique identifier of the workspace to list modeling requests for
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MODELRY_LIST_PRODUCT_REPOSITORIESTool to list all product repositories in a workspace. Use after confirming the workspace ID.
Input parameters
Page number for pagination (starts at 1)
Number of items per page (1-100)
Unique identifier of the workspace to list repositories for
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MODELRY_LIST_PRODUCTSList all products in Modelry. Returns paginated product data including IDs, names, and metadata. Use this to retrieve product IDs needed for other product-related actions like delete or get details. Optionally scope to a specific workspace using workspace_id parameter.
Input parameters
Page number for pagination, must be >= 1
Number of items per page for pagination, between 1 and 100
Workspace ID to scope the products listing. If provided, only products in this workspace are returned.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MODELRY_LIST_WORKSPACESTool to list all workspaces in Modelry. Use when you need to retrieve available workspaces after authenticating.
Input parameters
Page number for pagination, must be >= 1
Number of items per page for pagination, between 1 and 100
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MODELRY_ORDER_MODELING_SERVICETool to place an order for 3D modeling services. Use when workspace and product IDs are known and modeling specifications are ready.
Input parameters
Additional instructions or comments for the modeler
Requested delivery date in ISO 8601 format; if omitted, standard turnaround applies
Turnaround priority; 'rush' may incur extra fees
Identifier of the product to be modeled
Level of modeling detail required
Unique identifier of the workspace where the order is placed
List of URLs pointing to reference images for the modeler
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
MODELRY_TRACK_MODELING_PROGRESSTool to track the progress of a 3D modeling request. Use after initiating a modeling job to poll current status and completion percentage.
Input parameters
Unique identifier of the modeling request to track
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
No publicly available marketplace agent is found using this tool yet. There are 96 agents privately built on Nagent that already use Modelry.
Build on Nagent
Connect Modelry to any Nagent agent in minutes — no API key management, no boilerplate. Just configure and deploy.
The five questions agent builders ask before adopting a new integration.
Open the External Integrations panel inside Nagent (app.nagent.ai/externalIntegration), find Modelry, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Modelry is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Modelry is connected, you configure its 14 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Modelry steps into any workflow visually. Pick an action (e.g., one of those listed above), fill in the inputs (Helix knows the required vs. optional schema for each parameter), and connect it to upstream/downstream steps. Triggers run as the entry point of an agent, so when a Modelry event fires, the agent kicks off automatically.
Every Modelry action and trigger ships with a fully-typed schema — input parameters with name, type, required flag, and description, plus the output payload shape. The schemas are documented in the sections above. Helix uses these schemas to validate your configuration at build time and to type-check the data flowing between steps.
Yes. While Modelry ships with 14 pre-built ecommerce actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Modelry together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Modelry-based workflows tailored to your business.