> For the complete documentation index, see [llms.txt](https://docs.yourv.id/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.yourv.id/content-id/manage-claims/understand-claim-detail-pages.md).

# Understand Claim Detail Pages

The Claim Detail Page displays all relevant information we have about a claim:

* **Asset Details**: The title, ID, and match policy of the asset the claim is based on. You can click the title or ID to see more details about the asset.
* **Video Details**: The video ID, the ID of the channel on which the video was uploaded, and the claim ID. You can click the video ID or channel ID to see all claims on that video or channel.
* **History**: Timeline of when the claim was created, released, disputed, or appealed.
* **Match Segments**: All segments of the video that include your asset's reference. You can click on a segment to play the respective section in the video.
* **Video Metadata**: Metadata we have about the video. Currently, this displays only the video description in the video's primary language when the claim was imported, disputed, or appealed, if the claim was updated within the last 60 days. Read the [disclaimer](/content-id/manage-claims/understand-claim-detail-pages/video-metadata-disclaimer.md) for more details.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.yourv.id/content-id/manage-claims/understand-claim-detail-pages.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.