USD Search API 1.2.0#

Release Date: September 2025

  • Hybrid search functionality that allows to simultaneously search across vector and textual fields

  • Images API that allows retrieving rendering images for the assets rendered by the service

  • Sample Web UI that allows to quickly experiment with USD Search APIs

Added#

  • Hybrid Search functionality

  • Images API to retrieve rendered images for assets

  • Possibility to skip Nucleus mounts

  • Rendering job configuration settings in the helm chart configuration

  • Authentication mechanism for embedding service allowing it to run on NVCF

  • Embedding service API test in the helm chart

  • Affinity support in rendering Job template

  • Possibility to pull the explorer sample WebUI from git repository

  • Admin tools (beta) that allow some basic operations (e.g. bulk re-indexing of asset).

Fixed#

  • Embedding liveness check does not work with NVCLIP NIM model

  • Service names for plugin worker metrics are too long

  • Added mapping verification to make sure usd_properties field exits in the index with the nested type

  • Allow the possibility of passing numeric values as credentials

  • S3proxy configuration bugfix

  • VLM-based auto-captioning bugfix when default prompt and metadata fields could not be modified

  • Security updates and vulnerability fixes

Known Limitations#

  • USD Search API relies on Omniverse Kit for rendering and extracting scene prim hierarchy. Therefore the service should work with any scene that Omniverse Kit can work with.

  • When using the filter_by_properties query parameter in USD Search API, different filters have to be separated by a single comma (having a comma and a space is not supported).

  • At the moment, asset previews are returned together in a single response, which limits the maximum number of results to be returned to around 700. If assets are requested without previews, this number is significantly higher (around 10000).

  • Pagination of search results is currently not supported.

  • Single and double quotes are not supported as part of the filter_by_properties query parameter.