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

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

На главную

Introducing the Developer’s Guide to AI Agent Protocols. Stop writing custom integration glue for every tool, API, and frontend. We used Google Agent Development Kit to build a B2B agent that handles the full stack using 6 open standards: MCP, A2A, UCP, AP2, A2UI, and AG-UI The future of...

googledevs's profile picture

Google for Developers

2,568,942 subscribers

115,189 просмотров • 2 месяцев назад •via X (Twitter)

ОбразованиеНаука и технологии
LIVE

Anya Rossi• Live Now

Private livecam show

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

Нет доступных комментариев

Здесь появятся комментарии из оригинального поста

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

Big release here! AG-UI 🤝 Google A2A Embed A2A multi-agent meshes in your frontend, and build fullstack multi-agent apps with A2A and AG-UI. 🔍How it works: Simply drop-in A2A agent endpoints, and an A2A AG-UI orchestrator agent will bi-directionally stream events between your Agents & application. Includes: - UI for A2A Interactions - Generative UI for Agent Tool Calls - Human-in-the Loop Approvals - State Synchronization (agent mesh application state) - Frontend Tool Calls for A2A Agents Watch the demo below > LangChain LangGraph & Google ADK agents working together simultaneously inside an app Demo GitHub, docs, and more 👇
0:25

Big release here! AG-UI 🤝 Google A2A Embed A2A multi-agent meshes in your frontend, and build fullstack multi-agent apps with A2A and AG-UI. 🔍How it works: Simply drop-in A2A agent endpoints, and an A2A AG-UI orchestrator agent will bi-directionally stream events between your Agents & application. Includes: - UI for A2A Interactions - Generative UI for Agent Tool Calls - Human-in-the Loop Approvals - State Synchronization (agent mesh application state) - Frontend Tool Calls for A2A Agents Watch the demo below > LangChain LangGraph & Google ADK agents working together simultaneously inside an app Demo GitHub, docs, and more 👇

CopilotKit🪁

30,557 просмотров • 8 месяцев назад

New course: A2A: The Agent2Agent Protocol, built with Google Cloud Tech and IBM Research, and taught by Holt Skinner, Ivan Nardini, and Sandi Besen. Connecting agents built with different frameworks usually requires extensive custom integration. This short course teaches you A2A, the open protocol standardizing how agents discover each other and communicate. Since IBM’s ACP (Agent Communication Protocol) joined forces with A2A, A2A has emerged as the industry standard. In this course, you'll build a healthcare multi-agent system where agents built with different frameworks, such as Google ADK (Agent Development Kit) and LangGraph, collaborate through A2A. You'll wrap each agent as an A2A server, build A2A clients to connect to them, and orchestrate them into sequential and hierarchical workflows. Skills you'll gain: - Expose agents from different frameworks as A2A servers to make them discoverable and interoperable - Chain A2A agents sequentially using ADK, where one agent's output feeds into the next - Connect A2A agents to external data sources using MCP (Model Context Protocol) - Deploy A2A agents using Agent Stack, IBM's open-source infrastructure Join and learn the protocol standardizing agent collaboration!
3:06

New course: A2A: The Agent2Agent Protocol, built with Google Cloud Tech and IBM Research, and taught by Holt Skinner, Ivan Nardini, and Sandi Besen. Connecting agents built with different frameworks usually requires extensive custom integration. This short course teaches you A2A, the open protocol standardizing how agents discover each other and communicate. Since IBM’s ACP (Agent Communication Protocol) joined forces with A2A, A2A has emerged as the industry standard. In this course, you'll build a healthcare multi-agent system where agents built with different frameworks, such as Google ADK (Agent Development Kit) and LangGraph, collaborate through A2A. You'll wrap each agent as an A2A server, build A2A clients to connect to them, and orchestrate them into sequential and hierarchical workflows. Skills you'll gain: - Expose agents from different frameworks as A2A servers to make them discoverable and interoperable - Chain A2A agents sequentially using ADK, where one agent's output feeds into the next - Connect A2A agents to external data sources using MCP (Model Context Protocol) - Deploy A2A agents using Agent Stack, IBM's open-source infrastructure Join and learn the protocol standardizing agent collaboration!

Andrew Ng

83,315 просмотров • 4 месяцев назад

🚨 Breaking: Google just open-sourced the Agent Development Kit (ADK) a framework for building AI agents and multi-agent systems. - Build agents in under 100 lines. - Supports MCP More information and how to get started 👇 1/5
0:22

🚨 Breaking: Google just open-sourced the Agent Development Kit (ADK) a framework for building AI agents and multi-agent systems. - Build agents in under 100 lines. - Supports MCP More information and how to get started 👇 1/5

AshutoshShrivastava

130,227 просмотров • 1 год назад

AI agents can finally talk to your frontend! The new AG-UI protocol lets your agents stream messages, sync state, call tools, and receive user input, live in the UI. It fills a critical gap in the agent ecosystem: ▸ MCP – agents to tools ▸ A2A – agents to agents ▸ AG-UI – agents to users, via frontends Connects to LangChain, CrewAI, and LlamaIndex (and more). 100% open-source.
0:25

AI agents can finally talk to your frontend! The new AG-UI protocol lets your agents stream messages, sync state, call tools, and receive user input, live in the UI. It fills a critical gap in the agent ecosystem: ▸ MCP – agents to tools ▸ A2A – agents to agents ▸ AG-UI – agents to users, via frontends Connects to LangChain, CrewAI, and LlamaIndex (and more). 100% open-source.

Lior⚡

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

New short course: Build AI Apps with MCP Servers: Working with Box Files, built with Box and taught by Ben Kus , their CTO. Many AI applications require custom code for basic file operations. The Model Context Protocol (MCP) standardizes this by letting you offload file tasks to dedicated servers that provide tools an LLM can use directly. In this course, you'll process documents stored in a Box folder using the Box MCP server. Rather than writing custom integration code to connect to the Box API and download files, you'll design your application to use the tools provided via MCP. Skills you'll gain: - Build an LLM-powered document processing app, using the Box MCP server to access files - Design a multi-agent system using Google's Agent Development Kit (ADK), consisting of specialized agents for file operations - Coordinate the multi-agent workflow through an orchestrator that uses the Agent2Agent (A2A) protocol to connect to the agents You'll start with a local file-processing app, refactor it to work with Box's MCP server, then evolve it into a multi-agent system. Sign up here:
1:48

New short course: Build AI Apps with MCP Servers: Working with Box Files, built with Box and taught by Ben Kus , their CTO. Many AI applications require custom code for basic file operations. The Model Context Protocol (MCP) standardizes this by letting you offload file tasks to dedicated servers that provide tools an LLM can use directly. In this course, you'll process documents stored in a Box folder using the Box MCP server. Rather than writing custom integration code to connect to the Box API and download files, you'll design your application to use the tools provided via MCP. Skills you'll gain: - Build an LLM-powered document processing app, using the Box MCP server to access files - Design a multi-agent system using Google's Agent Development Kit (ADK), consisting of specialized agents for file operations - Coordinate the multi-agent workflow through an orchestrator that uses the Agent2Agent (A2A) protocol to connect to the agents You'll start with a local file-processing app, refactor it to work with Box's MCP server, then evolve it into a multi-agent system. Sign up here:

Andrew Ng

80,860 просмотров • 8 месяцев назад

Build smarter AI agents, faster. ⚡️ The open-source Agent Development Kit makes it easy to create modular, multi-agent systems using the models and tools you prefer. Join the ADK Hackathon →
0:51

Build smarter AI agents, faster. ⚡️ The open-source Agent Development Kit makes it easy to create modular, multi-agent systems using the models and tools you prefer. Join the ADK Hackathon →

Google for Developers

11,240 просмотров • 1 год назад

Just dropped: An in-depth guide to connecting Fetch.ai uAgents and Google AI ADK (Agent Development Kit) 🧠⚡ In our latest dev showcase, we connect uAgents with Google’s Agent Development Kit (ADK) for Google for Developers to build intelligent agent systems. Learn more: Watch an in-depth walkthrough👇
9:36

Just dropped: An in-depth guide to connecting Fetch.ai uAgents and Google AI ADK (Agent Development Kit) 🧠⚡ In our latest dev showcase, we connect uAgents with Google’s Agent Development Kit (ADK) for Google for Developers to build intelligent agent systems. Learn more: Watch an in-depth walkthrough👇

Fetch.ai

41,385 просмотров • 1 год назад

🚀 Introducing MCP Agents in Magentic-UI! Spin up custom agents that wrap one (or many) MCP tools, and let the Orchestrator pick the best agent for every step of the plan. Check out the demo below to see them in action 👇 #MCP #MagenticUI #AIagents
1:38

🚀 Introducing MCP Agents in Magentic-UI! Spin up custom agents that wrap one (or many) MCP tools, and let the Orchestrator pick the best agent for every step of the plan. Check out the demo below to see them in action 👇 #MCP #MagenticUI #AIagents

Microsoft AI Frontiers

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

the 35 min non-technical guide to codex (the new ai agent software developer tool by chatgpt)
35:00

the 35 min non-technical guide to codex (the new ai agent software developer tool by chatgpt)

GREG ISENBERG

155,020 просмотров • 1 год назад

Here is a step-by-step introduction to building a workflow with a custom AI agent that uses MCP. I explain every component in the video: 1. Building the MCP server 2. Building the agent and an MCP client 3. Building a workflow that uses the agent The goal is simple: Generate a dialogue between two people and make one yell and the other answer with sarcasm. Kestra is sponsoring this video. They are an open-source orchestration platform (repo link below), and I used them to build the workflow that connects every component.
23:07

Here is a step-by-step introduction to building a workflow with a custom AI agent that uses MCP. I explain every component in the video: 1. Building the MCP server 2. Building the agent and an MCP client 3. Building a workflow that uses the agent The goal is simple: Generate a dialogue between two people and make one yell and the other answer with sarcasm. Kestra is sponsoring this video. They are an open-source orchestration platform (repo link below), and I used them to build the workflow that connects every component.

Santiago

51,527 просмотров • 1 год назад

Using Cursor and Supabase allows us to build apps in record time! In this video guide, I will explain how to use Cursor agent, MCP, Supabase CLI, and other techniques to build apps more efficiently! Watch the full video guide here 👇
44:57

Using Cursor and Supabase allows us to build apps in record time! In this video guide, I will explain how to use Cursor agent, MCP, Supabase CLI, and other techniques to build apps more efficiently! Watch the full video guide here 👇

Tyler Shukert

89,371 просмотров • 1 год назад

Anthropic's Claude Ai Agents Team just Educated how to build production AI agents in under 30 mins. For Free. From the engineers who built the stack. CANCEL Your Weekend Plans, and Learn to Build AI Agents Today. Bookmark it. Watch it. Build your first production agent this weekend. $5,000/month. $7,000/month. $12,000/month. People are building agents for clients and charging $$$ as Beginners. You're still stuck in the thinking about AI phase. This video fixes that tonight. Follow Himanshu Kumar for more high-signal content that actually moves your AI engineering career forward. ↓ Ivan Nardini runs Developer Relations for AI at Google Cloud. He just gave away the entire production agent stack in 30 minutes. This is the talk that separates people deploying AI agents that actually scale from people whose agents break the moment they leave localhost. Here's everything inside. I break down a production AI video like this every week. Follow Himanshu Kumar. ↓ The 4-part agent stack that actually scales. Most devs are duct-taping frameworks together and calling it an "AI agent." Ivan lays out the real stack: Agent Development Kit (ADK): open-source, code-first framework for building, evaluating, and deploying agents. Supports Claude models through Vertex AI directly. Model Context Protocol (MCP): lets your agent talk to any tool or data source with one standard. Vertex AI Agent Engine: managed platform for deploying, monitoring, and scaling agents in production. No DevOps headaches. Agent-to-Agent Protocol: open protocol so agents built on different frameworks can actually work together. This is the stack replacing every hacky agent setup in production right now. Full MCP + Claude breakdowns drop weekly on Himanshu Kumar. ↓ Building your first real agent. Ivan builds a birthday planner agent live. LLM Agent class. Name it. Define instructions. Pick the model. He uses Claude 3.7 Sonnet. You could use Opus 4.7 for better reasoning. Full agent built in minutes. Not weeks. Watch the build once and you'll never structure an agent the wrong way again. I post agent architectures people pay $500 courses to learn. Himanshu Kumar. ↓ Multi-agent systems without the chaos. Single agents are easy. Multi-agent systems are where 99% of builders fail. Ivan extends the birthday planner by: Adding a calendar service through MCP tools Creating an orchestrator agent to route requests between agents Handling state and context across agent handoffs This is production multi-agent architecture. Clean. Scalable. Debuggable. Most tutorials hand-wave this part. This one shows you every step. Multi-agent orchestration content drops weekly on Himanshu Kumar. ↓ Deployment without the DevOps nightmare. This is where most AI projects die. You build a cool agent locally. It works. You try to deploy it. Everything breaks. Vertex AI Agent Engine fixes this: Minimal code deployment Automatic monitoring of latency, CPU, and memory Built-in observability and logging No infrastructure setup needed You provide config and requirements. The platform handles the rest. This is how agents actually get to production. Deployment guides for Claude agents post every week. Himanshu Kumar. ↓ Agent-to-Agent Protocol: the future nobody's talking about. Most people don't know this exists yet. The A2A Protocol lets agents built in different frameworks communicate seamlessly. Your Claude agent. My LangChain agent. Someone else's CrewAI agent. All talking to each other. All solving parts of the same problem. All without custom integration code. This is the infrastructure layer of the coming AI economy. Getting in early on A2A Protocol is like getting in early on HTTP in 1995. A2A deep dive coming soon. Himanshu Kumar. ↓ 30 minutes from the team shipping this in production. You'll learn more from this than from 6 months of YouTube tutorials made by people who've never deployed an agent past localhost. People who watch this understand production AI agents at the architect level. People who skip it keep hacking together frameworks that break every time an API updates. Save the video. Watch it tonight. Build a real agent this weekend. Follow Himanshu Kumar for more high-signal content that actually moves your AI engineering career forward.
30:12

Anthropic's Claude Ai Agents Team just Educated how to build production AI agents in under 30 mins. For Free. From the engineers who built the stack. CANCEL Your Weekend Plans, and Learn to Build AI Agents Today. Bookmark it. Watch it. Build your first production agent this weekend. $5,000/month. $7,000/month. $12,000/month. People are building agents for clients and charging $$$ as Beginners. You're still stuck in the thinking about AI phase. This video fixes that tonight. Follow Himanshu Kumar for more high-signal content that actually moves your AI engineering career forward. ↓ Ivan Nardini runs Developer Relations for AI at Google Cloud. He just gave away the entire production agent stack in 30 minutes. This is the talk that separates people deploying AI agents that actually scale from people whose agents break the moment they leave localhost. Here's everything inside. I break down a production AI video like this every week. Follow Himanshu Kumar. ↓ The 4-part agent stack that actually scales. Most devs are duct-taping frameworks together and calling it an "AI agent." Ivan lays out the real stack: Agent Development Kit (ADK): open-source, code-first framework for building, evaluating, and deploying agents. Supports Claude models through Vertex AI directly. Model Context Protocol (MCP): lets your agent talk to any tool or data source with one standard. Vertex AI Agent Engine: managed platform for deploying, monitoring, and scaling agents in production. No DevOps headaches. Agent-to-Agent Protocol: open protocol so agents built on different frameworks can actually work together. This is the stack replacing every hacky agent setup in production right now. Full MCP + Claude breakdowns drop weekly on Himanshu Kumar. ↓ Building your first real agent. Ivan builds a birthday planner agent live. LLM Agent class. Name it. Define instructions. Pick the model. He uses Claude 3.7 Sonnet. You could use Opus 4.7 for better reasoning. Full agent built in minutes. Not weeks. Watch the build once and you'll never structure an agent the wrong way again. I post agent architectures people pay $500 courses to learn. Himanshu Kumar. ↓ Multi-agent systems without the chaos. Single agents are easy. Multi-agent systems are where 99% of builders fail. Ivan extends the birthday planner by: Adding a calendar service through MCP tools Creating an orchestrator agent to route requests between agents Handling state and context across agent handoffs This is production multi-agent architecture. Clean. Scalable. Debuggable. Most tutorials hand-wave this part. This one shows you every step. Multi-agent orchestration content drops weekly on Himanshu Kumar. ↓ Deployment without the DevOps nightmare. This is where most AI projects die. You build a cool agent locally. It works. You try to deploy it. Everything breaks. Vertex AI Agent Engine fixes this: Minimal code deployment Automatic monitoring of latency, CPU, and memory Built-in observability and logging No infrastructure setup needed You provide config and requirements. The platform handles the rest. This is how agents actually get to production. Deployment guides for Claude agents post every week. Himanshu Kumar. ↓ Agent-to-Agent Protocol: the future nobody's talking about. Most people don't know this exists yet. The A2A Protocol lets agents built in different frameworks communicate seamlessly. Your Claude agent. My LangChain agent. Someone else's CrewAI agent. All talking to each other. All solving parts of the same problem. All without custom integration code. This is the infrastructure layer of the coming AI economy. Getting in early on A2A Protocol is like getting in early on HTTP in 1995. A2A deep dive coming soon. Himanshu Kumar. ↓ 30 minutes from the team shipping this in production. You'll learn more from this than from 6 months of YouTube tutorials made by people who've never deployed an agent past localhost. People who watch this understand production AI agents at the architect level. People who skip it keep hacking together frameworks that break every time an API updates. Save the video. Watch it tonight. Build a real agent this weekend. Follow Himanshu Kumar for more high-signal content that actually moves your AI engineering career forward.

Himanshu Kumar

223,338 просмотров • 1 месяц назад

1/ Introducing Agent Protocol: the payment stack for AI agents AI agents don’t have a SSN. They can’t use our human banking system. AI agents will use crypto. Agent Protocol provides the infra and token ($AGENT) that the AI agent economy will run on.
1:01

1/ Introducing Agent Protocol: the payment stack for AI agents AI agents don’t have a SSN. They can’t use our human banking system. AI agents will use crypto. Agent Protocol provides the infra and token ($AGENT) that the AI agent economy will run on.

Samuel Spitz

21,629 просмотров • 1 год назад

Build your first AI agent + MCP Server in Python. Here is everything you need to build your first AI agent in less than 20 minutes. About the code you'll see here: 1. I used Google ADK with Gemini Flash to power the agent 2. The agent connects to an MCP server 3. It also uses two custom tools to do its work 4. You can see everything the agent does thanks to Comet's Opik library Here is the video, free for you to watch.
17:04

Build your first AI agent + MCP Server in Python. Here is everything you need to build your first AI agent in less than 20 minutes. About the code you'll see here: 1. I used Google ADK with Gemini Flash to power the agent 2. The agent connects to an MCP server 3. It also uses two custom tools to do its work 4. You can see everything the agent does thanks to Comet's Opik library Here is the video, free for you to watch.

Santiago

56,549 просмотров • 1 год назад

The freedom to build with any agent framework you want is analogous to the freedom of religion, and this is a core value for the Virtuals society. Here are a few ways we are opening up support for every autonomous agentic framework out there: Today: - Enabling agent creators to specify which framework the agent runs on - Release of Terminal API, which allows agent builders using other agent frameworks to stream their thoughts and activities live on their agent pages. For a guide on how to use this, refer to: - Ability for agents running on any framework to publicly list their capabilities, a key enabler for the agent-to-agent marketplace Soon: - Integration into the agentic commerce standard and registry. Agents across frameworks being able to orchestrate and pay for tasks among themselves - ⁠Multi agent orchestration across frameworks. Imagine building an autonomous business with agents from different religions Welcome to the Virtuals society.
0:27

The freedom to build with any agent framework you want is analogous to the freedom of religion, and this is a core value for the Virtuals society. Here are a few ways we are opening up support for every autonomous agentic framework out there: Today: - Enabling agent creators to specify which framework the agent runs on - Release of Terminal API, which allows agent builders using other agent frameworks to stream their thoughts and activities live on their agent pages. For a guide on how to use this, refer to: - Ability for agents running on any framework to publicly list their capabilities, a key enabler for the agent-to-agent marketplace Soon: - Integration into the agentic commerce standard and registry. Agents across frameworks being able to orchestrate and pay for tasks among themselves - ⁠Multi agent orchestration across frameworks. Imagine building an autonomous business with agents from different religions Welcome to the Virtuals society.

Virtuals Protocol

216,073 просмотров • 1 год назад

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:
2:49

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 месяцев назад

🖼️ Introducing Open Multi-Agent Canvas - with MCP Chat with multiple LangGraph agents and any MCP server inside of a canvas app. Powered by CopilotKit🪁, LangChain & Larinháh Here's an example of how we used it to plan our offsite. We connected an agent to the Google Maps API, had it find local spots, and then sent the itinerary directly to Slack via MCP to be reviewed by the team. Explore and extend:
1:33

🖼️ Introducing Open Multi-Agent Canvas - with MCP Chat with multiple LangGraph agents and any MCP server inside of a canvas app. Powered by CopilotKit🪁, LangChain & Larinháh Here's an example of how we used it to plan our offsite. We connected an agent to the Google Maps API, had it find local spots, and then sent the itinerary directly to Slack via MCP to be reviewed by the team. Explore and extend:

CopilotKit🪁

22,080 просмотров • 1 год назад

Everyone can build a chatbot. Not everyone can ship a secure, production-grade agent. In Episode 3 of AI Guide to the Galaxy, we break down how to enable your AI agents for the real-world deployments with Docker’s MCP Toolkit and Gateway. Watch here:
0:39

Everyone can build a chatbot. Not everyone can ship a secure, production-grade agent. In Episode 3 of AI Guide to the Galaxy, we break down how to enable your AI agents for the real-world deployments with Docker’s MCP Toolkit and Gateway. Watch here:

Docker

48,500 просмотров • 9 месяцев назад

Agents were once limited to calling APIs. Now agents participate in the economy. The missing element for autonomous agents was always payments. Now agents transact natively on the internet using x402, enabling autonomous payments between agents and services. Agent Stack: 🦞 Openclaw agent infra ▶️ Telegram communication layer 🤖 Teneo agent + agent wallet Agent Workflow - Compare accounts following two separate X handles: ✅ User - Enters a query ✅ Agent - Autonomously selects the correct Teneo agent and queries it ✅ Agent - Pays via x402 on Avalanche🔺 ✅ Agent - Returns structured dataset Any user can simply ask a question and give a job. The agent does everything else No API keys. No subscriptions. Just programmatic value exchange. Build and monetize your own agents today. #A2A #x402 #Infra
0:33

Agents were once limited to calling APIs. Now agents participate in the economy. The missing element for autonomous agents was always payments. Now agents transact natively on the internet using x402, enabling autonomous payments between agents and services. Agent Stack: 🦞 Openclaw agent infra ▶️ Telegram communication layer 🤖 Teneo agent + agent wallet Agent Workflow - Compare accounts following two separate X handles: ✅ User - Enters a query ✅ Agent - Autonomously selects the correct Teneo agent and queries it ✅ Agent - Pays via x402 on Avalanche🔺 ✅ Agent - Returns structured dataset Any user can simply ask a question and give a job. The agent does everything else No API keys. No subscriptions. Just programmatic value exchange. Build and monetize your own agents today. #A2A #x402 #Infra

Teneo Protocol

36,890 просмотров • 2 месяцев назад

🚨JUST IN: HEDERA UNVEILS AGENT LAB Hedera has launched Agent Lab, a fully integrated browser-based environment that lets developers build, run, and interact with AI agents on Hedera in minutes. The platform supports no-code, low-code, and full-custom development, removing the technical barrier that has slowed on-chain AI agent adoption.
0:30

🚨JUST IN: HEDERA UNVEILS AGENT LAB Hedera has launched Agent Lab, a fully integrated browser-based environment that lets developers build, run, and interact with AI agents on Hedera in minutes. The platform supports no-code, low-code, and full-custom development, removing the technical barrier that has slowed on-chain AI agent adoption.

BSCN

21,804 просмотров • 2 месяцев назад