usd-search

Stand up a USD Search deployment the user controls. Branches on local docker-compose vs. helm on Kubernetes. Local branch covers the full quickstart compose stack with GPU/VLM/storage-backend questionnaires. Helm branch covers the usdsearch chart at helm/usdsearch. Use when: "deploy usdsearch", "run the stack myself", "helm install usdsearch", "start the stack", "run usdsearch locally", "host my own".

Run the locally-built Explorer UI against a REMOTE, fully-hosted USD Search instance by proxying every API call through the local gateway. No local deepsearch-api / OpenSearch / SigLIP2 / Asset Graph Service — only the Explorer + gateway run locally, so search, thumbnails, dependency graphs, and downloads all work exactly as on the hosted instance (which already has a populated index + AGS + storage). Use when: you want to test/demo the local Explorer with WORKING dependency graphs and downloads but don't want to (or can't) build a local index + Asset Graph Service. Default target is the public staging instance (api.staging.deepsearch-horde.nvidia.com).

Deep-inspect a single 3D asset by URL. Fetches multi-view thumbnails, per-plugin indexing status, USD scene summary (prim counts, geometry, scale, up-axis, default prim), prim hierarchy, forward + inverse dependency graphs, and optionally runs VLM relevance validation against a description. Use when the user asks to inspect / deep-dive / describe / learn about / report on a specific asset, or asks "what's in this USD", "tell me about this asset", "where is this asset used", "what does this asset reference", "is this asset indexed".

Get a first-time user to a real 3D asset in seconds. Asks one question — "where do you want to search?" — with three backend lanes (NVIDIA-hosted default, your own URL, or a local deployment), then hands off to /search for the actual query. The journey is the SVG at docs/quickstart-user-journey.svg: Stage 1 (entry) + Stage 2 (backend pick), then /search drives Stages 3-5. Use when: "quickstart", "try usd search", "show me what this does", "getting started", "what is usd search", "tour", "first time".

Spatial and scene-graph queries inside a USD scene via the Asset Graph Service. Answers: what's near a point or prim (radius), what's inside a bounding box, what prims of a given type or property exist in this scene, what does this scene reference, where is this asset used, what's the prim hierarchy. Optionally chains to /search_hybrid with image_similarity_search to find assets similar to a prim's source asset. Use when the user has a scene URL plus a spatial, structural, or dependency question.

Search USD Search for 3D assets. One skill, three input modes: text query, reference image, or both combined. Hits POST /search_hybrid + GET /images. Iterates on intermediate matches for visual-similarity refinement when the user wants "more like this". Use when: "search assets", "find a 3D model", "find a USD", "find similar", "more like this", "visually similar".

Discover which USD properties a USD Search deployment's corpus actually carries, and turn that into local config: hits GET /search/stats/usd_properties, then builds a ranked usd_property_catalog.yaml (the grounding source for the built-in LLM query parser) plus ready-to-use search_fields.generated.yaml filter stanzas. Has a P0 "gap audit" mode that reports which target properties are present/absent and pulls sample assets for parsing validation. Use when: "what USD properties can I filter on", "discover usd properties", "build a property catalog", "which metadata is in the index", "audit P0 metadata", "ground the query parser on real properties".