Video yükleniyor...

Video Yüklenemedi

Ana Sayfaya Dön

APIs are a bottleneck, not a solution! AI agents can't access 95% of the web because most websites simply don't have APIs. Supplier portals, appointment systems, regional job boards, etc., none of them have developer APIs. The valuable data lives behind logins, multi-step forms, and interfaces built for humans,...

akshay_pachaar's profile picture

Akshay 🚀

274,941 subscribers

62,659 görüntüleme • 8 ay önce •via X (Twitter)

EğitimBilim & Teknoloji
LIVE

Anya Rossi• Live Now

Private livecam show

0 Yorum

Yorum bulunmuyor

Orijinal gönderinin yorumları burada görünecek

Benzer Videolar

The web was built for humans. And honestly, that's fine for you guys. But the next trillion internet users are AI agents, robots, and devices who act on your behalf - booking appointments, filling forms, placing orders, and getting things done - using sites that will never, ever have APIs. 95% of the economy falls into this Deep Web of HTML mess designed for humans, not agents. Oh, those generic computer use agents aren't taking you anywhere. They're too slow, too expensive, they hallucinate, and are nondeterministic to rely on. That changes now. This is me, Mino, a web agents API to build on this Deep Web. I take a goal in simple language and execute it on websites that were never meant to be automated. Massive companies like Google, DoorDash, ClassPass are already using me to do their homework. Now it’s your turn. How though? I actually understand what's on the page - parsing structure and identifying elements. I use AI once to understand everything, codify my successes, and get better and faster with every run. You get: → 85-95% success rate on complex workflows → Pennies per job (stop wasting $$ on one job) → Parallel execution across multiple sites → Structured JSON outputs. Every. Single. Time. The web wasn't built for agents. I forced it to work anyway. Go build something real. 50 completed runs on the house:
1:41

The web was built for humans. And honestly, that's fine for you guys. But the next trillion internet users are AI agents, robots, and devices who act on your behalf - booking appointments, filling forms, placing orders, and getting things done - using sites that will never, ever have APIs. 95% of the economy falls into this Deep Web of HTML mess designed for humans, not agents. Oh, those generic computer use agents aren't taking you anywhere. They're too slow, too expensive, they hallucinate, and are nondeterministic to rely on. That changes now. This is me, Mino, a web agents API to build on this Deep Web. I take a goal in simple language and execute it on websites that were never meant to be automated. Massive companies like Google, DoorDash, ClassPass are already using me to do their homework. Now it’s your turn. How though? I actually understand what's on the page - parsing structure and identifying elements. I use AI once to understand everything, codify my successes, and get better and faster with every run. You get: → 85-95% success rate on complex workflows → Pennies per job (stop wasting $$ on one job) → Parallel execution across multiple sites → Structured JSON outputs. Every. Single. Time. The web wasn't built for agents. I forced it to work anyway. Go build something real. 50 completed runs on the house:

TinyFish

656,586 görüntüleme • 9 ay önce

This is how you can get programmatic access to any website. You need two things: 1. The URL of the website 2. A prompt specifying what you want to do on the site Mino is a neat platform that uses browser automation and AI-powered navigation to understand your prompt, open the website, and extract the information you want. This opens the doors to unlimited potential automations you could build using data from everyday websites that don't give you an API. Mino uses AI to go way further than you could get by using a regular web scraping tool: • It can handle dynamic JavaScript content • It can handle login walls • It can navigate through interactive booking flows • It adapts to different interfaces and layout changes • It can fill out forms automatically • It supports stealth browser mode In my experience, running Mino on relatively straightforward sites takes about 30-60 seconds to complete. The more times you run it, the faster it gets. I recorded a quick video to show you the platform. You can check their site here: Thanks to the team for the support, onboarding me on their platform, and the collaboration on this post.
5:10

This is how you can get programmatic access to any website. You need two things: 1. The URL of the website 2. A prompt specifying what you want to do on the site Mino is a neat platform that uses browser automation and AI-powered navigation to understand your prompt, open the website, and extract the information you want. This opens the doors to unlimited potential automations you could build using data from everyday websites that don't give you an API. Mino uses AI to go way further than you could get by using a regular web scraping tool: • It can handle dynamic JavaScript content • It can handle login walls • It can navigate through interactive booking flows • It adapts to different interfaces and layout changes • It can fill out forms automatically • It supports stealth browser mode In my experience, running Mino on relatively straightforward sites takes about 30-60 seconds to complete. The more times you run it, the faster it gets. I recorded a quick video to show you the platform. You can check their site here: Thanks to the team for the support, onboarding me on their platform, and the collaboration on this post.

Santiago

31,789 görüntüleme • 9 ay önce

how to use firecrawl to give your AI eyes and actually build startups that outperform 99% of apps: 1. your AI is smart but blind. it can't go to a website, read a page, or grab data on its own. firecrawl fixes that. you put in a URL. you get back clean markdown, structured JSON, screenshots. feed it to any model. 2. three lines of code. that's it. no proxies. no anti-bot detection. no custom scrapers that break when a site changes. one API call. clean data back in seconds. works on 98%+ of sites. 3. firecrawl has six core capabilities: scrape a single page. crawl an entire site. map all URLs on a domain. search google and return full content. an agent endpoint where you describe what you want and it goes and finds it. and a browser sandbox where AI controls a real browser like filling forms, clicking buttons, handles logins. 4. the agent endpoint is wild. you can say "find all of YC's winter 24 dev tool companies and their founders and emails" and get back structured data. or "compare pricing tiers across stripe, square, and paypal" and get a side-by-side table. 5. the browser sandbox lets your AI stay logged in across sessions, navigate pagination, watch live as it browses. this is computer use without building the infrastructure yourself. 6. think of it in layers. every builder needs: an agent harness (claude code, cursor, codex), a search layer (perplexity, exa), a web data layer (firecrawl), an ops brain (obsidian, notion), and an outbound stack. the web data layer is the one most people are sleeping on. 7. this is the AWS moment for web data. in 2006 building a web app meant buying servers and managing racks. AWS said one API call, use our servers. some of the biggest companies of the last decade were built on that. firecrawl is doing the same thing for web data in 2026. 8. the framework i'd use for coming up with startup ideas building with clean data: take a massive horizontal platform. rebuild it for one niche using firecrawl. the vertical version always wins because people want specific, not generic. price for outcome. 9. a year ago firecrawl posted a job listing that said "please only apply if you're an AI agent." content creator agents. customer support agents. junior dev agents. it looked weird. it was a signal for where this is all going. the people who understand how to get clean web data, wrap it around an LLM, and package it as a product are the the ones with a 12-month head start. i use Firecrawl with Idea Browser . once you see what's possible with structured web data, you can't unsee it. episode is live on The Startup Ideas Podcast (SIP) 🧃 (full breakdown there) i tried to explain this as clear as possible for even the non technical. send it to a builder friend. watch
27:27

how to use firecrawl to give your AI eyes and actually build startups that outperform 99% of apps: 1. your AI is smart but blind. it can't go to a website, read a page, or grab data on its own. firecrawl fixes that. you put in a URL. you get back clean markdown, structured JSON, screenshots. feed it to any model. 2. three lines of code. that's it. no proxies. no anti-bot detection. no custom scrapers that break when a site changes. one API call. clean data back in seconds. works on 98%+ of sites. 3. firecrawl has six core capabilities: scrape a single page. crawl an entire site. map all URLs on a domain. search google and return full content. an agent endpoint where you describe what you want and it goes and finds it. and a browser sandbox where AI controls a real browser like filling forms, clicking buttons, handles logins. 4. the agent endpoint is wild. you can say "find all of YC's winter 24 dev tool companies and their founders and emails" and get back structured data. or "compare pricing tiers across stripe, square, and paypal" and get a side-by-side table. 5. the browser sandbox lets your AI stay logged in across sessions, navigate pagination, watch live as it browses. this is computer use without building the infrastructure yourself. 6. think of it in layers. every builder needs: an agent harness (claude code, cursor, codex), a search layer (perplexity, exa), a web data layer (firecrawl), an ops brain (obsidian, notion), and an outbound stack. the web data layer is the one most people are sleeping on. 7. this is the AWS moment for web data. in 2006 building a web app meant buying servers and managing racks. AWS said one API call, use our servers. some of the biggest companies of the last decade were built on that. firecrawl is doing the same thing for web data in 2026. 8. the framework i'd use for coming up with startup ideas building with clean data: take a massive horizontal platform. rebuild it for one niche using firecrawl. the vertical version always wins because people want specific, not generic. price for outcome. 9. a year ago firecrawl posted a job listing that said "please only apply if you're an AI agent." content creator agents. customer support agents. junior dev agents. it looked weird. it was a signal for where this is all going. the people who understand how to get clean web data, wrap it around an LLM, and package it as a product are the the ones with a 12-month head start. i use Firecrawl with Idea Browser . once you see what's possible with structured web data, you can't unsee it. episode is live on The Startup Ideas Podcast (SIP) 🧃 (full breakdown there) i tried to explain this as clear as possible for even the non technical. send it to a builder friend. watch

GREG ISENBERG

135,254 görüntüleme • 5 ay önce

🚨 THIS IS ACTUALLY INSANE Your AI agent can have access to the web. But if it can't reliably read what’s actually on the page, that access is almost useless. We looked at Firecrawl as the web layer for AI agents and the numbers are hard to ignore. The setup is simple: Give it a URL, search query, or website. Firecrawl handles the ugly part — crawling, scraping, rendering, extracting, and turning web content into something an AI model can actually use. The headline numbers: → 173,000+ GitHub stars → Search, scrape and interact with the web at scale → Supports web pages, PDFs, DOCX and other content → Structured data extraction for AI workflows → MCP support for connecting it directly to AI agents The workflow looks like this: Search → Scrape → Crawl → Extract → Feed the agent Three things stand out: 1. Scraping becomes an infrastructure layer Instead of maintaining your own pile of HTTP clients, parsers, browser automation and retry logic, you can treat web access as an API. 2. Agents get more than raw HTML The goal isn't just downloading a webpage. It's turning messy web content into clean context that an LLM can reason over. 3. The same layer works across different agent workflows Research agents. RAG pipelines. AI search. Competitive intelligence. Web-data extraction. The interesting shift: AI agents don't just need better models. They need better access to the information those models are supposed to reason about. Firecrawl is building that layer. Save this repo.
0:28

🚨 THIS IS ACTUALLY INSANE Your AI agent can have access to the web. But if it can't reliably read what’s actually on the page, that access is almost useless. We looked at Firecrawl as the web layer for AI agents and the numbers are hard to ignore. The setup is simple: Give it a URL, search query, or website. Firecrawl handles the ugly part — crawling, scraping, rendering, extracting, and turning web content into something an AI model can actually use. The headline numbers: → 173,000+ GitHub stars → Search, scrape and interact with the web at scale → Supports web pages, PDFs, DOCX and other content → Structured data extraction for AI workflows → MCP support for connecting it directly to AI agents The workflow looks like this: Search → Scrape → Crawl → Extract → Feed the agent Three things stand out: 1. Scraping becomes an infrastructure layer Instead of maintaining your own pile of HTTP clients, parsers, browser automation and retry logic, you can treat web access as an API. 2. Agents get more than raw HTML The goal isn't just downloading a webpage. It's turning messy web content into clean context that an LLM can reason over. 3. The same layer works across different agent workflows Research agents. RAG pipelines. AI search. Competitive intelligence. Web-data extraction. The interesting shift: AI agents don't just need better models. They need better access to the information those models are supposed to reason about. Firecrawl is building that layer. Save this repo.

Vikas gupta

18,053 görüntüleme • 9 gün önce

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.
3:38

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,647 görüntüleme • 1 yıl önce

For 20+ years, we've stayed ahead of every major shift in technology. Today we take the next one: we're introducing the world's first AI-native tech services model. Most of the industry is adding AI to the way it already works. Like bolting a copilot onto old processes and calling it transformation because it's faster than before. That's not what enterprises actually need. works differently. It provides instant access to AI Pods (service units run by AI agents and supervised by Globant experts) that deliver tech services at machine speed, but with the rigor, the governance, and the quality that enterprise-grade work demands. It is a smarter model, running the right AI through parallel agents, loops, workflows, and deterministic processes. With organizations access AI services with transparent, output or consumption-linked pricing, not per hour or per seat, and they own everything they produce. We are bringing the speed AI promises, with the rigor and quality any business needs. Join the waitlist at
0:48

For 20+ years, we've stayed ahead of every major shift in technology. Today we take the next one: we're introducing the world's first AI-native tech services model. Most of the industry is adding AI to the way it already works. Like bolting a copilot onto old processes and calling it transformation because it's faster than before. That's not what enterprises actually need. works differently. It provides instant access to AI Pods (service units run by AI agents and supervised by Globant experts) that deliver tech services at machine speed, but with the rigor, the governance, and the quality that enterprise-grade work demands. It is a smarter model, running the right AI through parallel agents, loops, workflows, and deterministic processes. With organizations access AI services with transparent, output or consumption-linked pricing, not per hour or per seat, and they own everything they produce. We are bringing the speed AI promises, with the rigor and quality any business needs. Join the waitlist at

Martin Migoya

393,456 görüntüleme • 1 ay önce

Today, Box is announcing major new AI agent capabilities to let customers tap into the full value of their unstructured data. First, we’re announcing all new updates to the Box AI Studio to make it even easier to build AI agents that tap into your enterprise content for any job function, business process, or industry specific use case. We are also expanding our set of foundational agents that customers will be able to use to work with their enterprise content, including new features like search and research on unstructured data. Next, we’re announcing Box Extract to enable customers to use AI agents seamlessly for complex data extraction from any type of document or content. This makes it easier than ever to pull out data from contracts, invoices, research data, marketing assets, medical charts, and more. Finally, we’re introducing Box Automate, a new workflow automation solution within Box that lets you deploy AI agents across enterprise content-centric workflows. With Box Automate, you can design your business process in a simple drag and drop builder and then drop in AI agents at any step in the process. This ensures agents execute tasks at the right steps in a workflow every time. Best of all, our AI agents and workflow tools are designed to work across any system our customers work within, whether it’s leveraging pre-built integrations, Box APIs, or the new Box MCP Server. Ultimately, all of these capabilities come together to transform how companies can work with their enterprise content. Software has historically only been good at automating work that deals with structured data, which is why ERP, CRM, and HR systems have been mainstays of enterprise software for so long. The data in these systems fits neatly into a database, and the workflows are very ripe for automation. But it turns out most of the work in the world deals with unstructured data. It’s ideating through research documents, working with a client on contracts, reviewing details for a new product launch, looking at a patient’s healthcare record to make a diagnosis, working through due diligence documents for an M&A deal, and so on. For the first time ever, we can begin to bring all new insights and automation to this work with AI agents. At Box, we’re incredibly excited to be on this journey to help customers transform how they work with their most important data.
1:21

Today, Box is announcing major new AI agent capabilities to let customers tap into the full value of their unstructured data. First, we’re announcing all new updates to the Box AI Studio to make it even easier to build AI agents that tap into your enterprise content for any job function, business process, or industry specific use case. We are also expanding our set of foundational agents that customers will be able to use to work with their enterprise content, including new features like search and research on unstructured data. Next, we’re announcing Box Extract to enable customers to use AI agents seamlessly for complex data extraction from any type of document or content. This makes it easier than ever to pull out data from contracts, invoices, research data, marketing assets, medical charts, and more. Finally, we’re introducing Box Automate, a new workflow automation solution within Box that lets you deploy AI agents across enterprise content-centric workflows. With Box Automate, you can design your business process in a simple drag and drop builder and then drop in AI agents at any step in the process. This ensures agents execute tasks at the right steps in a workflow every time. Best of all, our AI agents and workflow tools are designed to work across any system our customers work within, whether it’s leveraging pre-built integrations, Box APIs, or the new Box MCP Server. Ultimately, all of these capabilities come together to transform how companies can work with their enterprise content. Software has historically only been good at automating work that deals with structured data, which is why ERP, CRM, and HR systems have been mainstays of enterprise software for so long. The data in these systems fits neatly into a database, and the workflows are very ripe for automation. But it turns out most of the work in the world deals with unstructured data. It’s ideating through research documents, working with a client on contracts, reviewing details for a new product launch, looking at a patient’s healthcare record to make a diagnosis, working through due diligence documents for an M&A deal, and so on. For the first time ever, we can begin to bring all new insights and automation to this work with AI agents. At Box, we’re incredibly excited to be on this journey to help customers transform how they work with their most important data.

Aaron Levie

91,863 görüntüleme • 1 yıl önce

Here is why Nimble has 1.1M Claude plugin installs… I tested the Nimble Studio for a few minutes and immediately understood the appeal. Instead of manually scraping sites or fighting APIs, Nimble lets AI agents pull structured live data from platforms like TikTok, YouTube, Instagram, Reddit, and more. I tried pulling trending AI tool content and it turned messy social pages into a clean dataset almost instantly, complete with engagement metrics, creators, hashtags, and trends. The interesting part is how natural it feels. You’re basically giving AI agents the ability to interact with live web data in a usable format instead of static search results. That’s why the 1.1M installs matter. It solves a real problem for developers, researchers, marketers, and teams building AI workflows around real-time internet data.
0:27

Here is why Nimble has 1.1M Claude plugin installs… I tested the Nimble Studio for a few minutes and immediately understood the appeal. Instead of manually scraping sites or fighting APIs, Nimble lets AI agents pull structured live data from platforms like TikTok, YouTube, Instagram, Reddit, and more. I tried pulling trending AI tool content and it turned messy social pages into a clean dataset almost instantly, complete with engagement metrics, creators, hashtags, and trends. The interesting part is how natural it feels. You’re basically giving AI agents the ability to interact with live web data in a usable format instead of static search results. That’s why the 1.1M installs matter. It solves a real problem for developers, researchers, marketers, and teams building AI workflows around real-time internet data.

Kaitee

28,590 görüntüleme • 3 ay önce

AI AGENTS 101 (58 minute free masterclass) send this to anyone who wants to understand ai agents, claude skills, md files, how to get the most out of AI etc in plain english: 1. chat vs agents - chat models answer questions in a back and forth while agents take a goal, figure out the steps, and deliver a result 2. agents don’t stop after one response. they keep running until the task is actually finishedno babysitting required 3. everything runs on a loop. they gather context, decide what to do, take an action, then repeat until done 4. the loop is the system. they look at files, tools, and the internet. decide the next step. execute and then feed that back into the next step. over and over until completion 5. the model is just one piece. gpt, claude, gemini are the reasoning layer. the key is model + loop + tools + context 6. mcp is how agents use tools. it connects things like browser, code, apis, and your internal software. once connected, the agent decides when to use them to get the job done 7. context beats prompt all day. you don't need to write perfect prompts. load your agent with context about your business, style, and goals and then simple instructions work 8. claude.md or agents.md is the onboarding doc it tells the agent who it is, how to behave, what it knows, and what tools it can use. this gets loaded every time before it starts 9. memory.md is how it improves. agents don’t remember by default. this file stores preferences, corrections, and patterns you tell the agent to update it, and it gets better over time 10. skills + harnesses make it usable. skills are reusable tasks like writing, research, analysis the harness is the environment like claude code or openclaw that runs everything. basiclaly, different interfaces, same system underneath this episode with remy on The Startup Ideas Podcast (SIP) 🧃 was one of the clearest ways of understanding a lot of the core concepts of ai agents could be the best beginners course for ai agents 58 mins. all free. no advertisers. i just want to see you build cool stuff. im rooting for you. send to a friend watch
58:55

AI AGENTS 101 (58 minute free masterclass) send this to anyone who wants to understand ai agents, claude skills, md files, how to get the most out of AI etc in plain english: 1. chat vs agents - chat models answer questions in a back and forth while agents take a goal, figure out the steps, and deliver a result 2. agents don’t stop after one response. they keep running until the task is actually finishedno babysitting required 3. everything runs on a loop. they gather context, decide what to do, take an action, then repeat until done 4. the loop is the system. they look at files, tools, and the internet. decide the next step. execute and then feed that back into the next step. over and over until completion 5. the model is just one piece. gpt, claude, gemini are the reasoning layer. the key is model + loop + tools + context 6. mcp is how agents use tools. it connects things like browser, code, apis, and your internal software. once connected, the agent decides when to use them to get the job done 7. context beats prompt all day. you don't need to write perfect prompts. load your agent with context about your business, style, and goals and then simple instructions work 8. claude.md or agents.md is the onboarding doc it tells the agent who it is, how to behave, what it knows, and what tools it can use. this gets loaded every time before it starts 9. memory.md is how it improves. agents don’t remember by default. this file stores preferences, corrections, and patterns you tell the agent to update it, and it gets better over time 10. skills + harnesses make it usable. skills are reusable tasks like writing, research, analysis the harness is the environment like claude code or openclaw that runs everything. basiclaly, different interfaces, same system underneath this episode with remy on The Startup Ideas Podcast (SIP) 🧃 was one of the clearest ways of understanding a lot of the core concepts of ai agents could be the best beginners course for ai agents 58 mins. all free. no advertisers. i just want to see you build cool stuff. im rooting for you. send to a friend watch

GREG ISENBERG

377,138 görüntüleme • 6 ay önce

A finance professor manages $200M with AI agents, and he told everyone why: "Large language models are at the level of a fourth-year PhD student in every field" Alejandro Lopez-Lira's AI fund, Autopilot, returned 56% last year. The S&P did 16%. There are 52,000 people with money in it, and most of them just watch the machine work. What he automated is the same six-step loop every fund on earth runs: find an idea, code it, backtest it, deploy it, read the autopsy, learn from it. A quant at Two Sigma runs that loop once a month, and the salary time alone costs around $50,000 per hypothesis. All steps from this loop now fit in AI trading text box. Plain English in, executable strategy out, five-year backtest in 12 seconds, live on a broker 90 seconds after you typed the sentence. He runs $200M with AI. You can run same AI fund in two clicks, free to try: Step 6 on this loop is where everyone is stuck. Your agent has no memory. Every strategy it kills goes into a log nobody reads, and the next one starts from zero. Nobody keeps negative results. Not Citadel, not Man Group, not a single repo on GitHub. Fix that and the agent remembers every hypothesis it killed and the regime it died in. It stops burning cycles on your old mistakes. Jane Street pays 3,500 people to run this cycle and made $39.6 billion doing it. Five sixths of it is now free. Bookmark & read full map of this loop in the article below. Most people still think AI trading is out of reach for them - it isn't. Don't want to spend a dollar for testing this? Kalshi just opened a perps exchange and gives US users $25 free to start ->
0:48

A finance professor manages $200M with AI agents, and he told everyone why: "Large language models are at the level of a fourth-year PhD student in every field" Alejandro Lopez-Lira's AI fund, Autopilot, returned 56% last year. The S&P did 16%. There are 52,000 people with money in it, and most of them just watch the machine work. What he automated is the same six-step loop every fund on earth runs: find an idea, code it, backtest it, deploy it, read the autopsy, learn from it. A quant at Two Sigma runs that loop once a month, and the salary time alone costs around $50,000 per hypothesis. All steps from this loop now fit in AI trading text box. Plain English in, executable strategy out, five-year backtest in 12 seconds, live on a broker 90 seconds after you typed the sentence. He runs $200M with AI. You can run same AI fund in two clicks, free to try: Step 6 on this loop is where everyone is stuck. Your agent has no memory. Every strategy it kills goes into a log nobody reads, and the next one starts from zero. Nobody keeps negative results. Not Citadel, not Man Group, not a single repo on GitHub. Fix that and the agent remembers every hypothesis it killed and the regime it died in. It stops burning cycles on your old mistakes. Jane Street pays 3,500 people to run this cycle and made $39.6 billion doing it. Five sixths of it is now free. Bookmark & read full map of this loop in the article below. Most people still think AI trading is out of reach for them - it isn't. Don't want to spend a dollar for testing this? Kalshi just opened a perps exchange and gives US users $25 free to start ->

cvxv666

82,936 görüntüleme • 1 ay önce

Today we're launching Amplitude MCP MCP was made for data analytics. Ask a vague question and have an AI model iteratively query Amplitude to find you insights. Amplitude MCP exposes all of Amplitude's functionality so an agent can interact with it directly. It allows you to use Amplitude without having to know anything about Amplitude's user interface or your data taxonomy. It uses the intelligence of off the shelf AI agents, including Claude, Gemini, and Cursor, to query Amplitude data you already have to find answers. It leverages all of your existing Amplitude data and how it's used to navigate through large complex behavioral datasets. You can have conversations about your product data directly inside any AI model with MCP. It can create Amplitude dashboards and notebooks with what it finds and even make recommendations. This is the best MCP use case I've ever seen. Watching an AI agent think, reason, query Amplitude, and then repeat that process iteratively is magical. See it in action:
3:08

Today we're launching Amplitude MCP MCP was made for data analytics. Ask a vague question and have an AI model iteratively query Amplitude to find you insights. Amplitude MCP exposes all of Amplitude's functionality so an agent can interact with it directly. It allows you to use Amplitude without having to know anything about Amplitude's user interface or your data taxonomy. It uses the intelligence of off the shelf AI agents, including Claude, Gemini, and Cursor, to query Amplitude data you already have to find answers. It leverages all of your existing Amplitude data and how it's used to navigate through large complex behavioral datasets. You can have conversations about your product data directly inside any AI model with MCP. It can create Amplitude dashboards and notebooks with what it finds and even make recommendations. This is the best MCP use case I've ever seen. Watching an AI agent think, reason, query Amplitude, and then repeat that process iteratively is magical. See it in action:

Spenser Skates

32,420 görüntüleme • 10 ay önce

Ex-Google engineer built a graph-based workflow that made Claude Code do nearly 10 days of work in about an hour. Here's the exact setup he uses. step 1. create a separate Git worktree for every task. run: git worktree add ../task-1 -b task-1 open a new terminal, cd into it, and launch Claude Code. repeat this for every agent. each one gets its own branch, so nothing conflicts. step 2. give every Claude agent a different task. same repository. different branches. they all work in parallel. step 3. once they're done, review the pull requests. keep the good ones. merge what works. step 4. add a review agent. paste each PR into Claude and ask: "does this implementation match the original specification" every agent now has another agent reviewing its work before it gets merged. step 5. scale it up. 48GB of RAM can comfortably run around 20 Claude Code agents. 128GB can handle roughly 50. most engineers run Claude Code once and wait. he runs dozens of Claude Code agents in parallel, then merges the best results. this 60-minute lecture is one of the best free resources on graph engineering and multi-agent workflows. bookmark it and watch it below.
55:30

Ex-Google engineer built a graph-based workflow that made Claude Code do nearly 10 days of work in about an hour. Here's the exact setup he uses. step 1. create a separate Git worktree for every task. run: git worktree add ../task-1 -b task-1 open a new terminal, cd into it, and launch Claude Code. repeat this for every agent. each one gets its own branch, so nothing conflicts. step 2. give every Claude agent a different task. same repository. different branches. they all work in parallel. step 3. once they're done, review the pull requests. keep the good ones. merge what works. step 4. add a review agent. paste each PR into Claude and ask: "does this implementation match the original specification" every agent now has another agent reviewing its work before it gets merged. step 5. scale it up. 48GB of RAM can comfortably run around 20 Claude Code agents. 128GB can handle roughly 50. most engineers run Claude Code once and wait. he runs dozens of Claude Code agents in parallel, then merges the best results. this 60-minute lecture is one of the best free resources on graph engineering and multi-agent workflows. bookmark it and watch it below.

MIKE

32,199 görüntüleme • 1 ay önce

New Short Course: Building AI Browser Agents! Learn how to build AI agents that interact and take actions on websites in this course, created in partnership with and taught by and @namangarg0, Co-founders of AGI Inc. AI browser agents can log into websites, fill out forms, click through web pages, or even place orders online for you. They use both visual information, like screenshots, and structural data, like the HTML or Document Object Model (DOM) of a web page, to reason and take action. With the complexity of webpages and multiple possible actions at each step, it can be challenging for an AI browser agent to complete an assigned task. Because these agents run long action sequences, a single error—like clicking the wrong button or misreading a field—can lead to unexpected outcomes or errors that compound over time. In this course, you'll understand how autonomous web agents work, their current limitations, and how AgentQ enables them to improve through self-correction. In detail, you'll: - Learn what web agents are, how they automate tasks online, their architecture, key components, limitations, and an overview of their decision-making strategies. - Build a web agent that can scrape website and return course recommendations in a structured output format. - Build an autonomous web agent that can execute multiple tasks, such as finding and summarizing webpages, filling out a form, and signing up for a newsletter. - Explore AgentQ, a framework that enables agents to self-correct by combining Monte Carlo Tree Search (MCTS), a self-critique mechanism for continuous improvement, and Direct Preference Optimization (DPO). - Deep dive into MCTS, learn how it finds an effective path, illustrated by an example of Gridworld animation, and use AgentQ to complete web tasks. - Understand AI agents' current state and future directions—including key factors shaping their evolution, such as hardware, algorithm innovation, and data availability. By the end of this course, you will have hands-on experience building browser agents and a deeper understanding of how to make them more robust and reliable. Please sign up here:
2:06

New Short Course: Building AI Browser Agents! Learn how to build AI agents that interact and take actions on websites in this course, created in partnership with and taught by and @namangarg0, Co-founders of AGI Inc. AI browser agents can log into websites, fill out forms, click through web pages, or even place orders online for you. They use both visual information, like screenshots, and structural data, like the HTML or Document Object Model (DOM) of a web page, to reason and take action. With the complexity of webpages and multiple possible actions at each step, it can be challenging for an AI browser agent to complete an assigned task. Because these agents run long action sequences, a single error—like clicking the wrong button or misreading a field—can lead to unexpected outcomes or errors that compound over time. In this course, you'll understand how autonomous web agents work, their current limitations, and how AgentQ enables them to improve through self-correction. In detail, you'll: - Learn what web agents are, how they automate tasks online, their architecture, key components, limitations, and an overview of their decision-making strategies. - Build a web agent that can scrape website and return course recommendations in a structured output format. - Build an autonomous web agent that can execute multiple tasks, such as finding and summarizing webpages, filling out a form, and signing up for a newsletter. - Explore AgentQ, a framework that enables agents to self-correct by combining Monte Carlo Tree Search (MCTS), a self-critique mechanism for continuous improvement, and Direct Preference Optimization (DPO). - Deep dive into MCTS, learn how it finds an effective path, illustrated by an example of Gridworld animation, and use AgentQ to complete web tasks. - Understand AI agents' current state and future directions—including key factors shaping their evolution, such as hardware, algorithm innovation, and data availability. By the end of this course, you will have hands-on experience building browser agents and a deeper understanding of how to make them more robust and reliable. Please sign up here:

Andrew Ng

186,182 görüntüleme • 1 yıl önce

9 out of 10 multi-agent projects never leave demo mode Not because the model is bad. Because the structure is missing. Most people who try to build [ a team of AI agents ] end up with one agent talking to itself in five tabs. The agents don't share context → Don't divide work → Don't know what the others are doing. > stage 1: if your agent doesn't have a real loop, observe, act, iterate, you have a long prompt, not an agent > stage 2: subagents need isolated context, the orchestrator never reads their raw transcript, only the summary > stage 3: the orchestrator plans and delegates, the moment it executes, it drowns in details that belong inside subagents > stage 4: without a shared task list it's not a team, it's five agents duplicating each other's work in parallel > stage 5: a permissions file is what lets you sleep, the model cannot bypass it because the rule lives outside the model a team of AI agents is not more model, it is more structure the most ignored stage in every demo that died: - durability... when a 50-step task crashes at step 47 and starts from zero, that's not a model failure. that's a missing write-to-disk call
1:07

9 out of 10 multi-agent projects never leave demo mode Not because the model is bad. Because the structure is missing. Most people who try to build [ a team of AI agents ] end up with one agent talking to itself in five tabs. The agents don't share context → Don't divide work → Don't know what the others are doing. > stage 1: if your agent doesn't have a real loop, observe, act, iterate, you have a long prompt, not an agent > stage 2: subagents need isolated context, the orchestrator never reads their raw transcript, only the summary > stage 3: the orchestrator plans and delegates, the moment it executes, it drowns in details that belong inside subagents > stage 4: without a shared task list it's not a team, it's five agents duplicating each other's work in parallel > stage 5: a permissions file is what lets you sleep, the model cannot bypass it because the rule lives outside the model a team of AI agents is not more model, it is more structure the most ignored stage in every demo that died: - durability... when a 50-step task crashes at step 47 and starts from zero, that's not a model failure. that's a missing write-to-disk call

Shadow Nick

14,714 görüntüleme • 3 ay önce

When data agents fail, they often fail silently - giving confident-sounding answers that are wrong, and it can be hard to figure out what caused the failure. "Building and Evaluating Data Agents" is a new short course created with Snowflake and taught by Anupam Datta and Josh Reini that teaches you to build data agents with comprehensive evaluation built in. Skills you'll gain: - Build reliable LLM data agents using the Goal-Plan-Action framework and runtime evaluations that catch failures mid-execution - Use OpenTelemetry tracing and evaluation infrastructure to diagnose exactly where agents fail and systematically improve performance - Orchestrate multi-step workflows across web search, SQL, and document retrieval in LangGraph-based agents The result: visibility into every step of your agent's reasoning, so if something breaks, you have a systematic approach to fix it. Sign up to get started:
3:20

When data agents fail, they often fail silently - giving confident-sounding answers that are wrong, and it can be hard to figure out what caused the failure. "Building and Evaluating Data Agents" is a new short course created with Snowflake and taught by Anupam Datta and Josh Reini that teaches you to build data agents with comprehensive evaluation built in. Skills you'll gain: - Build reliable LLM data agents using the Goal-Plan-Action framework and runtime evaluations that catch failures mid-execution - Use OpenTelemetry tracing and evaluation infrastructure to diagnose exactly where agents fail and systematically improve performance - Orchestrate multi-step workflows across web search, SQL, and document retrieval in LangGraph-based agents The result: visibility into every step of your agent's reasoning, so if something breaks, you have a systematic approach to fix it. Sign up to get started:

Andrew Ng

102,364 görüntüleme • 11 ay önce

The biggest marketplace on Earth won't be the assets humans own. It'll be the data AI needs. Everything that can be digitised is getting pulled in to train the next models. Every scientific dataset, every piece of research sitting in a university, every sensor reading off every John Deere tractor in a field. All of it feeds the machine, and almost none of it is visible to us. What comes out is an agentic economy running at machine speed. You plug your data into a vault, and agents monetise it on your behalf, trading with other agents in real time, in a marketplace we never see. The company sitting on proprietary data becomes part of it without even knowing. This is what the Economic Singularity actually looks like from the inside. The real economy stops being the one we can see and price, and moves somewhere we can't follow. You own a piece of it, or you get priced out of it. Jordi Visser.
1:27

The biggest marketplace on Earth won't be the assets humans own. It'll be the data AI needs. Everything that can be digitised is getting pulled in to train the next models. Every scientific dataset, every piece of research sitting in a university, every sensor reading off every John Deere tractor in a field. All of it feeds the machine, and almost none of it is visible to us. What comes out is an agentic economy running at machine speed. You plug your data into a vault, and agents monetise it on your behalf, trading with other agents in real time, in a marketplace we never see. The company sitting on proprietary data becomes part of it without even knowing. This is what the Economic Singularity actually looks like from the inside. The real economy stops being the one we can see and price, and moves somewhere we can't follow. You own a piece of it, or you get priced out of it. Jordi Visser.

Raoul Pal

79,047 görüntüleme • 1 ay önce

Big moment for Postgres! AI agents broke the idea of what a database is supposed to do. Traditional databases were built for humans, and Agents broke that model. - They branch endlessly. - They run ten experiments at once. - They need isolation, context, memory, structured reasoning, and safe sandboxes. Letting agents touch production systems is terrifying because the old model of Postgres was never built for this kind of behavior. Agentic Postgres is an agent-ready version of Postgres by TimescaleDB (by Tiger Data) that solves this. I think it is one of the biggest upgrades to the Agent stack this year and Tiger Data is working with me on this post to share what they did. Some key features: > It instantly creates branches of an entire database, which is perfect for parallel agent evals, safe experiments, migrations, or isolated testing. Forks take seconds and cost almost nothing. > It comes with a built-in MCP server, which agents can use to get schema guidance, best practices, and safe, structured access to Postgres. This is also helpful to run migrations with a real understanding. > It comes with actual hybrid search (vector search and BM25), so Agents can retrieve data directly inside the database. > The database is Memory native. This gives a persistent context for Agents to evolve. This is one of the first times I have seen Postgres feel ready for the AI native era.
0:26

Big moment for Postgres! AI agents broke the idea of what a database is supposed to do. Traditional databases were built for humans, and Agents broke that model. - They branch endlessly. - They run ten experiments at once. - They need isolation, context, memory, structured reasoning, and safe sandboxes. Letting agents touch production systems is terrifying because the old model of Postgres was never built for this kind of behavior. Agentic Postgres is an agent-ready version of Postgres by TimescaleDB (by Tiger Data) that solves this. I think it is one of the biggest upgrades to the Agent stack this year and Tiger Data is working with me on this post to share what they did. Some key features: > It instantly creates branches of an entire database, which is perfect for parallel agent evals, safe experiments, migrations, or isolated testing. Forks take seconds and cost almost nothing. > It comes with a built-in MCP server, which agents can use to get schema guidance, best practices, and safe, structured access to Postgres. This is also helpful to run migrations with a real understanding. > It comes with actual hybrid search (vector search and BM25), so Agents can retrieve data directly inside the database. > The database is Memory native. This gives a persistent context for Agents to evolve. This is one of the first times I have seen Postgres feel ready for the AI native era.

Avi Chawla

94,290 görüntüleme • 9 ay önce

Right now the main paradigm that we think of agents in is chatting back and forth, but the biggest use of tokens will come from agents that are just always on running in the background doing work for us, or ones triggered from a workflow. Agents will be working 24/7 in our workflows processing data, reviewing and generating documents, moving data between systems, writing code, accelerating decision making steps, and more. In Claude's new Managed Agents feature, in a couple minutes you can wire up an agent that can read contracts when they come into Box to review them, and then assign a task in Linear with the critical information from the contract. But this could have been any workflow, like reviewing documents for client onboarding, invoice processing, M&A due-diligence, data extraction pipelines, and millions of other use-cases. And integrating data across any system. This is only possible when you can have long-running agents that can complete real work in the background, accurately. Agents have the ability to execute code safely, leverage tools, access a compute sandbox, and connect across systems is clearly the architecture of the future. The industry is now making it easier and easier for enterprises to build and deploy these agents.
0:43

Right now the main paradigm that we think of agents in is chatting back and forth, but the biggest use of tokens will come from agents that are just always on running in the background doing work for us, or ones triggered from a workflow. Agents will be working 24/7 in our workflows processing data, reviewing and generating documents, moving data between systems, writing code, accelerating decision making steps, and more. In Claude's new Managed Agents feature, in a couple minutes you can wire up an agent that can read contracts when they come into Box to review them, and then assign a task in Linear with the critical information from the contract. But this could have been any workflow, like reviewing documents for client onboarding, invoice processing, M&A due-diligence, data extraction pipelines, and millions of other use-cases. And integrating data across any system. This is only possible when you can have long-running agents that can complete real work in the background, accurately. Agents have the ability to execute code safely, leverage tools, access a compute sandbox, and connect across systems is clearly the architecture of the future. The industry is now making it easier and easier for enterprises to build and deploy these agents.

Aaron Levie

17,543 görüntüleme • 5 ay önce

Reviewing AI-generated code is the new bottleneck. Writing code was slow before. Now, in a few minutes, you can generate virtually unlimited lines of code using AI. But developers are now spending 70% of their time checking that code. That's the new bottleneck. I've been using Cline, and they have a feature that actually helps with this: You can click a button and have Cline generate an inline explanation for every single line of AI-generated code. Take a look at the attached video. What it does: 1. You can read the code and the explanation together 2. You don't lose context while reviewing code 3. You understand the "why" behind each change And here is the best part: It works on any git diff. You can use it to review PRs, understand commits from other people, or catch up on a codebase you haven't touched in a while.
3:25

Reviewing AI-generated code is the new bottleneck. Writing code was slow before. Now, in a few minutes, you can generate virtually unlimited lines of code using AI. But developers are now spending 70% of their time checking that code. That's the new bottleneck. I've been using Cline, and they have a feature that actually helps with this: You can click a button and have Cline generate an inline explanation for every single line of AI-generated code. Take a look at the attached video. What it does: 1. You can read the code and the explanation together 2. You don't lose context while reviewing code 3. You understand the "why" behind each change And here is the best part: It works on any git diff. You can use it to review PRs, understand commits from other people, or catch up on a codebase you haven't touched in a while.

Santiago

64,438 görüntüleme • 9 ay önce

Okay, This is a big Hermes Desktop update 👀 Hermes can now actually use the Preview pane. Not just open a page. Not just read a page. Use it. Click. Type. Scroll. Navigate. Annotate. Inside the same visible browser pane you are watching. That is a big deal. It means Hermes Desktop is starting to feel a lot less like a chat window attached to tools and a lot more like an agent that can work through web tasks in front of you. Think about the use cases: → Open documentation and show you exactly where a setting lives → Walk through a setup flow and point out what to click → Search a site, open the right result, and keep moving → Work through a dashboard while you supervise → Annotate important controls on a crowded page → Reproduce a web issue step by step → Fill out multi-step web workflows with you watching → Find the right tutorial or guide and take you straight to it That changes the feel of Hermes Desktop. Because now Hermes is not just telling you what to do. It can show you, point to it, and act on it in the same workspace. This one opens up a lot!!!
0:26

Okay, This is a big Hermes Desktop update 👀 Hermes can now actually use the Preview pane. Not just open a page. Not just read a page. Use it. Click. Type. Scroll. Navigate. Annotate. Inside the same visible browser pane you are watching. That is a big deal. It means Hermes Desktop is starting to feel a lot less like a chat window attached to tools and a lot more like an agent that can work through web tasks in front of you. Think about the use cases: → Open documentation and show you exactly where a setting lives → Walk through a setup flow and point out what to click → Search a site, open the right result, and keep moving → Work through a dashboard while you supervise → Annotate important controls on a crowded page → Reproduce a web issue step by step → Fill out multi-step web workflows with you watching → Find the right tutorial or guide and take you straight to it That changes the feel of Hermes Desktop. Because now Hermes is not just telling you what to do. It can show you, point to it, and act on it in the same workspace. This one opens up a lot!!!

Hermes Release Watch

56,232 görüntüleme • 22 gün önce