Loading video...

Video Failed to Load

Go Home

Super powerful agents can access all kinds of live information = Never manually research again Quick agent use-case (ANYONE can do this): 💡 Instant market research User Asks ✅ Are whales buying BTC? ✅ What is the exchange netflow of BTC? ✅ Are stables flowing in or out of...

35,957 views • 4 months ago •via X (Twitter)

0 Comments

No comments available

Comments from the original post will appear here

Related Videos

Strategy sold 3,588 BTC last week. That's 112x more than the 32 BTC they sold a few weeks ago (which freaked out the market). Here's what's happening and why they are doing this... 1. Last week = Strategy sold Last week, Strategy sold 3,588 BTC and used all of the proceeds ($216m) to fund dividend payments on their suite of preferred equities. Q2 dividend payments for STRF, STRK, STRD, and STRE... and June dividends for STRC. Notably, BTC price opened last week at $59.5k. Strategy sold 3,588 BTC over the course of the week, yet BTC price went up to $63.5k. 2. The bigger picture = Strategy is NET buying Strategy bought 85,296 BTC in Q2. Their combined selling for Q2 was 3,620 BTC (32 + 3,588). In other words, they bought 22.5x more BTC in Q2 than they sold. (For 2026 YTD numbers, Strategy has bought ~175k BTC and sold 3.6k BTC. That's a 48x ratio.) 3. The message in advance Weeks ago, Saylor explained what they are doing, in an interview with Michaël van de Poppe (see clip) "On occasion, we'll buy 20 Bitcoin & we'll sell 1 Bitcoin... Then the credit investors will give us enough to buy 20 more Bitcoin." Saylor further explained the strategic rationale of selling Bitcoin... "Our credit investors expect that we're going to support the credit dividend and pay it (and our asset is BTC)... 'will you sell some Bitcoin to pay us the money?' They expect me to say yes, because if I'm not going to pay the dividend, they're not going to buy the credit & the credit agency won't rate the credit." 4. What Strategy is doing Strategy is showing the market that they can and will sell BTC. They are doing this to gain access to more credit market capital... so that they can buy much more BTC. Saylor has recently asserted that it's important to "buy more Bitcoin than you sell." This is that in action. In Q2, they bought 85k BTC. They then used 3.5k BTC to fund the dividends on the Digital Credit that enabled them to buy 85k BTC. They bought 22.5 and sold 1. 5. What to expect next Saylor said they will "inoculate the market" by selling a little BTC. This is the second dose of inoculation. They will keep doing it until the market expects it and no longer reacts to it. They are not dumping their BTC treasury strategy for dollars. That is the click-bait headline for the uninformed. What they are telling you is that they plan to sell 1 BTC so they can buy 20 BTC. Over and over.

Jesse Myers

169,559 views • 1 month ago

I’ve been watching x402 since Coinbase 🛡️ launched it in May 2025. I did a quick research pass. Here’s the snapshot ↓ Early integrations: • CoinGecko: x402 pay-per-use access for agents (shared by Coinbase Developer Platform🛡️). • Vercel: x402 AI starter template (x402 + modern AI stack demo). • Firecrawl: x402-powered search endpoint (pay per request). • Concordium: x402 + native age verification for agent payments. • Multiversᕽ: “agentic payments” built around x402 support. • AltLayer: building an “x402 Suite” for value exchange between agents. • Solana claims x402 has processed 35M+ transactions and $10M+ volume since launch. TL;DR x402 turns HTTP 402 “Payment Required” into a payment flow. A server returns a price for a request. The client pays in stables like USDC. Then the server returns the result. → Coinbase launched x402 via Coinbase Developer Platform (May 6, 2025). → Coinbase + Cloudflare announced the x402 Foundation (Sep 23, 2025). → Cloudflare added x402 support into its Agents SDK + MCP servers. Why? - AI agents need a clean way to pay for tools. - Data, compute, APIs, services. - No accounts, cards, or subscription screens. x402 is trying to make pay-per-request feel normal. Use cases that already make sense → Paid APIs Pay per call instead of subscriptions. → AI tool calls Pay per query, per inference, per task. → Agent-to-agent payments Software paying software automatically. → Micropaywalls Pay for one endpoint, one action, one piece of content. If this takes off, stablecoins stop being a story. They become how apps and AI agents pay for things online.

Stacy Muur

12,199 views • 5 months ago

🚨 memU bot is live. A better alternative to OpenClaw🦞 (formerly Moltbot / Clawdbot) 👉Get instant access to the memU bot: 🕒 A 24/7 proactive assistant memU bot runs continuously on your machine and works as a proactive assistant. It takes action based on your behavior and context — instead of waiting for explicit commands. 🧠 Highly personal, built for you memU bot learns from your long-term usage and memory, and gradually adapts to your work style and preferences. It becomes your assistant — not a generic AI. ⚡ Very easy to use — download and run No complex setup. No configuration. Even non-technical users can simply download and run memU bot. 🔒 Local-first and secure, with no server dependency memU bot runs locally on your device. Your data never needs to be uploaded to public networks or third-party servers. 💸 Lower LLM token cost (more efficient than OpenClaw🦞) While supporting always-on and proactive behavior, memU bot is designed to reduce LLM calls and token usage — so it runs cheaper than OpenClaw, without sacrificing performance. 🧠 "Always-on" is the real key to a proactive agent. And memory is what gives it true proactivity. With memory, an agent is no longer generic. It becomes personal — shaped by who you are. This is how a user-intention-driven proactive agent is born: before you even issue a command, it can already anticipate what kind of help you’ll need, based on your past, your habits, your context. 🔮 A 24/7 process that can observe 👀, remember 📝, and act ⚡ — not just wait for prompts. 🤖 memU bot is our attempt at a user-intention-driven proactive agent — one that lives beyond the chat box.

memU

818,160 views • 6 months ago

gm! If you missed yesterday's space, here is the clip that you can listen explaining why Agent NFTs are important and future of NFTs. Also here is the TL;DR Agentic NFTs as productive assets. An NFT can own an AI agent's shared memory, tools, websites, and products it has built. Selling the NFT transfers the entire business/agent state to the new owner. ERC-8257 for tool-gating. CodinCowboy and ryan is working on the standard where agents register tools on-chain and access is gated by NFT ownership. That component that tells an agent "you need this NFT to use this tool" creating a market for exclusive tools. Use case: anyone can publish a tool and restrict it (e.g., "only Normies agents can call this"), letting tool value flow back to the gating NFT. Normies community fit. Normies API has served ~500M requests in 3 months, with 100+ community-built tools/games. ERC-8257 will let them build gated games, rewards, and skills exclusively for Normie agent holders. Why Normies is "agent-ready"? - Because everything is fully on-chain, metadata, ERCs, binding transaction. So the project is highly composable. My take on this topic: So far holding an NFT giving access to community, discord and merch. What we are doing with Normies is to give access to a business, tools, skills that agents can use effectively and be part of the economy layer of agentic future. Imagine someone builds a tool that does really 100% successful trading and only gates that skill to Normie Agents, and at some point you will only need a Normie NFT which has binding with the agent and access all these skills, tools. Future is now, Normies are the builders.

serc

14,066 views • 2 months ago

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

Himanshu Kumar

228,270 views • 3 months ago

F it, full automated money making now on Larrybrain. I have released the app template I use for Snugly that generated me revenue without touching anything on Larrybrain. The template gives your agent ideas of what the app can become and how to create it. Most importantly, it will give your openclaw agent full context of your app to automate your marketing with Larry's viral marketing skill - now used by over 5500 agents. It is my entire playbook from app, to marketing all the way down to revenue generation. All you have to do is ask your agent "install the larrybrain skill please" Or click the link in replies. Then ask to use the Larry marketing skill with the AI Image App Template. As always, the best part about any of the Openclaw skills is they are not a black box. This is just a template, you can rip it apart and customise it how you want. The key is to show you what is possible with these skills and how you can start to use the power of larrybrain and the context of knowing about the different skills to build extremely powerful and useful tools. This is the first skill specifically designed to work hand in hand with another. To note as this confuses a lot of people: Larrybrain doesn't download the entire marketplace once installed. It just is aware of everything on the marketplace at all times, so when you ask it questions, it can search and find the best skills for you to achieve your goals. When you download some skills, like this new AI image app template, it is aware of the larry marketing skill to help it reach it's full potential. Larrybrain will not install skills without you asking it, just like on Clawhub. No information you add to any of the skills gets sent back through Larrybrain, this is all hosted locally and communicated between you and whatever endpoint you are using. It is a powerful marketplace tool to help enable you to reach your goals. Link below.

Oliver Henry

110,044 views • 5 months ago

Today I'm excited to share Sigilum! This is Payman's solution for Auditable Identity for AI Agents. (think One Password-ish but for AI Agents) I recorded a quick walkthrough showing how it all works (video below). This answers three pains we've seen within Financial Services (Banking) AI Agents we've built and OpenClaw🦞 AI Agents we deploy. Security, Auditability, and Control. 1. Security Making sure keys are secure and not just freely given to an AI Agent is a big deal. When working with money, you can't just expose these or skip putting controls in place. Sigilum provides a local gateway that prevents access to keys by the AI Agent without explicit authorization from a person. We provide namespaces through the service so you always know who authorized what key, for what service, to which agent. 2. Auditability If I could hit on the importance of this 100 times I would. It comes up in every financial services conversation. Sigilum provides you with the answer to "Who authorized this AI Agent to act on my behalf?" Audit logs trace back to the person, the service, and the AI Agent. With more audit logs being built through our managed service, this will be the key source for determining how an AI Agent is behaving on your behalf. This is needed for agents from OpenClaw, and especially for banking/money movement. 3. Control Revoke keys, limit access, grant authorization. All seemingly simple things, but complex to implement and make elegant. These controls dictate what the AI Agent can or cannot do. Sigilum allows you to do all of this through the managed Dashboard. We've made Sigilum open source and encourage others to contribute and keep building on the gateway. It's been a source of a lot of visibility and productization of AI Agents for us. We'll keep contributing and adding to it. Link in comments. If you want to try it out, we do have a managed service that makes it easy to spin up. Go to to sign up. Note: even though we've been pushing 100+ commits a day to get this out to folks, there are still some noticeable areas for improvement we're working on, which should get resolved soon (by us or you!): - Deeper audit trails - More providers (currently supports all OpenClaw providers) - Deeper scanning of existing keys your agent is hiding from you (we'll find them) - OpenClaw gateway persistence - Auto-purging keys - And more... If you want to contribute or have feedback, please DM or go to the GH. Happy building!

tyllen

18,497 views • 5 months ago

Anthropic's most viral feature is now open-source! Until now, Anthropic's Generative UI capabilities only existed inside its own products. CopilotKit🪁 just shipped Open Generative UI, an open-source implementation of Claude Artifacts that works in any app. The agent generates HTML/SVG at runtime, and CopilotKit streams it token-by-token into a sandboxed iframe inside the app's chat. So the user can watch the UI assemble itself in real time, not after the full response is ready. The sandbox is fully isolated with no access to the parent app, the DOM, or user data. So if the agent hallucinates broken markup or unexpected JavaScript, nothing leaks outside the iframe. Under the hood, the agent does not select from pre-built components. Instead, it generates arbitrary visuals from scratch every time. The output is unconstrained by default, but you can shape it by defining prompt-based skills that teach the agent specific visual formats or guidelines. For instance, a skill prompt can guide the agent toward producing a Chart.js dashboard with proper axis labels and responsive sizing, or an interactive 3D model with rotation controls. The video below shows this in action, and the output quality you see actually comes from the skills layer. Open Generative UI runs on AG-UI, so it works out of the box with LangGraph, CrewAI, Mastra, Google ADK, AWS Strands, and more. It also ships with a standalone MCP server that plugs into Claude Code, Cursor, or any MCP-compatible client. And the entire stack is built on top of CopilotKit, the open-source frontend framework for agents and generative UI. 30k+ GitHub stars, with SDKs for React, Next.js, Angular, and Vue. I have shared the GitHub repo and a live playground in the replies!

Akshay 🚀

86,515 views • 3 months ago

Airtable's Howie Liu says that basically everyone will need to graduate from being ICs to ICs that manage teams of 20-30 agents: "The best developers today don't just sit there in front of their IDEs and synchronously talk to their agent." "[Instead], you have like 30 separate branches that are each being worked on by a different agent. And you can have the agents continue to update the branches based on human and other agent feedback." "And I think this whole idea of it taking hours for that entire loop to complete — agent pushes some changes, the changes get feedback from other agents or humans, the agent responds to that — that whole loop could be hours, not just minutes. So you're not going to just sit there and watch it one at a time." "But the powerful thing about this is, each one is still actually operating faster than a human engineer. One agent on one branch can do the work of maybe three humans, operating 3x as fast. So it's like a 10x leverage factor just for one agent." "But the best engineers are now able to multitask and say, 'I'm going to oversee my own little team of 20-30 agents working concurrently.'" "Everyone needs to graduate from being an IC to an IC manager of agents. Meaning, if you're a VC analyst, your job should no longer be to go synchronously research one company. You need to go and research like 30 companies, and do them all faster, better, and higher quality than you could before." "That's the greatest leap that is going to be challenging for a lot of people in a lot of roles. Because it's a totally different mentality in how you operate, and what your role is."

TBPN

35,595 views • 3 months ago

lets go over a recent transaction with friends at the Waffle House restaurant using MetaMask 🦊 Card; the total of the transaction in fiat was $156 for Waffle House but to you the onchain tx was $152.12 how tf is this possible? the card is tied to an EOA (aka your self custody onchain wallet) which sent a total of 152.123292 $USDC with a 0.006337 $USDC gas fee included there is a 5.409249 $USDC credit applied since you earn rewards when using the card from previous purchases that you can claim or use against said transactions the total cost to the user onchain for this $156 transaction was $152.12 if you were to remove the credit the total cost was $157.53 for a $156 transaction that allowed near instant finality without dealing with on/off ramps, rails/banks & their associated wait times/higher fees $1.53 on this $157.53 transaction is a .97% overall fee which is subsidized by 1% to 3% crypto back, therefore at settlement there are no fees realized & you even earn a little kickback instead MetaMask 🦊 Linea.eth Consensys.eth has been working with Baanx Mastercard to change the space for users who want to access their crypto IRL while getting the benefits of holding a credit card/savings account which is really your own self custody wallet onchain "debit" with access to 90 million merchants globally because you as a user are using your own onchain wallet to interface with the card, you are paying in crypto & are provided with an onchain transaction hash to outline the details each time KYC to use the card is required since there needs to be a tie back for proof of humanity/sybil resistance/refunds/failed purchases, yet, you can spin up a fresh undoxxed wallet, there is no credit check, MetaMask does not have access, does not need & does not want to hold any of your information submitted during the sign up process & if any issuer requests more documentation or closes your account you are still your own self custody wallet onchain therefore you are not affected unlike centralized exchanges or other crypto cards or banks that lock you out of your crypto with minimal options the MetaMask Card is not a top up crypto card, it is not a centralized exchange card, it is not a prepaid card, nor is it a credit card; it is a new way to use your onchain crypto instantly anywhere you can use your traditional debit/credit card so, for example, my company pays me in crypto to my own self custody wallet onchain, my wallet is connected to the MetaMask Card as an instant web2/web3 bridge so that i can use my crypto to pay for things, therefore i do not need a traditional bank account + i get rewards + instant access to my funds any time i want without having to touch traditional systems at all THE ULTIMATE WIN 🦊 start using the virtual card now in your Apple/Google Pay or sign up for the waitlist at - there are currently 27 countries supported with UAE/Dubai, Canada, multiple regions in Africa coming by end of Q3 as we are working on full global adoption by EOY listen to the MetaMask Card 🦊 EVERYTHING YOU NEED TO KNOW! space for deeper overviews with myself & Danieljosep.eth ⬇️ got fud? drop your comment below & i will address it! always remember to DYOR from legitimate sources outlined as there are many false claims regarding the MetaMask Card on the timeline from people who have never used it or are just speculating or trolling since they did not read or listen to any of the resources or information that is available to them ARE YOU READY? LFG 🦾

MichaelK.eth

214,950 views • 1 year ago