Loading video...

Video Failed to Load

There was a problem loading this video. This could be due to a temporary network issue or the video might be unavailable.

One of the hardest problems with using AI agents to automate meaningful document work (contracts, KYC, diligence, claims, and more) is not actually building the agent, but building the UI/UX audit trail so the human can understand decisions linking back to the source documents - in PDFs, Powerpoint, Word,... etc. This requires really good layout detection and segmentation, that you need to surface as metadata context to the AI agent, beyond any document -> markdown conversion. We've built really-nice VLM-capabilities to identify and segment all the elements within your document: from tables to charts to form boxes. You can use this metadata to directly provide experiences where humans can analyze the source document even as decisions are being made. Come check out LlamaParse!show more

Jerry Liu

84,556 subscribers

19,319 views • 6 months ago •via X (Twitter)

Anya Rossi• Live Now

Private livecam show

7 Comments

United Records6 months ago

crazy

LightShift Studio6 months ago

Man, still trying to figure out why you're flipping through PDFs like it's 1999?

Creart6 months ago

In our slice the same problem: one product shot as source → listing variants, ad formats. Outputs need to trace back to the asset. We're building that.

Contextually | Context Studio6 months ago

Underrated insight. The "last mile" of trust isn't model accuracy it's showing your work. Same principle applies to personal Al: if your assistant makes a recommendation, you need to see why it thought that. Context without transparency is just a black box making decisions for you. Contextually | Cue coming soon get it first:

Leo Pessoa4 months ago

The audit trail problem is why object-level grounding matters, not just agent-level. When the domain object carries its sources and updates fields from them, each value traces to a source by construction — you know what grounded what. takes this approach.

Carmelo schepis6 months ago

interesting

Thomas Tao6 months ago

Yeah the audit trail is the product. When spans point to exact PDF regions, trust goes way up.

Related Videos

As frontier models (e.g. Fable 5) continue to push the task horizon of knowledge work automation, it becomes ever more important for humans to be able to audit decisions back to the source context. It is extremely easy for agents to cite an entire document or document page, but much harder for them to trace back to the exact numbers/words/figures within a page. Today we've launched granular bounding boxes within LlamaParse, which allows you to obtain visual citations of every single word in the document. This allows human users to audit exact words and figures - not just general document regions or entire pages! Come check it out:

As frontier models (e.g. Fable 5) continue to push the task horizon of knowledge work automation, it becomes ever more important for humans to be able to audit decisions back to the source context. It is extremely easy for agents to cite an entire document or document page, but much harder for them to trace back to the exact numbers/words/figures within a page. Today we've launched granular bounding boxes within LlamaParse, which allows you to obtain visual citations of every single word in the document. This allows human users to audit exact words and figures - not just general document regions or entire pages! Come check it out:

Jerry Liu

23,491 views • 3 months ago

If you’re building an “agent over your PDFs” in 2026, one of the most underrated things you can do is to provide exact grounding back to the source document for any agentic answers. Specifically, showing the exact word, line, or region that the answer came from. Frontier vision models do a terrible job at this. They have a hard time predicting exact bounding boxes over region, tying it back to the source answer, and surfacing it as context in a cost-effective and accurate manner. Dedicated VLM-based document OCR/extraction tools like LlamaParse are a lot better at visual grounding and specifically tying it to extracted outputs. One of our main evaluation areas in ExtractBench, our recently released real-world benchmark, is to evaluate the visual grounding capabilities of document extraction. ExtractBench: If you want to give LlamaParse a shot, come check it out:

If you’re building an “agent over your PDFs” in 2026, one of the most underrated things you can do is to provide exact grounding back to the source document for any agentic answers. Specifically, showing the exact word, line, or region that the answer came from. Frontier vision models do a terrible job at this. They have a hard time predicting exact bounding boxes over region, tying it back to the source answer, and surfacing it as context in a cost-effective and accurate manner. Dedicated VLM-based document OCR/extraction tools like LlamaParse are a lot better at visual grounding and specifically tying it to extracted outputs. One of our main evaluation areas in ExtractBench, our recently released real-world benchmark, is to evaluate the visual grounding capabilities of document extraction. ExtractBench: If you want to give LlamaParse a shot, come check it out:

Jerry Liu

14,515 views • 1 month ago

Parsing a document accurately is one thing. Proving where every value came from is another. When a compliance team reviews an AI extraction, or an auditor needs to sign off on a figure pulled from a financial filing, "it came from this document" isn't enough. They need to see exactly where. The specific cell in the table, the exact line on the page, the precise word the agent used. Most parsers can get you to a paragraph or a table block. That's where the trail ends. Today we're shipping Granular Bounding Boxes in LlamaParse — word, line, and cell level coordinates for every value in your document. The result is a complete, verifiable trail from every extracted value back to its exact source in the document. Built for audit workflows, compliance review, and any pipeline where verification isn't optional. Read the full announcement →

Parsing a document accurately is one thing. Proving where every value came from is another. When a compliance team reviews an AI extraction, or an auditor needs to sign off on a figure pulled from a financial filing, "it came from this document" isn't enough. They need to see exactly where. The specific cell in the table, the exact line on the page, the precise word the agent used. Most parsers can get you to a paragraph or a table block. That's where the trail ends. Today we're shipping Granular Bounding Boxes in LlamaParse — word, line, and cell level coordinates for every value in your document. The result is a complete, verifiable trail from every extracted value back to its exact source in the document. Built for audit workflows, compliance review, and any pipeline where verification isn't optional. Read the full announcement →

LlamaIndex 🦙

29,090 views • 3 months ago

We built an AI agent that lets you vibe-code document extraction - high accuracy and citations over the most complex documents. Our latest release lets you upload documents as context. All you then have to do is describe what you want extracted in natural language. 💡 Our agent will then read the document with file tools to infer the right schema, validation rules, and other pre/postprocessing logic. ✅ It will give you back a workflow that can extract over thousands/millions of documents at scale. You can still of course review and edit every output before approving. Stop handling paperwork manually; just upload files, describe your task, and let our agent handle the rest. Our vision for LlamaAgents is to provide the most advanced and easy-to-use way for you to orchestrate document work. Walkthrough: Check it out: If you’re interested in reducing the operational burden of document extraction (invoices, claims, onboarding forms), come talk to us!

We built an AI agent that lets you vibe-code document extraction - high accuracy and citations over the most complex documents. Our latest release lets you upload documents as context. All you then have to do is describe what you want extracted in natural language. 💡 Our agent will then read the document with file tools to infer the right schema, validation rules, and other pre/postprocessing logic. ✅ It will give you back a workflow that can extract over thousands/millions of documents at scale. You can still of course review and edit every output before approving. Stop handling paperwork manually; just upload files, describe your task, and let our agent handle the rest. Our vision for LlamaAgents is to provide the most advanced and easy-to-use way for you to orchestrate document work. Walkthrough: Check it out: If you’re interested in reducing the operational burden of document extraction (invoices, claims, onboarding forms), come talk to us!

Jerry Liu

20,857 views • 7 months ago

Kicking off the Document Agent Olympics. Build a document agent - Win $200 🥇 Document agents turn messy PDFs, invoices, and filings into structured data you can actually use. Think: extracting financials from SEC filings, reconciling invoices against contracts, or processing a stack of resumes to surface top candidates. We're giving away three $200 prizes for the best agents built over the next 3 weeks. To enter: 💛 Deploy the agent to LlamaCloud 🤝 Make sure the agent repository is public 🚀 Explain what your document agent is solving 🔥 Bonus points for a good readme and demo video And most importantly, let us know what you think about our new LlamaAgents Builder! Ready to participate? Join the contest and start building your winning agent! Signup to LlamaCloud to get started

Kicking off the Document Agent Olympics. Build a document agent - Win $200 🥇 Document agents turn messy PDFs, invoices, and filings into structured data you can actually use. Think: extracting financials from SEC filings, reconciling invoices against contracts, or processing a stack of resumes to surface top candidates. We're giving away three $200 prizes for the best agents built over the next 3 weeks. To enter: 💛 Deploy the agent to LlamaCloud 🤝 Make sure the agent repository is public 🚀 Explain what your document agent is solving 🔥 Bonus points for a good readme and demo video And most importantly, let us know what you think about our new LlamaAgents Builder! Ready to participate? Join the contest and start building your winning agent! Signup to LlamaCloud to get started

LlamaIndex 🦙

12,111 views • 7 months ago

LiteParse Samples 📄🧑‍🏫 LiteParse is our free and fast document parser that can parse text with bounding boxes from any document. I’ve created a new repository that contains some demos on how you can make use of its outputs! ✅ Comparison against PyPDF and PyMuPDF ✅ Visual Citations: search for any keyword and see joined bounding boxes pop up in the source images It should be a default tool to help AI agents OCR any document type (supports PDF, Word, Powerpoint + dozens of other formats), before heavier-weight VLM-based document parsing solutions (like our own LlamaParse). LiteParse Samples repo: LiteParse:

LiteParse Samples 📄🧑‍🏫 LiteParse is our free and fast document parser that can parse text with bounding boxes from any document. I’ve created a new repository that contains some demos on how you can make use of its outputs! ✅ Comparison against PyPDF and PyMuPDF ✅ Visual Citations: search for any keyword and see joined bounding boxes pop up in the source images It should be a default tool to help AI agents OCR any document type (supports PDF, Word, Powerpoint + dozens of other formats), before heavier-weight VLM-based document parsing solutions (like our own LlamaParse). LiteParse Samples repo: LiteParse:

Jerry Liu

13,196 views • 6 months ago

The latest RAG trend for the current agent harnesses (Codex, Cowork) is to do two passes of document processing to solve a knowledge work task over a data room of documents: 1️⃣ A fast and light pass, oftentimes using a free/OSS doc parsing tool. This can be cheaply run across 10-100-1k’s of files, and enables the agent to then do retrieval (e.g. grep, semantic) to find relevant subsets of context. 2️⃣ A “just-in-time” VLM-based pass. Once the agent finds the relevant pages of context, it will screenshot the documents can call its own VLM (or write code) to dissect the pages. The issue with only using VLM-based OCR tools over massive ad-hoc customer file dumps is that it’s slow and expensive. Doing JIT VLM OCR allows the agent to filter through the data cheaply, but still preserve accuracy for the context that’s needed for the task. The agent harnesses do two-pass document processing by default using off the shelf-tools: pdf2text as the first pass, and using itself (Opus 5) as the second pass. See the below video where Cowork runs over a bunch of PDFs to answer a question about a benchmark graph in the Kimi k3 paper. The main issues here with the “out of the box” doc processing these agents offer are: * Opus 5 is not the best VLM for OCR. It is also way too expensive at scale and lacks grounding * The OSS tools like pypdf, pdf2text, may not be versatile enough as the first pass. * The agent will write a lot of throwaway code to rewrite things an OCR tool would’ve provided out of the box, like chart processing, bounding boxes, confidence scores, leading to increased cost and speed. We have all the tools within LlamaIndex 🦙 to help any agent do two-pass document processing with higher accuracy and lower cost. 1️⃣ We have liteparse for the first pass - a free/OSS parser written in Rust that’s faster/more accurate than other OSS parsers, and supports 50+ document types 2️⃣ We have LlamaParse for the second pass - an agentic document engine that uses VLMs+harnesses to achieve SOTA in accuracy and cost across various doc parsing and extraction tasks. It can be called from any agent harness as an MCP or skill. It takes in page numbers as input, so that the agent can choose to run LlamaParse over a subset of the doc instead of the full doc as a “zoom-in” pass. Come check it out! LiteParse: LlamaParse: All the relevant docs, including MCP, are here:

The latest RAG trend for the current agent harnesses (Codex, Cowork) is to do two passes of document processing to solve a knowledge work task over a data room of documents: 1️⃣ A fast and light pass, oftentimes using a free/OSS doc parsing tool. This can be cheaply run across 10-100-1k’s of files, and enables the agent to then do retrieval (e.g. grep, semantic) to find relevant subsets of context. 2️⃣ A “just-in-time” VLM-based pass. Once the agent finds the relevant pages of context, it will screenshot the documents can call its own VLM (or write code) to dissect the pages. The issue with only using VLM-based OCR tools over massive ad-hoc customer file dumps is that it’s slow and expensive. Doing JIT VLM OCR allows the agent to filter through the data cheaply, but still preserve accuracy for the context that’s needed for the task. The agent harnesses do two-pass document processing by default using off the shelf-tools: pdf2text as the first pass, and using itself (Opus 5) as the second pass. See the below video where Cowork runs over a bunch of PDFs to answer a question about a benchmark graph in the Kimi k3 paper. The main issues here with the “out of the box” doc processing these agents offer are: * Opus 5 is not the best VLM for OCR. It is also way too expensive at scale and lacks grounding * The OSS tools like pypdf, pdf2text, may not be versatile enough as the first pass. * The agent will write a lot of throwaway code to rewrite things an OCR tool would’ve provided out of the box, like chart processing, bounding boxes, confidence scores, leading to increased cost and speed. We have all the tools within LlamaIndex 🦙 to help any agent do two-pass document processing with higher accuracy and lower cost. 1️⃣ We have liteparse for the first pass - a free/OSS parser written in Rust that’s faster/more accurate than other OSS parsers, and supports 50+ document types 2️⃣ We have LlamaParse for the second pass - an agentic document engine that uses VLMs+harnesses to achieve SOTA in accuracy and cost across various doc parsing and extraction tasks. It can be called from any agent harness as an MCP or skill. It takes in page numbers as input, so that the agent can choose to run LlamaParse over a subset of the doc instead of the full doc as a “zoom-in” pass. Come check it out! LiteParse: LlamaParse: All the relevant docs, including MCP, are here:

Jerry Liu

22,763 views • 1 month ago

LlamaParse now has an official Agent Skill you can use across 40+ agents. With built-in instructions for parsing complex documents, including different formats, tables, charts, and images, your agents gain access to deeper document understanding, not just raw text extraction. 👇 Watch the demo 📖 Read the docs: 🚀 Get started with LlamaCloud:

LlamaParse now has an official Agent Skill you can use across 40+ agents. With built-in instructions for parsing complex documents, including different formats, tables, charts, and images, your agents gain access to deeper document understanding, not just raw text extraction. 👇 Watch the demo 📖 Read the docs: 🚀 Get started with LlamaCloud:

LlamaIndex 🦙

51,845 views • 6 months ago

Last week we brought LlamaParse to Claude. Now it’s available in ChatGPT, too 🦙 ChatGPT can already read PDFs. But document work gets harder when the information you need is buried in messy scans, dense tables, spreadsheets, and charts. Strike the right balance between burning tokens and accuracy, with a specialized API for document understanding. Turn complex documents into clean, structured context and let Astra run its magic. Use our connector to: ✅ Parse documents into clean Markdown, JSON, or HTML. ✅ Extract specific fields into a schema you define. ✅ Search across document collections to find the information you need. ✅ Classify files and split documents into logical sections. Live in the ChatGPT plugin directory now! →

Last week we brought LlamaParse to Claude. Now it’s available in ChatGPT, too 🦙 ChatGPT can already read PDFs. But document work gets harder when the information you need is buried in messy scans, dense tables, spreadsheets, and charts. Strike the right balance between burning tokens and accuracy, with a specialized API for document understanding. Turn complex documents into clean, structured context and let Astra run its magic. Use our connector to: ✅ Parse documents into clean Markdown, JSON, or HTML. ✅ Extract specific fields into a schema you define. ✅ Search across document collections to find the information you need. ✅ Classify files and split documents into logical sections. Live in the ChatGPT plugin directory now! →

LlamaIndex 🦙

17,601 views • 21 days ago

The same kinds of productivity gains we've seen in coding with AI agents are heading to the rest of knowledge work. This is the jump when you go from having a chatbot to being able to actually have an agent go off and do work for minutes or even hours and come back with a complete work output that you then review. Here's an example of the new Box Agent filling out an RFP response from an existing knowledge base. This process would normally take hours to fill out, and requires the full attention of the user doing the work. Now, you provide the Box Agent with the RFP questions, and it will go off, make a plan, extract all the relevant questions, read through existing source material to come up with an answer, and then generate a new word document as the final output. All while you're doing something else. The key to this architecture is that the agent is able to use all of the same tools in the background that a user uses to get work done. The agent can search for documents, read entire files, run scripts and tools in the background, and even be able to write code on the fly to automate tasks it hasn't seen before. And best of all, the Box Agent will (soon) work from the Box MCP and CLI so you can invoke it in any agentic system as a step in a process. This kind of agent complexity would have been impossible even 6 months ago. Models consistently failed at tracking long running tasks or using the right tools at the right moment for the task. But this is all now possible because of models like GPT-5.4, Opus 4.6, and Gemini 3, and is only getting better by the month. Just as we moved from engineers writing code and using AI as an assistant to answer questions, in many areas of knowledge work -like legal, finance, consulting, sales, marketing, and more- when we have a problem we'll just kick off the AI agent to just go work on it for us in the background.

The same kinds of productivity gains we've seen in coding with AI agents are heading to the rest of knowledge work. This is the jump when you go from having a chatbot to being able to actually have an agent go off and do work for minutes or even hours and come back with a complete work output that you then review. Here's an example of the new Box Agent filling out an RFP response from an existing knowledge base. This process would normally take hours to fill out, and requires the full attention of the user doing the work. Now, you provide the Box Agent with the RFP questions, and it will go off, make a plan, extract all the relevant questions, read through existing source material to come up with an answer, and then generate a new word document as the final output. All while you're doing something else. The key to this architecture is that the agent is able to use all of the same tools in the background that a user uses to get work done. The agent can search for documents, read entire files, run scripts and tools in the background, and even be able to write code on the fly to automate tasks it hasn't seen before. And best of all, the Box Agent will (soon) work from the Box MCP and CLI so you can invoke it in any agentic system as a step in a process. This kind of agent complexity would have been impossible even 6 months ago. Models consistently failed at tracking long running tasks or using the right tools at the right moment for the task. But this is all now possible because of models like GPT-5.4, Opus 4.6, and Gemini 3, and is only getting better by the month. Just as we moved from engineers writing code and using AI as an assistant to answer questions, in many areas of knowledge work -like legal, finance, consulting, sales, marketing, and more- when we have a problem we'll just kick off the AI agent to just go work on it for us in the background.

Aaron Levie

24,728 views • 5 months ago

We’re on a mission to parse the world’s hardest PDFs, and we’d love your help There are so many document types that introduce a million edge cases for current VLMs / OCR: handwritten forms, badly scanned/rotated pages, charts, diagrams, and more. We are running a contest right now for you to try to extract the hardest PDFs you can find. Come sign up on our agent builder, describe what you want to extract through natural language, upload your document, and show the results. If our platform doesn’t work, even better; this is great feedback for us to improve our service. Either way submit your project and we’d love to get your feedback! Check out LlamaCloud here:

We’re on a mission to parse the world’s hardest PDFs, and we’d love your help There are so many document types that introduce a million edge cases for current VLMs / OCR: handwritten forms, badly scanned/rotated pages, charts, diagrams, and more. We are running a contest right now for you to try to extract the hardest PDFs you can find. Come sign up on our agent builder, describe what you want to extract through natural language, upload your document, and show the results. If our platform doesn’t work, even better; this is great feedback for us to improve our service. Either way submit your project and we’d love to get your feedback! Check out LlamaCloud here:

Jerry Liu

21,005 views • 7 months ago

I needed an app to export markdown from images and PDFs, so I built one using the best model on the market: Mistral OCR. It can convert images, PDFs, and even extract tables and images, keeping them contextually within the markdown. All you need is a Mistral AI API.

I needed an app to export markdown from images and PDFs, so I built one using the best model on the market: Mistral OCR. It can convert images, PDFs, and even extract tables and images, keeping them contextually within the markdown. All you need is a Mistral AI API.

Pietro Schirano

48,786 views • 1 year ago

Introducing LiteParse - the best model-free document parsing tool for AI agents 💫 ✅ It’s completely open-source and free. ✅ No GPU required, will process ~500 pages in 2 seconds on commodity hardware ✅ More accurate than PyPDF, PyMuPDF, Markdown. Also way more readable - see below for how we parse tables!! ✅ Supports 50+ file formats, from PDFs to Office docs to images ✅ Is designed to plug and play with Claude Code, OpenClaw, and any other AI agent with a one-line skills install. Supports native screenshotting capabilities. We spent years building up LlamaParse by orchestrating state-of-the-art VLMs over the most complex documents. Along the way we realized that you could get quite far on most docs through fast and cheap text parsing. Take a look at the video below. For really complex tables within PDFs, we output them in a spatial grid that’s both AI and human-interpretable. Any other free/light parser light PyPDF will destroy the representation of this table and output a sequential list. This is not a replacement for a VLM-based OCR tool (it requires 0 GPUs and doesn’t use models), but it is shocking how good it is to parse most documents. Huge shoutout to Logan Markewich and Clelia Bertelli (🦀/acc) for all the work here. Come check it out: Repo:

Introducing LiteParse - the best model-free document parsing tool for AI agents 💫 ✅ It’s completely open-source and free. ✅ No GPU required, will process ~500 pages in 2 seconds on commodity hardware ✅ More accurate than PyPDF, PyMuPDF, Markdown. Also way more readable - see below for how we parse tables!! ✅ Supports 50+ file formats, from PDFs to Office docs to images ✅ Is designed to plug and play with Claude Code, OpenClaw, and any other AI agent with a one-line skills install. Supports native screenshotting capabilities. We spent years building up LlamaParse by orchestrating state-of-the-art VLMs over the most complex documents. Along the way we realized that you could get quite far on most docs through fast and cheap text parsing. Take a look at the video below. For really complex tables within PDFs, we output them in a spatial grid that’s both AI and human-interpretable. Any other free/light parser light PyPDF will destroy the representation of this table and output a sequential list. This is not a replacement for a VLM-based OCR tool (it requires 0 GPUs and doesn’t use models), but it is shocking how good it is to parse most documents. Huge shoutout to Logan Markewich and Clelia Bertelli (🦀/acc) for all the work here. Come check it out: Repo:

Jerry Liu

257,589 views • 6 months ago

Cursor for contracts is here. Announcing Spellbook's new AI document editor. Doc editing for lawyers is disjointed: you can edit with AI in chat, but then need to "Open in Word" to make manual tweaks without breaking formatting. Alternatively you can use a Word add-in like Spellbook's, but this only allows you to work on one document at a time. For a long time, Mitch and I talked about getting to a real "Cursor for Contracts" experience. With a lot of blood and sweat, we're finally there. Spellbook's new editor combines the best of AI editing and manual editing in one place—while fully supporting rich Word formatting that lawyers rely on. Ask AI to make edits across an entire document set, then review, accept and tweak all in one window. This sounds like a small thing, but the reduction in friction has totally changed my document editing workflow.

Cursor for contracts is here. Announcing Spellbook's new AI document editor. Doc editing for lawyers is disjointed: you can edit with AI in chat, but then need to "Open in Word" to make manual tweaks without breaking formatting. Alternatively you can use a Word add-in like Spellbook's, but this only allows you to work on one document at a time. For a long time, Mitch and I talked about getting to a real "Cursor for Contracts" experience. With a lot of blood and sweat, we're finally there. Spellbook's new editor combines the best of AI editing and manual editing in one place—while fully supporting rich Word formatting that lawyers rely on. Ask AI to make edits across an entire document set, then review, accept and tweak all in one window. This sounds like a small thing, but the reduction in friction has totally changed my document editing workflow.

Scott Stevenson

57,218 views • 1 month ago

Reducto CLI is the best way for agents to interact with document data in any workflow, and I’m really excited to see the range of use cases that are possible with this. It uses our frontier models for anything from parsing to editing, and can help automate full workflows like building spreadsheets or reports with really ugly cases. Raunak’s demo is a great example of what this unlocks

Reducto CLI is the best way for agents to interact with document data in any workflow, and I’m really excited to see the range of use cases that are possible with this. It uses our frontier models for anything from parsing to editing, and can help automate full workflows like building spreadsheets or reports with really ugly cases. Raunak’s demo is a great example of what this unlocks

Adit

16,957 views • 9 months ago

Tutorial: Automating KYC with AI agents 🪪🕵 I’m creating a new tutorial series of automating practical document workflows with agents. Every financial institution needs to perform KYC (know your customer) to verify a customer’s identity, and this involves manually sifting through IDs, bank statements, etc. and doing the cross-checking by hand. This is a great first use case for agentic document workflows: 1. Extract identification information from the user supplied ID (license, passport) 2. Extract fields from utility bills/bank statements and then use LLMs to cross-validate extracted fields with the extracted ID fields It obviously doesn’t cover the full e2e process and uses publicly available online data, but should be a good reference guide to get started. To make this work well, you do need high-quality document extraction with confidence scores and citations! Check out the tutorial: If you’re interested come check out LlamaParse:

Tutorial: Automating KYC with AI agents 🪪🕵 I’m creating a new tutorial series of automating practical document workflows with agents. Every financial institution needs to perform KYC (know your customer) to verify a customer’s identity, and this involves manually sifting through IDs, bank statements, etc. and doing the cross-checking by hand. This is a great first use case for agentic document workflows: 1. Extract identification information from the user supplied ID (license, passport) 2. Extract fields from utility bills/bank statements and then use LLMs to cross-validate extracted fields with the extracted ID fields It obviously doesn’t cover the full e2e process and uses publicly available online data, but should be a good reference guide to get started. To make this work well, you do need high-quality document extraction with confidence scores and citations! Check out the tutorial: If you’re interested come check out LlamaParse:

Jerry Liu

30,062 views • 5 months ago

Microsoft Teams just got Generative UI But this is just the tip of the iceberg. AG-UI is the protocol connecting any agent to any user on any app, topped with Generative UI. That means your agent can render: - forms - buttons - charts - approval flows Right inside the chat, on the fly. But it's not limited to in-app copilots. What's special is that you can work with any agent using the same system and bring them into any surface, including Slack, WhatsApp, Discord and more. This is exactly why Hermes and OpenClaw took off. As users of these agents, we don't like walls of text, and it's a pain to get when you can have way better UX. CopilotKit🪁 + AG-UI handle that interaction layer. If you want to try out Agentic UI in Microsoft Teams, you can get early access here:

Microsoft Teams just got Generative UI But this is just the tip of the iceberg. AG-UI is the protocol connecting any agent to any user on any app, topped with Generative UI. That means your agent can render: - forms - buttons - charts - approval flows Right inside the chat, on the fly. But it's not limited to in-app copilots. What's special is that you can work with any agent using the same system and bring them into any surface, including Slack, WhatsApp, Discord and more. This is exactly why Hermes and OpenClaw took off. As users of these agents, we don't like walls of text, and it's a pain to get when you can have way better UX. CopilotKit🪁 + AG-UI handle that interaction layer. If you want to try out Agentic UI in Microsoft Teams, you can get early access here:

Atai Barkai

24,891 views • 3 months ago

🚀 The team at Google just released the Agents API, a service for building and running custom agents inside a sandboxed Linux environment, and we built a template that gives these agents access to LlamaParse / LiteParse, enabling them to process unstructured documents automatically 📄⚡ Here’s how it works: 🔹 Configure a Git repository where data and outputs will be stored 🔹 Clone the repository into the agent sandbox 🔹 Install the LiteParse CLI, the LlamaParse SDK, and agent skills to use both 🔹 Prompt the agent with a task and watch it process documents autonomously 🤖 The result? An agent that can work directly with messy, real-world documents using LlamaParse and LiteParse within Google’s new agent runtime. Check out the GitHub repository: Get started with LlamaParse:

🚀 The team at Google just released the Agents API, a service for building and running custom agents inside a sandboxed Linux environment, and we built a template that gives these agents access to LlamaParse / LiteParse, enabling them to process unstructured documents automatically 📄⚡ Here’s how it works: 🔹 Configure a Git repository where data and outputs will be stored 🔹 Clone the repository into the agent sandbox 🔹 Install the LiteParse CLI, the LlamaParse SDK, and agent skills to use both 🔹 Prompt the agent with a task and watch it process documents autonomously 🤖 The result? An agent that can work directly with messy, real-world documents using LlamaParse and LiteParse within Google’s new agent runtime. Check out the GitHub repository: Get started with LlamaParse:

LlamaIndex 🦙

21,975 views • 4 months ago

I vibe-coded an AI agent for making presentations 🤖🖼️ - accessible to everyone and open-source! You can upload both your context files, as well as a style template (a file that captures the style of the presentation you want to create). Then you launch a prompt and watch the agent one-shot your presentation. After the presentation is generated, you can edit the text inline, chat with the agent to add/modify/delete slides, and export to Powerpoint or PDF. Built with Claude Code, powered by Claude Agent SDK + LlamaParse. Hosted on Vercel/Render. To use it, you do need to specify your LlamaCloud API key and Anthropic API key (see below). App: Repo: Sign up to LlamaCloud:

I vibe-coded an AI agent for making presentations 🤖🖼️ - accessible to everyone and open-source! You can upload both your context files, as well as a style template (a file that captures the style of the presentation you want to create). Then you launch a prompt and watch the agent one-shot your presentation. After the presentation is generated, you can edit the text inline, chat with the agent to add/modify/delete slides, and export to Powerpoint or PDF. Built with Claude Code, powered by Claude Agent SDK + LlamaParse. Hosted on Vercel/Render. To use it, you do need to specify your LlamaCloud API key and Anthropic API key (see below). App: Repo: Sign up to LlamaCloud:

Jerry Liu

21,073 views • 8 months ago