Video wird geladen...

Video konnte nicht geladen werden

Beim Laden dieses Videos ist ein Problem aufgetreten. Dies könnte an einem vorübergehenden Netzwerkproblem liegen oder das Video ist möglicherweise nicht verfügbar.

A conversational agent with no hallucinations! This is huge! Here is the $1M problem: Build a customer-facing AI agent that works consistently, doesn't hallucinate, and is fully aligned with the business rules. Check out Parlant, a FREE, open-source library. I've talked about them before, and here is the TL;DR:... 1. Parlant gives you 10x more control over what your agent says 2. It helps you control how agents conduct conversations 3. It helps you control the service protocols and rules agents follow 4. It helps you control what agents can and can't say They do something pretty clever: 1. They have a set of predefined potential responses that the agent can use to reply to the customer. 2. When a customer sends a message, the agent generates a fluid response draft using an LLM and matches and renders the closest pre-approved reply template. 3. The agent returns the rendered pre-approved reply, not the one generated by the LLM. This maintains fluidity while avoiding unpredictability. Parlant also uses your domain terminology, invokes your tools, and implements self-critique to craft/evaluate its response iteratively. This pretty much solves any hallucination issues with your agent.show more

Santiago

451,858 subscribers

64,237 Aufrufe • vor 1 Jahr •via X (Twitter)

Wissenschaft & Technologie Nachrichten & Politik Bildung

Anya Rossi• Live Now

Private livecam show

11 Kommentare

Profilbild von Santiago

Santiagovor 1 Jahr

Here is the GitHub repository: And here is a paper showing the prompt engineering method Parlant uses behind the scenes (4.8% more accurate than Chain of Thought!):

Profilbild von AskLex.ai

AskLex.aivor 1 Jahr

Have AI answers to legal questions reviewed by a real lawyer instantly.

Profilbild von Mind Prison

Mind Prisonvor 1 Jahr

Sounds like the pre-LLM bots. Predefined responses. So we have gone full circle? Billions of dollars for slightly better predefined chatbot responses?

Profilbild von Santiago

Santiagovor 1 Jahr

"Slightly better predefined responses" is a solution that's indeed worth billions of dollars

Profilbild von Karl

Karlvor 1 Jahr

TBH that idea is quite old (m$ bot framework and intents etc). LLMs are only more general. Not allowing hallucinations is not resolving them. It's like not leaving your street to avoid a robbery.

Profilbild von luizfcouto

luizfcoutovor 1 Jahr

Love this! Pre approved templates are a smart way to avoid hallucinations with full control. We’ve been using Guardrail AI Agents, a bit more dynamic, with layered rules and validations instead of fixed replies. But honestly, combining both feels like the sweet spot for flexibility and safety.

Profilbild von Tech Brief Ai

Tech Brief Aivor 1 Jahr

This is a game-changer. Parlant’s hybrid approach — LLM creativity + strict response control — is exactly what customer-facing AI needs. You get natural, on-brand conversations without the risk of rogue replies or hallucinations. It’s not just smart — it’s deployment-ready. If you’re building serious AI agents for business, this isn’t optional anymore. It’s the new standard.

Profilbild von Danon 🛡️

Danon 🛡️vor 1 Jahr

How to use genAI to mimic the legacy NLU based chatbots 🤣. Probabilistic behavior is not a bug, but a feature. You don't hire a human agent for your contact center and tell him you are only allowed to use this list of pre approved sentences...

Profilbild von zee | ai web scraper

zee | ai web scrapervor 1 Jahr

So...use llm to choose which reply from the ancient chat bot to reply with? Lol hard pass

Profilbild von Arpit Sharma

Arpit Sharmavor 1 Jahr

Most agents today either sound robotic or go off-script entirely. This approach feels like it could finally bridge that gap.

Profilbild von Lukas Bug

Lukas Bugvor 1 Jahr

“No hallucinations” and “LLM” are mutually exclusive

Ähnliche Videos

This is huge! This fixes the universal problem with conversational agents: hallucinations! Every company that builds customer-facing agents struggles to align them with business rules and make them consistent. If you solve this, you'll become a hero overnight. Check out Parlant, a free, open-source library taking off on GitHub. This is why it's big: 1. You have 10x more control over what your conversation agent says 2. You control how it conducts conversations 3. You control the service protocols and rules it follows 4. You control what it can and can't say Here is how Parlant's engine works behind the scenes as soon as your agent receives a question from a customer: 1. It loads the necessary domain terminology 2. It finds the relevant guidelines to answer the question 3. It invokes your tools to gather any relevant information 4. It implements self-critique to craft/evaluate its response iteratively All of this makes it very hard for an agent to hallucinate. Here is the GitHub repository: And here is a paper showing the prompt engineering method Parlant uses behind the scenes (4.8% more accurate than Chain of Thought!):

This is huge! This fixes the universal problem with conversational agents: hallucinations! Every company that builds customer-facing agents struggles to align them with business rules and make them consistent. If you solve this, you'll become a hero overnight. Check out Parlant, a free, open-source library taking off on GitHub. This is why it's big: 1. You have 10x more control over what your conversation agent says 2. You control how it conducts conversations 3. You control the service protocols and rules it follows 4. You control what it can and can't say Here is how Parlant's engine works behind the scenes as soon as your agent receives a question from a customer: 1. It loads the necessary domain terminology 2. It finds the relevant guidelines to answer the question 3. It invokes your tools to gather any relevant information 4. It implements self-critique to craft/evaluate its response iteratively All of this makes it very hard for an agent to hallucinate. Here is the GitHub repository: And here is a paper showing the prompt engineering method Parlant uses behind the scenes (4.8% more accurate than Chain of Thought!):

Santiago

93,080 Aufrufe • vor 1 Jahr

This agent relies on a marketplace of 2.8M+ specialized agents to complete a task. This is how I imagine the future of personal agents. Here is how this works: 1. Agentverse is a marketplace of agents 2. Anyone can build and publish an agent there 3. ASI:One is a personal agent with access to the marketplace 4. To solve a task, ASI:One finds the best agent for the job In other words: You have an agent that can solve pretty much *anything* because it knows how to outsource the work to a network of specialized agents. And you don't need to do any setup to get this working. The way ranking agents in the marketplace works is pretty cool: Fetch.ai, the company behind it, created an AgentRank algorithm that works much like Google's PageRank. Every time an agent calls another, it forms a connection. Over time, these connections build into a graph of who relies on whom. An agent that is frequently called by other reputable agents scores higher and surfaces higher in results. The end result here is that your agent will consistently use the best agents in the marketplace to accomplish a goal. You should give this a try: You don't need to pay or even register to try these agents. Thanks to the team for partnering with me on this post.

This agent relies on a marketplace of 2.8M+ specialized agents to complete a task. This is how I imagine the future of personal agents. Here is how this works: 1. Agentverse is a marketplace of agents 2. Anyone can build and publish an agent there 3. ASI:One is a personal agent with access to the marketplace 4. To solve a task, ASI:One finds the best agent for the job In other words: You have an agent that can solve pretty much anything because it knows how to outsource the work to a network of specialized agents. And you don't need to do any setup to get this working. The way ranking agents in the marketplace works is pretty cool: Fetch.ai, the company behind it, created an AgentRank algorithm that works much like Google's PageRank. Every time an agent calls another, it forms a connection. Over time, these connections build into a graph of who relies on whom. An agent that is frequently called by other reputable agents scores higher and surfaces higher in results. The end result here is that your agent will consistently use the best agents in the marketplace to accomplish a goal. You should give this a try: You don't need to pay or even register to try these agents. Thanks to the team for partnering with me on this post.

Santiago

18,715 Aufrufe • vor 2 Monaten

Now you can use your favorite AI agent to control your Coinbase account (or a sub-account), with Coinbase for Agents. Here’s a quick demo on how to set it up and some of the cool things you can get your agent to do.

Now you can use your favorite AI agent to control your Coinbase account (or a sub-account), with Coinbase for Agents. Here’s a quick demo on how to set it up and some of the cool things you can get your agent to do.

Brian Armstrong

213,343 Aufrufe • vor 2 Monaten

Here is how simple it is to build a UI front-end for an AI agent (assuming you are using . The video here is 90 seconds and will show you everything you need to connect an agent to a web app: 1. Set up CopilotKit🪁 in your app 1. Copy the agent's localhost URL from LangGraph Studio 2. Paste that URL into a CopilotKit🪁 remote endpoint That's all you need to get a front-end to interact with the agent! The secret sauce here is CoAgents, an open-source library. You can use CoAgents to integrate any agent with your web application. Here is what you get: • Human-in-the-loop to steer and correct the agent • Stream intermediate agent state • Real-time state sharing between the agent and the application • Agentic generative UI to build trust that the agent is on the right path Watch the attached demo so you see it in action.

Here is how simple it is to build a UI front-end for an AI agent (assuming you are using . The video here is 90 seconds and will show you everything you need to connect an agent to a web app: 1. Set up CopilotKit🪁 in your app 1. Copy the agent's localhost URL from LangGraph Studio 2. Paste that URL into a CopilotKit🪁 remote endpoint That's all you need to get a front-end to interact with the agent! The secret sauce here is CoAgents, an open-source library. You can use CoAgents to integrate any agent with your web application. Here is what you get: • Human-in-the-loop to steer and correct the agent • Stream intermediate agent state • Real-time state sharing between the agent and the application • Agentic generative UI to build trust that the agent is on the right path Watch the attached demo so you see it in action.

Santiago

46,142 Aufrufe • vor 1 Jahr

This little device lets your agents do what they do best, whilst making sure you approve every important action. This is a Ledger Nano Gen5, a hardware signer that keeps your accounts secure. You can install a CLI and a set of skills in your projects. These will enable your agents to send their plan to the signer, so you can approve it. This is awesome: 1. You can have an automated agentic workflow 2. Your agents can't make costly mistakes Check the video I recorded to see how this works. You can run all of this in two commands: 1. Install the CLI 2. Install the skills for your agent From here, the agent can query my Ethereum accounts, check balances, and even initiate transactions as long as my Ledger Nano Gen5 is plugged into the computer. My keys are never stored in my computer and never shared with the agent. This is huge! Also, while the agent can set up transactions, it can't execute them unless a human approves them using the device. Pretty awesome! Thanks to the Ledger team for partnering with me on this post.

This little device lets your agents do what they do best, whilst making sure you approve every important action. This is a Ledger Nano Gen5, a hardware signer that keeps your accounts secure. You can install a CLI and a set of skills in your projects. These will enable your agents to send their plan to the signer, so you can approve it. This is awesome: 1. You can have an automated agentic workflow 2. Your agents can't make costly mistakes Check the video I recorded to see how this works. You can run all of this in two commands: 1. Install the CLI 2. Install the skills for your agent From here, the agent can query my Ethereum accounts, check balances, and even initiate transactions as long as my Ledger Nano Gen5 is plugged into the computer. My keys are never stored in my computer and never shared with the agent. This is huge! Also, while the agent can set up transactions, it can't execute them unless a human approves them using the device. Pretty awesome! Thanks to the Ledger team for partnering with me on this post.

Santiago

44,296 Aufrufe • vor 2 Monaten

It takes 5 minutes to create a world-class web research agent that runs 24/7 and returns structured search results. 1. You can limit the sources it's allowed to use 2. You can specify the goals it needs to complete 3. You can design the format structure of the results 4. You can configure how much computing power it will use I show you how to set up a Web Search Agent in the video. A few benefits here: 1. This is great for complex research tasks 2. It's really easy to add this like a LEGO piece to a more complex workflow 3. Create an agent once, and reuse it with different inputs 4. The agent adapts to your use case as you work with it By the way, Nimble published a whole library of templates and research agents you can reuse and modify. You can start sending queries to one of these existing agents, and it will begin to adapt to Go here to try it out: Thanks to the Nimble team for partnering with me on this post.

It takes 5 minutes to create a world-class web research agent that runs 24/7 and returns structured search results. 1. You can limit the sources it's allowed to use 2. You can specify the goals it needs to complete 3. You can design the format structure of the results 4. You can configure how much computing power it will use I show you how to set up a Web Search Agent in the video. A few benefits here: 1. This is great for complex research tasks 2. It's really easy to add this like a LEGO piece to a more complex workflow 3. Create an agent once, and reuse it with different inputs 4. The agent adapts to your use case as you work with it By the way, Nimble published a whole library of templates and research agents you can reuse and modify. You can start sending queries to one of these existing agents, and it will begin to adapt to Go here to try it out: Thanks to the Nimble team for partnering with me on this post.

Santiago

20,943 Aufrufe • vor 21 Tagen

AG-UI makes building agentic applications dramatically easier. Here's how it works. This is a model for a simple chatbot: User → LLM → Response But interactive agents that render UI, pause for approvals, and ask users for input need a much more complex model. When building these agents, a response from the LLM will include a series of state changes as the agent runs: • Agent started a task • Agent called a tool • Agent updated its state • Agent streams these tokens • Agent is waiting on a human • Agent is resuming the task The Agent-User Interaction Protocol (AG-UI) treats the LLM response as a stream of events rather than a text endpoint. In practice, here is what you get as an agent runs: 1. Lifecycle events so your UI knows where the agent is. 2. Text messages that stream tokens. 3. Tool calls so your UI can prefill a form with any required arguments. 4. State updates that keep your UI in sync with the agent. 5. Special events for human approvals, rich media, and custom needs. All of these events travel over standard transports (SSE, WebSockets, or plain HTTP) as JSON. As a result, you can build a frontend that stays in sync with the agent's progress without having to invent a custom process to make this happen. For example, building a human-in-the-loop workflow becomes an off-the-shelf component you can integrate rather than build from scratch. CopilotKit🪁 is the creator of AG-UI, and you can use it when building frontend applications pretty much anywhere: • React • Angular • Vue • React Native • Slack • Teams • Discord • WhatsApp • Telegram Here is the link for you to check it out: Thanks to the CopilotKit team for partnering with me on this post.

AG-UI makes building agentic applications dramatically easier. Here's how it works. This is a model for a simple chatbot: User → LLM → Response But interactive agents that render UI, pause for approvals, and ask users for input need a much more complex model. When building these agents, a response from the LLM will include a series of state changes as the agent runs: • Agent started a task • Agent called a tool • Agent updated its state • Agent streams these tokens • Agent is waiting on a human • Agent is resuming the task The Agent-User Interaction Protocol (AG-UI) treats the LLM response as a stream of events rather than a text endpoint. In practice, here is what you get as an agent runs: 1. Lifecycle events so your UI knows where the agent is. 2. Text messages that stream tokens. 3. Tool calls so your UI can prefill a form with any required arguments. 4. State updates that keep your UI in sync with the agent. 5. Special events for human approvals, rich media, and custom needs. All of these events travel over standard transports (SSE, WebSockets, or plain HTTP) as JSON. As a result, you can build a frontend that stays in sync with the agent's progress without having to invent a custom process to make this happen. For example, building a human-in-the-loop workflow becomes an off-the-shelf component you can integrate rather than build from scratch. CopilotKit🪁 is the creator of AG-UI, and you can use it when building frontend applications pretty much anywhere: • React • Angular • Vue • React Native • Slack • Teams • Discord • WhatsApp • Telegram Here is the link for you to check it out: Thanks to the CopilotKit team for partnering with me on this post.

Santiago

17,438 Aufrufe • vor 1 Monat

My agent is now paying for its own data. No API key. No account. No credit card. Check the video I recorded. This uses the x402 open protocol built by Coinbase, along with a simple skill. This is an open protocol governed by the Linux Foundation. To complete a goal, an agent can now search for an actor on the Apify Store, pay for it, and use it without any human intervention. The way it works is pretty simple: 1. Your agent finds an Actor it wants to use 2. It sends a request 3. The Actor sends back an HTTP 402 "Payment Required" response 4. Agent authorizes payment from a wallet in USDC on Base 5. The Actor runs 6. User receives the result The model is pay-as-you-go: the agent authorizes a spending ceiling, pays only for usage, and the remaining balance is automatically settled. This brings an entire marketplace of AI tools into the agentic economy. Here is the skill you need. Add it to your agent, and it will take care of everything for you: If you want to know how this works, including what you can do with $1, read this post: Thanks to the Apify team for partnering with me on this post.

My agent is now paying for its own data. No API key. No account. No credit card. Check the video I recorded. This uses the x402 open protocol built by Coinbase, along with a simple skill. This is an open protocol governed by the Linux Foundation. To complete a goal, an agent can now search for an actor on the Apify Store, pay for it, and use it without any human intervention. The way it works is pretty simple: 1. Your agent finds an Actor it wants to use 2. It sends a request 3. The Actor sends back an HTTP 402 "Payment Required" response 4. Agent authorizes payment from a wallet in USDC on Base 5. The Actor runs 6. User receives the result The model is pay-as-you-go: the agent authorizes a spending ceiling, pays only for usage, and the remaining balance is automatically settled. This brings an entire marketplace of AI tools into the agentic economy. Here is the skill you need. Add it to your agent, and it will take care of everything for you: If you want to know how this works, including what you can do with $1, read this post: Thanks to the Apify team for partnering with me on this post.

Santiago

26,865 Aufrufe • vor 1 Monat

INSANE: Grok 3 + Lovable = BEST AI Agent Apps!!!! Grok 3 generated the code for an AI agent that manages your Gmail - send, reply, and draft effortlessly Here's how it works: - Connect with your Gmail using Composio - Use Lovable to build an extremely cool frontend for the Agent - Agentic workflow with LlamaIndex Built with LlamaIndex 🦙 To connect your agents with more tools like Gmail, use

INSANE: Grok 3 + Lovable = BEST AI Agent Apps!!!! Grok 3 generated the code for an AI agent that manages your Gmail - send, reply, and draft effortlessly Here's how it works: - Connect with your Gmail using Composio - Use Lovable to build an extremely cool frontend for the Agent - Agentic workflow with LlamaIndex Built with LlamaIndex 🦙 To connect your agents with more tools like Gmail, use

Karan Vaidya

62,030 Aufrufe • vor 1 Jahr

You can spin up an AI workforce with one prompt. Here's why it works: it pulls the context the AI needs to lay the foundation. Give it: - your role - team size - the goals you want to hit. Then say "interview me." After that, build it out in four steps: 1) Start with 1 agent. - What does it feel like to work with one? 2) Make that agent proactive. - Now it's doing things on your behalf before you ask. 3) Expand to 2 agents. - One directs the other, or routes to it. - This is where you learn how context gets passed. 4) Scale the workforce. - A mission control where you watch it all move around. - Now you see what has to run in parallel, which agent never needed that tool, which one runs fine on a smaller model. - Not everything needs Opus. Sub-agents are haiku and sonnet. The catch: the prompt gets you agents with markdown files doing some stuff. Getting to the 90% plus level is iteration, and that part is specific to each person. Nobody can hand it to you. Start with one agent. Spin up one agent this week. The rest is discovery.

You can spin up an AI workforce with one prompt. Here's why it works: it pulls the context the AI needs to lay the foundation. Give it: - your role - team size - the goals you want to hit. Then say "interview me." After that, build it out in four steps: 1) Start with 1 agent. - What does it feel like to work with one? 2) Make that agent proactive. - Now it's doing things on your behalf before you ask. 3) Expand to 2 agents. - One directs the other, or routes to it. - This is where you learn how context gets passed. 4) Scale the workforce. - A mission control where you watch it all move around. - Now you see what has to run in parallel, which agent never needed that tool, which one runs fine on a smaller model. - Not everything needs Opus. Sub-agents are haiku and sonnet. The catch: the prompt gets you agents with markdown files doing some stuff. Getting to the 90% plus level is iteration, and that part is specific to each person. Nobody can hand it to you. Start with one agent. Spin up one agent this week. The rest is discovery.

The Startup Ideas Podcast (SIP) 🧃

18,006 Aufrufe • vor 11 Tagen

Agents shouldn't see your secrets. Today, most deployments hand the agent a real API key and hope for the best. That's why we're launching Infisical Agent Proxy. You give an agent a fake API key. The agent uses that key and the proxy swaps it for the real one at the network boundary before forwarding it outbound to its destination. An agent can't leak a secret it never sees. Build and deploy AI agents securely with Infisical Agent Proxy.

Agents shouldn't see your secrets. Today, most deployments hand the agent a real API key and hope for the best. That's why we're launching Infisical Agent Proxy. You give an agent a fake API key. The agent uses that key and the proxy swaps it for the real one at the network boundary before forwarding it outbound to its destination. An agent can't leak a secret it never sees. Build and deploy AI agents securely with Infisical Agent Proxy.

Infisical

28,086 Aufrufe • vor 25 Tagen

You can create an AI Agent that answers your email with a few clicks. 1. Go to ChatLLM ( 2. Click on AI Engineer 3. Select Create an AI Agent 4. Choose the Email Answering Agent ChatLLM will do the rest: it will code, test, and deploy the agent for you. You can also create a custom agent in English. The Agent Economy is coming (somebody should write a book and use this title.) We are going to see examples like this, times 1,000 in 2025. Just think about how many repetitive tasks you perform every day. Some of these tasks are involved enough that we couldn't automate them with pre-AI solutions. That's where we'll see agents explode, and I'm here for it.

You can create an AI Agent that answers your email with a few clicks. 1. Go to ChatLLM ( 2. Click on AI Engineer 3. Select Create an AI Agent 4. Choose the Email Answering Agent ChatLLM will do the rest: it will code, test, and deploy the agent for you. You can also create a custom agent in English. The Agent Economy is coming (somebody should write a book and use this title.) We are going to see examples like this, times 1,000 in 2025. Just think about how many repetitive tasks you perform every day. Some of these tasks are involved enough that we couldn't automate them with pre-AI solutions. That's where we'll see agents explode, and I'm here for it.

Santiago

79,974 Aufrufe • vor 1 Jahr

This is literally the easiest way to build an AI agent. Zero code. You only need to run a couple of commands. (I've said this before, but Google ADK is my favorite way to build code-first agents.) Here is what you need to do: 1. Open your terminal and create an empty folder 2. Run `uv init` inside the folder (if you don't have uv installed, you are really missing out!) 3. Install the google-adk library using the following command: `uv add google-adk`. 4. At this point, you can use the ask to create your agent with a single command: `uv run adk create --type=config my_agent`. This will ask you a couple of questions, including your GEMINI_API_KEY (you can create one online). 5. The command above will create a my_agent/root_agent.yaml file. Open it and add the following two lines at the end of the file so your agent can use Google to search for stuff: tools: - name: google_search 6. You have everything you need now. Run the adk web interface and start playing with your agent: `uv run adk web` That's it! Literally zero code. The agent works off the YAML configuration file.

This is literally the easiest way to build an AI agent. Zero code. You only need to run a couple of commands. (I've said this before, but Google ADK is my favorite way to build code-first agents.) Here is what you need to do: 1. Open your terminal and create an empty folder 2. Run `uv init` inside the folder (if you don't have uv installed, you are really missing out!) 3. Install the google-adk library using the following command: `uv add google-adk`. 4. At this point, you can use the ask to create your agent with a single command: `uv run adk create --type=config my_agent`. This will ask you a couple of questions, including your GEMINI_API_KEY (you can create one online). 5. The command above will create a my_agent/root_agent.yaml file. Open it and add the following two lines at the end of the file so your agent can use Google to search for stuff: tools: - name: google_search 6. You have everything you need now. Run the adk web interface and start playing with your agent: `uv run adk web` That's it! Literally zero code. The agent works off the YAML configuration file.

Santiago

140,922 Aufrufe • vor 8 Monaten

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.

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

We just open-sourced Simulang, a JavaScript library that gives you and your coding agents the ability to fully control computers. Simulang is our scripting framework for desktop automation. It allows you to write deterministic computer use code that can be replayed dozens if not hundreds of times. Much faster and cheaper, compared to LLM agents. It ships with a skill out of the box. That means you can turn natural language prompts into Simulang code directly, and your agent can now see the screen, click, type, and navigate. It gives your AI agents eyes and hands to control the computer like humans do. Try these things with Simulang: - upload your pile of invoices to the expense platform - find 50 people with specific criteria on LinkedIn - open your calculator app and do some math - find all buttons on your favorite app using accessibility tree - or draw a bunny with MS paint 🐰 In this demo, we show how Simulang took over when the coding agent couldn’t open and click on the target LinkedIn profile page. Give it a try:

Simular

14,452 Aufrufe • vor 3 Monaten

Postman is going all-in on AI! Their AI Agent Builder is live (and it's pretty powerful!) Postman's API Network has 100,000+ APIs and they just released a suite of tools for building AI Agents that can automatically discover and connect to any of these APIs. Think about it for a second: You can now build an AI agent that searches the network, discovers an API, processes its documentation, connects to it, and evaluates whether everything worked at the end of the process. This is a huge deal. Every person I know uses the Postman client to work with APIs. Now, they will have access to the AI Agent Builder, a complete suite for designing, building, testing, and deploying agents. I've built a few simple agents myself, and it's tough. The ability to discover and use an API automatically is really exciting (and a huge time saver if it works as promised!) In collaboration with the Postman team, who is sponsoring this post, I recorded a video with my thoughts about the Postman AI Agent Builder.

Postman is going all-in on AI! Their AI Agent Builder is live (and it's pretty powerful!) Postman's API Network has 100,000+ APIs and they just released a suite of tools for building AI Agents that can automatically discover and connect to any of these APIs. Think about it for a second: You can now build an AI agent that searches the network, discovers an API, processes its documentation, connects to it, and evaluates whether everything worked at the end of the process. This is a huge deal. Every person I know uses the Postman client to work with APIs. Now, they will have access to the AI Agent Builder, a complete suite for designing, building, testing, and deploying agents. I've built a few simple agents myself, and it's tough. The ability to discover and use an API automatically is really exciting (and a huge time saver if it works as promised!) In collaboration with the Postman team, who is sponsoring this post, I recorded a video with my thoughts about the Postman AI Agent Builder.

Santiago

230,594 Aufrufe • vor 1 Jahr

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:

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

New short course: Serverless Agentic Workflows with Amazon Bedrock. Learn to build and deploy serverless agents in this course created with Amazon Web Services and taught by Mike G Chambers, a Senior Developer Advocate at AWS specializing in GenAI. (Disclosure: I serve on Amazon's board.) Generative AI applications are becoming more complex, sophisticated, and agentic. Agentic applications have workloads that can be hard to predict in advance -- for example, what tools will it decide to call? -- and a serverless architecture helps you efficiently providing on-demand resources. This course teaches you to build and deploy a serverless agentic application. You’ll learn to create agents with tools, code execution, and guardrails, and build responsible agents for business use cases: - Build a customer service bot for a fictional tea mug business that can answering questions, retrieve information, and process orders. - Connect your customer service agent to a CRM to get customer info and log support tickets in real-time. - Explore how you invoke the agent, and see the trace to review the agent’s thought process and observation loop until it reaches its final output. - Attach a code interpreter to your agent, giving it the ability to perform accurate calculations by writing and running its own Python code. - Implement guardrails to prevent your agent from revealing sensitive information or using inappropriate language. By the end, you will have built a sophisticated AI agent capable of handling real-world customer support scenarios. Please sign up here!

New short course: Serverless Agentic Workflows with Amazon Bedrock. Learn to build and deploy serverless agents in this course created with Amazon Web Services and taught by Mike G Chambers, a Senior Developer Advocate at AWS specializing in GenAI. (Disclosure: I serve on Amazon's board.) Generative AI applications are becoming more complex, sophisticated, and agentic. Agentic applications have workloads that can be hard to predict in advance -- for example, what tools will it decide to call? -- and a serverless architecture helps you efficiently providing on-demand resources. This course teaches you to build and deploy a serverless agentic application. You’ll learn to create agents with tools, code execution, and guardrails, and build responsible agents for business use cases: - Build a customer service bot for a fictional tea mug business that can answering questions, retrieve information, and process orders. - Connect your customer service agent to a CRM to get customer info and log support tickets in real-time. - Explore how you invoke the agent, and see the trace to review the agent’s thought process and observation loop until it reaches its final output. - Attach a code interpreter to your agent, giving it the ability to perform accurate calculations by writing and running its own Python code. - Implement guardrails to prevent your agent from revealing sensitive information or using inappropriate language. By the end, you will have built a sophisticated AI agent capable of handling real-world customer support scenarios. Please sign up here!

Andrew Ng

81,048 Aufrufe • vor 1 Jahr

this ai agent is INSANE for creating & selling digital products... i built an agent that builds you digital products, helps you pick a niche, then gives you a full personalized blueprint to sell it. feed it a niche, the problem you're solving, and your desired outcome, one minute later you've got a ready-to-sell product and an ai assistant that helps you sell it. > it helps you find untapped niches in the digital product space > scans your niche for real problems, desires, and buyer personas > calculates whether the demand is actually worth launching into > once validated, it generates the full product in any format, pdf, notion template, ebook > gives you the exact path to sell it, even if you've never sold anything before. the output is a ready-to-sell product. go to your ai assistant, ask it how to sell, follow the blueprint. rt + reply "agent" and i'll send it to you so you can use it for your business (must be following so i can dm)

this ai agent is INSANE for creating & selling digital products... i built an agent that builds you digital products, helps you pick a niche, then gives you a full personalized blueprint to sell it. feed it a niche, the problem you're solving, and your desired outcome, one minute later you've got a ready-to-sell product and an ai assistant that helps you sell it. > it helps you find untapped niches in the digital product space > scans your niche for real problems, desires, and buyer personas > calculates whether the demand is actually worth launching into > once validated, it generates the full product in any format, pdf, notion template, ebook > gives you the exact path to sell it, even if you've never sold anything before. the output is a ready-to-sell product. go to your ai assistant, ask it how to sell, follow the blueprint. rt + reply "agent" and i'll send it to you so you can use it for your business (must be following so i can dm)

MONTE

13,838 Aufrufe • vor 1 Monat

The reason your AI gives generic answers isn't the model. It's that your company's knowledge lives in 12 different tools and your agent can't see any of it. So here's how to build a context database your agents can actually use: 1) Pull it in: - Slack, email, meetings, docs, tickets - Auto-collected on a schedule into one place. 2) Clean it up. - An agent files what matters and drops the noise, so your brain doesn't bloat. 3) Store it as memory. - Folders of files your agents read from and write back to as they learn. 4) Point your agents at it. - Now they draft, build, and ship with full context instead of guessing. Same model. Same agent. The difference is whether it can understand your company or not. Build the database once. Everything downstream gets smarter.

The reason your AI gives generic answers isn't the model. It's that your company's knowledge lives in 12 different tools and your agent can't see any of it. So here's how to build a context database your agents can actually use: 1) Pull it in: - Slack, email, meetings, docs, tickets - Auto-collected on a schedule into one place. 2) Clean it up. - An agent files what matters and drops the noise, so your brain doesn't bloat. 3) Store it as memory. - Folders of files your agents read from and write back to as they learn. 4) Point your agents at it. - Now they draft, build, and ship with full context instead of guessing. Same model. Same agent. The difference is whether it can understand your company or not. Build the database once. Everything downstream gets smarter.

The Startup Ideas Podcast (SIP) 🧃

13,598 Aufrufe • vor 2 Monaten