跳过导航
“Intelligent Document Processing” 📑🧪 as an industry is gone .
0:00 / 1:20

“Intelligent Document Processing” 📑🧪 as an industry is gone .

Jerry Liu

@jerryjliu08.7万 位关注者

在 X 上查看
384 个赞下载原帖

34,538 次观看

“Intelligent Document Processing” 📑🧪 as an industry is gone . With our latest release this week, *anyone* can build and deploy a specialized document agent in seconds ⚡️🤖, and customize the steps via code. Let’s take a tour through our invoice processing and contract matching agent: given an invoice, extract out vendor details and line items, and match it against the corresponding MSA with the vendor. 1️⃣ Put in your name and API key, and deploy the agent in 5 seconds 2️⃣ Upload some sample contracts and invoices, and watch the workflow run. 3️⃣ If you want to customize it, you can clone our source repository, modify the internals, and deploy the agent! It is both more accurate and more customizable than existing IDP solutions. With coding agents today, the ease of use is equivalent too. Click on the “agents” tab in LlamaCloud to check it out! Invoice processing repo: LlamaAgents Docs:

5 条评论

评论来自 X (Twitter) 上的原帖

  • Jerry Ann 的头像

    @AIMLforEdu

    Can it extract structured knowledge given predefined ontology or schema?

    1 个赞

  • 蕭夫SioFU 的头像

    @SioFU_AI

    Following the financial invoice is the electronic medical record.

  • Grzegorz Brzęczyszczykiewicz 🐀 的头像

    @_eMaX_

    Runs locally? It would be great if I could give an existing directory tree with content and for new content it would figure out where to put it.

  • Amit 的头像

    @amityhere

    Inteligent document processing was already solved in 2024. The real problem is cost by this type of providers.

  • Eugene Vyborov 的头像

    @evyborov

    counterpoint: idp isnt dead - its getting absorbed into agentic workflows. the meta-orchestrator layer is what actually matters now the real shift is from "process this doc" to "solve this problem using these docs"