Skip to main content
After you create indexes, use index inspection APIs to see what exists, whether each index is ready, which fields are available, and what records were indexed.
In V2, use get_index() plus index.records() instead of legacy get_scene_index(). Keep using get_scene_index() only with legacy scene indexes.

List indexes

Use list_indexes() to see the indexes available on a video.
Example response:
You can filter by capability when you only want indexes that support a retrieval mode:

Get one index

Use get_index() to inspect one index manifest.
You can also fetch by index ID:
get_index() returns metadata and schema. It does not return every indexed record by default.

Inspect field schema

Because V2 indexes can support query() and aggregate(), users need to know which fields are available for each capability.
Example schema:
Use this schema to decide which retrieval API to call:

Preview indexed records

Use record preview when you want to inspect what was indexed.
Example record:
Records are paginated:
index.records() is for inspection and debugging. For retrieval, filtering, ranking, and analytics, use search(), semantic_search(), query(), and aggregate().

Search APIs remain separate from index inspection

get_index() tells you what is possible. It does not duplicate retrieval APIs. For direct semantic search:
For structured filtering on the scene index:
For object filters, query the objects index:
For counts and facets, use the index that owns the field:

Delete an index

Delete by id from the video, or call delete() on an Index object you already hold:
Deleting an index removes the retrieval structures for that index. It does not delete the original video or stored understanding artifacts.

Next steps

Search APIs

Retrieve from the indexes you inspected.

Index Fields

Configure which fields become semantic text, filters, facets, and sort keys.