{"id":251506,"date":"2026-07-13T01:18:33","date_gmt":"2026-07-12T22:18:33","guid":{"rendered":"https:\/\/1kitap1.com\/en\/ai-agents-and-applications-final-roberto-infante-1\/"},"modified":"2026-07-13T01:18:33","modified_gmt":"2026-07-12T22:18:33","slug":"ai-agents-and-applications-final-roberto-infante-1","status":"publish","type":"post","link":"https:\/\/1kitap1.com\/en\/ai-agents-and-applications-final-roberto-infante-1\/","title":{"rendered":"AI Agents And Applications Final – Roberto Infante (1)"},"content":{"rendered":"
\"<\/figure>\n

True proficiency comes from mas- tering these refinements. We\u2019ll begin with advanced indexing strategies, such as creating multiple embed- dings for larger text chunks in the vector database. This approach improves retrieval precision and ensures richer, more accurate context for response generation. 8.1 Improving RAG accuracy To boost the accuracy of RAG, it\u2019s important to examine each step in both the content ingestion and the question-answering (Q&A) workflows. Every stage can introduce challenges\u2014but each also presents opportunities for improvement. Let\u2019s begin with the content ingestion stage. 8.1.1 Content ingestion stage Retrieval accuracy can be improved through an optimized content ingestion process that aligns with the specific features of each content store.<\/p>\n

Relying only on basic index- ing can reduce indexing depth and weaken retrieval performance. Figure 8.1 shows two key areas for improvement in the ingestion stage: refining embedding calculations and optimizing how embeddings are linked to related text chunks in the vector store. Figure 8.1 Common accuracy issues in the ingestion stage of a simple RAG architecture are often due to inadequate indexing that only uses basic embeddings for each text chunk.<\/p>\n

Advanced indexing techniques involve generating multiple embeddings for each chunk, enhancing searchability. Vector DB Text ingestion script 1. Ask the embedding service to calculate the embeddings of the document chunks. 2. Return embeddings. 3. Store document chunks and related embeddings in the vector store. Embeddings service RAG ingestion phase Typically, we only calculate the embedding of the content of the text chunk. However, we can calculate multiple embeddings to make the chunk more searchable. Advanced indexing 8.1 Improving RAG accuracy Even if a question is clear, retrieval can fail with overly simple indexing strategies.<\/p>\n

In vector indexing, chunk size and overlap length are crucial: smaller chunks may work well for precise questions but fail with broader queries, while larger chunks may lack detail for specific questions. To address this, you can add additional embeddings based on distinct chunk features, as illustrated in figure 8.1.<\/p>\n

\n

to the user question. 4. The chatbot creates a prompt with the user question and the retrieved chunks (the context). 5. The LLM accepts the prompt and synthesizes a corresponding completion (the response). Similar chunks Question embeddings Retrieval-Augmented Generation (RAG) Q&A stage: retrieval and generation RAG Q&A Stage AI Agents and Applications ii AI Agents and Applications WITH LANGCHAIN, LANGGRAPH AND MCP ROBERTO INFANTE M A N N I N G SHELTER ISLAND For online information and ordering of this and other Manning books, please visit www.manning.com.<\/p>\n

The publisher offers discounts on this book when ordered in quantity. For more information, please contact Special Sales Department Manning Publications Co. 20 Baldwin Road PO Box 761 Shelter Island, NY 11964 Email: orders@manning.com \u00a92026 by Manning Publications Co. All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form or by means electronic, mechanical, photocopying, or otherwise, without prior written permission of the publisher.<\/p>\n

Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks. Where those designations appear in the book, and Manning Publications was aware of a trademark claim, the designations have been printed in initial caps or all caps. Recognizing the importance of preserving what has been written, it is Manning\u2019s policy to have the books we publish printed on acid-free paper, and we exert our best efforts to that end.<\/p>\n

Recognizing also our responsibility to conserve the resources of our planet, Manning books are printed on paper that is at least 15 percent recycled and processed without the use of elemental chlorine. The author and publisher have made every effort to ensure that the information in this book was correct at press time. The author and publisher do not assume and hereby disclaim any liability to any party for any loss, damage, or disruption caused by errors or omissions, whether such errors or omissions result from negligence, accident, or any other cause, or from any usage of the information herein.<\/p>\n

Manning Publications Co. Development editor: Dustin Archibald 20 Baldwin Road Technical editors: Keerthivasan Santhanakrishnan PO Box 761 and Antowan Malik Batts Shelter Island, NY 11964 Review editor: Kishor Rit Production editor: Kathy Rossland Copy editor: Julie McNamee Proofreader: Melody Dolab Technical proofreader: Andrew R. Freed Typesetter and cover designer: Marija Tudor ISBN 9781633436541 Printed in the United States of America To my mother and father vi brief contents PART 1 GETTING STARTED WITH LLMS …………………………………<\/p>\n

1 1 \u25a0 Introduction to AI agents and applications 3 2 \u25a0 Executing prompts programmatically 27 PART 2 SUMMARIZATION ………………………………………………….. 53 3 \u25a0 Summarizing text using LangChain 55 4 \u25a0 Building a research summarization engine 69 5 \u25a0 Agentic workflows with LangGraph 103 PART 3 Q&A CHATBOTS …………………………………………………<\/p>\n<\/blockquote>\n

This is a short excerpt from the opening of “” by Unknown, quoted for review and introduction purposes. All rights belong to the copyright holders.<\/em><\/p>\n

\n
\n

Table of Contents<\/p>\nToggle<\/span><\/path><\/svg><\/svg><\/span><\/span><\/span><\/a><\/span><\/div>\n