<?xml version="1.0" encoding="UTF-8"?><oembed><type>video</type><version>1.0</version><html>&lt;iframe src=&quot;https://www.loom.com/embed/b6fc57a6040c41dabf4155f61bcb2df0&quot; frameborder=&quot;0&quot; width=&quot;1920&quot; height=&quot;1440&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1440</height><width>1920</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1440</thumbnail_height><thumbnail_width>1920</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/b6fc57a6040c41dabf4155f61bcb2df0-de3863d6caf4994e.gif</thumbnail_url><duration>87.109</duration><title>Demo of PDF Extraction Route Changes and API Testing</title><description>In this video, I demo the changes made to the PDF extraction route, including a new route and prompt. I show how I&apos;m testing it with a script that takes in a PDF path and a base URL, sending it to the Vercel endpoint created for this PR. I ran tests with different providers: Gemini ran out of tokens but was partially successful, while Anthropic and OpenAI successfully extracted data from the PDF. I encourage you to check the results and provide any feedback on the implementation.</description></oembed>