The vision model for browser page Fetches. Iris looks at the rendered page and decides what goes in the Main Markdown, what moves to the Appendix, and what is dropped.
Iris writes the Main Markdown for pages Fetch opens in a browser. It looks at the rendered page, not at the raw HTML, and decides what your agent should read first. There is nothing to switch on for a browser page. Files and YouTube videos use a different conversion path.
Other tools turn a page into Markdown with hand-written rules that guess what matters from the HTML. The guesses fail in both directions. A rule that drops a footer removes a company's address on one page, and on the next page it does not fire and ships thousands of tokens of clutter.
Iris does not guess from the HTML alone. It looks at the page the way you do.
For every element on the rendered page, Iris sees where it sits, how large it is, how bold its text is, whether it is pinned or floating, whether something covers it, and whether it works as navigation or as content.
So a pricing table stays a table, a check mark that means "included" stays a check mark, and a sidebar that looks like navigation is treated as navigation.
Iris sorts every element on the page into one of three groups. Its rule of thumb is that if a reasonable question could be asked about an element, the element stays.
| Group | Definition | Where it ends up |
|---|---|---|
| Keep | The content | The Main Markdown |
| Appendix | Navigation, sidebars, footers, related links | The Appendix, one request away |
| Drop | Ads, cookie banners, promos, share buttons | Nowhere. Dropped. |
Iris cannot know what your agent will need, so it picks a good default and keeps the rest reachable.
| Output | Markdown text | JSON object |
|---|---|---|
| The Main Markdown | The document body | markdown |
| Where a piece of the Appendix was cut | A [appendix omitted: 14 links · ~320 tokens] {612} marker in the body. {612} is the evidence ID of the first omitted block. | The same marker in markdown |
Every line of the Main Markdown links back to the exact spot on the captured page, so you can check what your agent read. See Playground & replay.
How to include the Appendix on each surface is on Include options.
| A pointer to the Appendix |
appendix: in the frontmatter, with its url and link counts |
meta.appendix |
The Appendix itself, with ?include=appendix | A ## Appendix section at the end | A ## Appendix section at the end of markdown |
| An evidence ID for citations | The {612} in each marker | json[].id on State JSON entries, location.evidenceId on Highlights snippets |