> ## Documentation Index
> Fetch the complete documentation index at: https://docs.url2llm.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Links and assets

> Collect navigable links and image or video references from a page.

Request `links` to inspect anchors on one page and `assets` to collect referenced images and videos. Use [map](https://docs.url2llm.com/features/map.md) when you need discovery across sitemap and page sources.

```json theme={null}
{
  "url": "https://example.com",
  "formats": ["links", "assets"],
  "renderJs": true
}
```

## Read page links

`data.links` contains deduplicated navigable HTTP and HTTPS links. Relative links are resolved against the page's final URL and a valid page base URL when present.

Each link includes its URL, normalized URL, classification, text, title, optional image URL, and an `internal` flag. Internal means the link belongs to the same normalized host as the page; it is not a permission or ownership judgment.

Email, telephone, JavaScript, data URLs, and bare fragment anchors are not returned as navigable page links. A link list describes anchors found in that page, not a complete site inventory.

Use link text and source metadata when building a crawl queue, then apply your application's host and path rules before scraping another page. The API does not automatically fetch every returned link.

## Read page assets

`data.assets` contains image and video records. Records identify the asset URL, type, MIME type, title, and available metadata. Metadata can include dimensions, image alt text, video provider, or a poster URL. A missing filename or zero dimension means that information was not available from the capture.

Assets include referenced media and supported video embeds. An embed URL identifies a player; it is not necessarily a downloadable video file. Asset references do not grant access to files that the source restricts.

Asset output requires JavaScript rendering in the current API. It does not return image bytes or automatically download and host all media. Your application chooses which returned assets to retrieve and how to store them.

## Filtering and completeness

Content inclusion or exclusion can affect the document used to extract links and assets. Use [content filtering](https://docs.url2llm.com/features/markdown-html.md#focus-on-useful-content) to narrow the result, and inspect the output on representative pages.

Media loaded only after an interaction or below the visible area may be absent. The current API does not accept a browser-actions sequence to open tabs or repeatedly scroll a page. A successful response means the requested extraction completed, not that every possible site asset was discovered.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.