Is this page helpful?

USD Search API 1.3.0#

Release Date: March 2026

  • SigLIP2 embedding model significantly improves search quality compared to the previous model.

  • Query relevance verification functionality uses a VLM to enable post-search evaluation of how relevant search results are to the input query. This feature significantly improves search quality, particularly for domain-specific queries or when the object of interest is under-represented in the database. (NOTE: VLM access must be configured at deployment time.)

  • Expanded USD properties search functionality to allow filtering for numeric properties and added support for indexing polygon count for USD assets.

  • Storage API backend support has been added to allow interacting with [Omniverse Storage APIs](https://catalog.ngc.nvidia.com/orgs/nvidia/teams/omniverse/collections/storage_apis).

Added#

  • Switched to using SigLIP2 as a based embedding model.

  • Added the possibility to enable VLM-based results relevance check.

  • Added support for processing multiple thumbnails for the asset.

  • Support for a broader set of VLM models including (Google Gemini, Azure OpenAI, etc.).

  • Support for limiting chunks size of search backend bulk operations.

  • Added support for filtering by polygon count.

  • Add support for >, >=, <, <= queries on numeric fields extracted from USD metadata.

  • Added support for relying on rendering service instead of dynamic k8s rendering jobs (currently in beta). - Added HSSC cache for rendering service. - Added the possibility to set the limit of how much RAM memory each Kit process may occupy in order to not crash the worker. - Added the possibility to reject further requests by the rendering service to avoid filling up the queue.

  • Added support to enable CORS on the API gateway level.

  • Added admin tools to allow cleaning up processing queues.

Updated#

  • Default OpenSearch and Redis settings.

  • Removed some of the services that were used for metrics collection. - Moved some metric collection from service monitors to pod monitors.

  • OpenSearch version is updated to 3.3.2.

  • Helm chart dependency updates.

Fixed#

  • Support rendering assets that do not have default prim explicitly defined.

  • Fixed the issue when passing invalid token still allowed searching.

  • Removed mentions of deprecated Azure storage backend type to avoid confusion, connecting to Azure blobstorage is fully supported through s3proxy functionality.

  • Fix possible image pull secret duplication issue (that throws error with helm>4).

  • Removed kube-dns resolver from API gateway config.

  • S3 re-scan timeout is not properly applied.

  • Tag based filtering.

  • Updated neo4j helm chart and livenessprobe to check if the database is operational.

NOTE: Since the base embedding model has been updated to [SigLIP2](https://huggingface.co/google/siglip2-giant-opt-patch16-384), previously extracted embeddings are not compatible. The background re-indexing process will start automatically after the instance update.

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 must be separated by a single comma (having a comma and a space is not supported).

  • Pagination of search results is currently not supported.

  • Search query results relevance check functionality only supports textual queries at the moment. Query results relevance check of image-based search queries is not yet supported.