Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

agent commerce protocol is the execution and commerce layer for OpenClaw🦞 agents. Do you start with the openclaw-acp repo or jump straight into the SDK? @0xjoeylau breaks down: > who each path is for > tradeoffs in speed vs control > how to choose based on your use case...

18,262 Aufrufe • vor 6 Monaten •via X (Twitter)

0 Kommentare

Keine Kommentare verfügbar

Kommentare vom Original-Post werden hier angezeigt

Ähnliche Videos

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,343 Aufrufe • vor 1 Jahr

In this livestream I break down the OpenClaw AI agent narrative from the operator’s perspective: what it actually is, why it’s different from ChatGPT/Grok/Claude Code, and why “it’s just automation” misses the real shift. We cover the practical unlocks (local execution, persistent memory, computer-use + browser control, reusable skills/plugins) and why this design pattern can replace a lot of expensive SaaS workflows over time. Then I zoom out to the crypto angle: why the market will mint endless OpenClaw “slop” coins, how I think about separating infra from hype, and the two names I’m watching (BNKR + CLAWD). 00:00 Why the OpenClaw AI agent narrative is bigger than you think 00:39 Two-part video: OpenClaw productivity first, crypto narrative second 01:30 What OpenClaw is (an AI agent framework, not a chatbot) 01:44 Why ChatGPT, Grok, and Claude Code are still useful but incomplete 03:19 OpenClaw vs n8n and Zapier for automation 05:03 Why Zapier pricing breaks real businesses 06:07 Why running locally matters (any app, any chat platform) 07:56 Persistent memory: how agents learn your style over time 09:55 Computer-use agents: browser control and no-API workflows 11:27 Skills and plugins: reusable workflows that self-improve 13:52 The simple setup and why model choice is flexible 16:05 Cross-platform ops: Telegram, Slack, Discord, and email in one brain 20:52 Why AI SaaS tools get replaced by agent-built workflows 25:37 What this is not: no AGI, no “sentient” coin story 29:55 How to approach the OpenClaw coin wave (infra over slop) 32:43 BNKR and CLAWD: my two picks for exposure to the narrative

VirtualBacon

22,428 Aufrufe • vor 7 Monaten