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

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

На главную

[Launch Week 1/5] Introducing Agent Identities Automation breaks at signup, login, or 2FA because agents rely on external accounts instead of their own. With Agent Identities, each agent gets a real email, phone and 2FA flow so it can sign up, log in and keep running without human intervention.

31,284 просмотров • 7 месяцев назад •via X (Twitter)

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

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

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

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

There are 8 billion people on earth. Soon there'll be 100 billion AI agents. Every one of them needs email. Six weeks ago I said the next wave of teams would run email through an agent instead of a dashboard. Today it ships. Nitrosend☄️ is launching Agentic Email Marketing: the email layer for the agent economy. What agents can do on Nitrosend right now: Sign themselves up. Point any agent at and it creates the account, connects your domain, sorts billing and sends its first email. No API key. No dashboard. No human required. Shipped, and users agents signing up with it daily. Get their own inboxes (beta, by request). Real addresses on the domain you own. Your agents receive, and send 1-1 email conversations with customers. A reply lands at 3am, your agent answers it. Anything that needs a human gets escalated to you. Ask us and we'll flick yours on. Next: Agentic Outreach (coming soon). Your agent studies your best customers, finds more like them, writes like a person, sends in sequence and works the replies. Then: set a goal and walk away. Goal-based agentic marketing is in development. "20% more activations this quarter" and Nitrosend plans, sends, measures and improves every week. Why we built this: Gmail is agent hostile and expensive per seat. Legacy email platforms assume a human sitting in a dashboard. agents needed an email layer of their own. They're already better at it than we are. They read everything, never miss a follow-up, and write personally at any scale. *94%* of actions on Nitrosend already happen inside an agent (Claude, Codex, ChatGPT, Cursor), not in our UI. Humans approve. Agents operate. This is our third email company. Six billion emails across the first two. We've been burned by every ugly part of email already, which is why the approval gates are built in exactly where you want them. Watch the launch, then send your agent to work: send it.

George Hartley ☄️

819,384 просмотров • 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:

Andrew Ng

105,343 просмотров • 1 год назад