Загрузка видео...

Не удалось загрузить видео

На главную

I built a multi-agent framework that pre-approves loan applications in under 5 minutes 🎉 1. Integrated 5 agents that make use of Experian and Plaid APIs for real-time credit and financial verification 2. The agents look up credit score, DTI, LTV, assets, property valuation and income to assess the...

312,580 просмотров • 1 год назад •via X (Twitter)

Комментарии: 10

Фото профиля Adam Silverman (Hiring!) 🖇️
Adam Silverman (Hiring!) 🖇️1 год назад

@Experian @Plaid great work @n_sri_laasya

Фото профиля Sri Laasya Nutheti 🖇️
Sri Laasya Nutheti 🖇️1 год назад

@Experian @Plaid Agentstack ftw 🤙

Фото профиля Erika⚡️⚡️
Erika⚡️⚡️1 год назад

@Experian @Plaid hell yeah

Фото профиля Sanket Dongre
Sanket Dongre1 год назад

@Experian @Plaid Imagine we have a software running on a PC which can track how an expert works and his workflow and builds out an agent prompt from his patterns.

Фото профиля João Moura
João Moura1 год назад

@Experian @Plaid Love this @n_sri_laasya will you opensource it?

Фото профиля george salapa 🜁
george salapa 🜁1 год назад

@Experian @Plaid this is very cool was it difficult to API to Plaid?

Фото профиля iamrobotbear (bk)
iamrobotbear (bk)1 год назад

@Experian @Plaid This is awesome, great work.

Фото профиля Shruti G
Shruti G1 год назад

@Experian @Plaid Amazing 🤩

Фото профиля build things that build things
build things that build things1 год назад

@Experian @Plaid Are these pydantic based?

Фото профиля Nima Ghamsari
Nima Ghamsari1 год назад

@Experian @Plaid This is so sick

Похожие видео

New Course: ACP: Agent Communication Protocol Learn to build agents that communicate and collaborate across different frameworks using ACP in this short course built with IBM Research's BeeAI, and taught by Sandi Besen, AI Research Engineer & Ecosystem Lead at IBM, and Nicholas Renotte, Head of AI Developer Advocacy at IBM. Building a multi-agent system with agents built or used by different teams and organizations can become challenging. You may need to write custom integrations each time a team updates their agent design or changes their choice of agentic orchestration framework. The Agent Communication Protocol (ACP) is an open protocol that addresses this challenge by standardizing how agents communicate, using a unified RESTful interface that works across frameworks. In this protocol, you host an agent inside an ACP server, which handles requests from an ACP client and passes them to the appropriate agent. Using a standardized client-server interface allows multiple teams to reuse agents across projects. It also makes it easier to switch between frameworks, replace an agent with a new version, or update a multi-agent system without refactoring the entire system. In this course, you’ll learn to connect agents through ACP. You’ll understand the lifecycle of an ACP Agent and how it compares to other protocols, such as MCP (Model Context Protocol) and A2A (Agent-to-Agent). You’ll build ACP-compliant agents and implement both sequential and hierarchical workflows of multiple agents collaborating using ACP. Through hands-on exercises, you’ll build: - A RAG agent with CrewAI and wrap it inside an ACP server. - An ACP Client to make calls to the ACP server you created. - A sequential workflow that chains an ACP server, created with Smolagents, to the RAG agent. - A hierarchical workflow using a router agent that transforms user queries into tasks, delegated to agents available through ACP servers. - An agent that uses MCP to access tools and ACP to communicate with other agents. You’ll finish up by importing your ACP agents into the BeeAI platform, an open-source registry for discovering and sharing agents. ACP enables collaboration between agents across teams and organizations. By the end of this course, you’ll be able to build ACP agents and workflows that communicate and collaborate regardless of framework. Please sign up here:

Andrew Ng

105,054 просмотров • 11 месяцев назад

How to setup a multi agent system? Bookmark it 📂 "The Trading Floor" Multi-Agent Market Analysis Council to analyze a stock ticker Z.ai GLM-4.7 🤝 OpenCode Agent framework: CrewAI How it works? 1. User enters a stock ticker to analyze 2. 5 AI agents wake up, each with distinct expertise: - Quant Analyst — technical indicators & price patterns - Sentiment Scout — market mood & crowd psychology - Macro Strategist — sector dynamics & economic context - Risk Manager — volatility, drawdowns & position sizing - Portfolio Chief — synthesizes all perspectives 3. Agents analyze independently using real market data 4. They debate, challenge assumptions, and identify disagreements 5. Portfolio Chief resolves conflicts and delivers a consensus recommendation 6. Final output: buy/hold/sell rating with confidence level, position size, and key risks How to built The Trading Floor? 1. Chose CrewAI as the agent framework — handles multi-agent orchestration out of the box 2. Defined 5 agents with distinct roles, goals, and backstories in Python 3. Built custom tools wrapping yfinance for real market data (prices, indicators, volatility) 4. Configured sequential workflow — specialists analyze first, Portfolio Chief synthesizes last 5. Set up FastAPI backend with SSE to stream agent thoughts in real-time 6. Built Next.js frontend to visualize the "board of directors" deliberating live 7. One environment variable (MODEL=openai/gpt-5.2) powers all agents 8. Generated unique agent icons with AI image tools Total cost: $0 for the framework, pay only for LLM API calls Tech stack: - GLM-4.7 with opencode to build the app - CrewAI (open source) for agent orchestration - GPT-5.2 powering each agent - FastAPI + SSE for real-time streaming - Next.js frontend showing live agent deliberations

CloudAI-X

57,703 просмотров • 5 месяцев назад

There's probably $100+ billion up for grabs for people who build startup for AI agents Over the next 10 years you're going to have a market of billions of customers (agents) with millions of wallets that want to use your services. TLDR; The internet was built for people: 1. Search google 2. Read landing page 3. Book demo 4. Talk to sales 5. Buy Agents don’t do that. Agents will: 1. Ask which product to use 2. Read your docs/pricing/security pages 3. Compare you to competitors 4. Check if you have an MCP/API/tool layer 5. Buy or recommend you without ever “visiting” your site like a person Everyone is going to have personal agents and business agents. This feels inevitable at this point. OpenClaw, Hermes, Claude Code, Codex, Google Spark. The tools are here. Which means there will be more agents on the internet than humans. So, where's the opportunity?? Go look at every SaaS tool you use. Notion. Slack. Jira. Google Analytics. Now ask: what is the version of this built purely for agents? Agent-native payments. Agent-native communication. Agent-native memory. Every category gets rebuilt. I clearly break down this shift and explain you everything on today's ep of The Startup Ideas Podcast (SIP) 🧃. Over the next 10 years you're going to have a market of billions of customers (agents) with millions of wallets that want to use your services. The founders who build for them now are going to look like the people who built websites in 1995. Might feel janky at the moment, but also obvious in hindsight. This is the next shift. Link over here: Watch

GREG ISENBERG

48,672 просмотров • 9 дней назад