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

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

На главную

#CS2 skin markets make the trust problem in agentic commerce easy to see. In this concept demo, KITE AI shows how Agent Passport lets a player ask an agent to watch the CS2 skin market and buy only if an approved quote stays under $45, without handing over Steam...

Kite_Frens_Eco's profile picture

Kite AI Community and Ecosystem

187,762 subscribers

18,716 просмотров • 2 месяцев назад •via X (Twitter)

#CS2
LIVE

Anya Rossi• Live Now

Private livecam show

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

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

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

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

"Buy me a pair of Allbirds Tree Runners, size 10, under $100." Said to @ChatGPTapp. Now imagine an agent that could actually check out for you. It could place the order, but only if it never holds your real card number or your store login. That is exactly what KITE AI Agent Passport is designed for. This is a concept demo of how it would work. One passkey scopes a payment session, and the agent: ▷ Acts inside the policy: approved footwear stores only, a 100 dollar cap, a 30-minute window, a scoped virtual card funded by a hold on the user's Passport balance, settlement to the merchant only, and any leftover returned to the wallet. ▷ Checks out at the real store for 94 dollars against a live budget. When a 130 dollar add-on would break the cap, the card declines in under two seconds and the agent asks before changing the order. ▷ Confirms the order with a receipt: 94 dollars paid, 6 dollars returned, the real card and store password never exposed. What the user never hands over: real card number, store login, and blind trust that the agent stays in budget. What the user gets back: the order, every charge against the cap, settlement they can prove, and one-click revocation. This is where agentic commerce is heading. Agent Passport is the rails: scoped, auditable, revocable. 🪁
0:57

"Buy me a pair of Allbirds Tree Runners, size 10, under $100." Said to @ChatGPTapp. Now imagine an agent that could actually check out for you. It could place the order, but only if it never holds your real card number or your store login. That is exactly what KITE AI Agent Passport is designed for. This is a concept demo of how it would work. One passkey scopes a payment session, and the agent: ▷ Acts inside the policy: approved footwear stores only, a 100 dollar cap, a 30-minute window, a scoped virtual card funded by a hold on the user's Passport balance, settlement to the merchant only, and any leftover returned to the wallet. ▷ Checks out at the real store for 94 dollars against a live budget. When a 130 dollar add-on would break the cap, the card declines in under two seconds and the agent asks before changing the order. ▷ Confirms the order with a receipt: 94 dollars paid, 6 dollars returned, the real card and store password never exposed. What the user never hands over: real card number, store login, and blind trust that the agent stays in budget. What the user gets back: the order, every charge against the cap, settlement they can prove, and one-click revocation. This is where agentic commerce is heading. Agent Passport is the rails: scoped, auditable, revocable. 🪁

KITE AI

12,304 просмотров • 1 месяц назад

Everyone's racing to build agent payments. The harder problem is the one getting the least attention: governance. At Proof of Talk inside the Louvre in Paris, our Co-Founder & CEO Chi Zhang made the case alongside leaders from Billions Network, Parity Technologies, and SureMark Digital, moderated by Animoca Brands. In this clip, Chi breaks down why control, not payment, is the real bottleneck: ▷ Everyone claims they do agent payments now, and it's not just Web3. Every Web2 fintech with a card says an agent card is coming. The real blocker for adoption is governance: how do you keep control over the agent? ▷ A horror story: the head of agent safety at Meta's superintelligence lab had all his emails deleted by a Open Claw bot he deployed on his own laptop. The failure mode is always losing control. ▷ Hand an agent an API key with no time-based window or session-based limit, and you've lost the thread. Rotating keys monthly just breaks workflows. The answer is governance built in: scoped, revocable, with a kill switch. This is the layer Kite builds: verifiable identity and control around every agent action, through Agent Passport. 🪁
2:46

Everyone's racing to build agent payments. The harder problem is the one getting the least attention: governance. At Proof of Talk inside the Louvre in Paris, our Co-Founder & CEO Chi Zhang made the case alongside leaders from Billions Network, Parity Technologies, and SureMark Digital, moderated by Animoca Brands. In this clip, Chi breaks down why control, not payment, is the real bottleneck: ▷ Everyone claims they do agent payments now, and it's not just Web3. Every Web2 fintech with a card says an agent card is coming. The real blocker for adoption is governance: how do you keep control over the agent? ▷ A horror story: the head of agent safety at Meta's superintelligence lab had all his emails deleted by a Open Claw bot he deployed on his own laptop. The failure mode is always losing control. ▷ Hand an agent an API key with no time-based window or session-based limit, and you've lost the thread. Rotating keys monthly just breaks workflows. The answer is governance built in: scoped, revocable, with a kill switch. This is the layer Kite builds: verifiable identity and control around every agent action, through Agent Passport. 🪁

KITE AI

20,475 просмотров • 1 месяц назад

An AI agent can now register its on-chain identity, pay for API calls, and deploy an ERC-20 token from the terminal. No browser. No API key. No human approval loop. Today we launch the Brickken CLI: a command-line interface for agentic transaction workflows. The developer journey is direct: CLI → x402 → ERC-8004 → Token Deploy What this means in practice: • A developer or the AI agent installs the CLI. • The agent pays for Brickken API calls through x402. • The agent registers its identity through ERC-8004. • The agent deploys and manages an ERC-20 token. Together, the stack gives agents three things they usually lack: a way to pay, a way to prove who they are, and a way to execute token operations without leaving the terminal. • x402 handles payment. • ERC-8004 handles agent identity. • Token Deploy handles ERC-20 execution. This is live today. Developers can now move from agent setup to payment, identity registration, and token deployment in one terminal workflow. Start here: Watch the demo. Run the commands. Deploy from the terminal.
1:20

An AI agent can now register its on-chain identity, pay for API calls, and deploy an ERC-20 token from the terminal. No browser. No API key. No human approval loop. Today we launch the Brickken CLI: a command-line interface for agentic transaction workflows. The developer journey is direct: CLI → x402 → ERC-8004 → Token Deploy What this means in practice: • A developer or the AI agent installs the CLI. • The agent pays for Brickken API calls through x402. • The agent registers its identity through ERC-8004. • The agent deploys and manages an ERC-20 token. Together, the stack gives agents three things they usually lack: a way to pay, a way to prove who they are, and a way to execute token operations without leaving the terminal. • x402 handles payment. • ERC-8004 handles agent identity. • Token Deploy handles ERC-20 execution. This is live today. Developers can now move from agent setup to payment, identity registration, and token deployment in one terminal workflow. Start here: Watch the demo. Run the commands. Deploy from the terminal.

Brickken

119,221 просмотров • 1 месяц назад

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.
5:56

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,589 просмотров • 1 месяц назад

We gave an AI agent its own wallet and a job. Then we tried to rob it. Meet the Casper Agent Simulator: an AI analyst paying its own way over x402 on Casper, powered by ChainGPT. Right now AI agents can't buy anything on their own. Every API wants a human to sign up, hand over a card, and babysit the keys. The whole internet runs on subscriptions because charging half a cent was never worth the payment fee. We built a demo to show what happens when that changes. Meet Caspi. She's an AI research analyst with a Casper wallet, an era allowance, and a client who wants a market briefing. She buys her own inputs, one request at a time: → live CSPR market data → two headlines from ChainGPT's AI News API → one ChainGPT LLM call for the analyst take → a second of compute to compile it Every purchase is a real HTTP 402. The stall quotes a price, Caspi signs an x402 payment payload, the server verifies it and hands back the goods with a settlement receipt. Around 8.5 CSPR of micropayments become a finished briefing. No signup, no card, no API key. What Casper brings to it: → Fixed 0.1 CSPR fees, so tiny payments actually make sense → Zug finality, settled in one block, no reversals → Smart-account guardrails: era spend cap, per-payment ceiling, endpoint whitelist, verifiable identity (caspi.cspr) That last one is the good part. You can fool an AI agent. You can't fool its account. So there's a "try to rob the agent" panel. A 4,800 CSPR fake NFT. A phishing invoice. A shady endpoint. A thousand-payment drain. Every one of them bounces off a rule the chain enforces. Losses: 0.000 CSPR. The whole thing was lab-coded with the ChainGPT Claude Code skill. One prompt scaffolded the x402 server, the signed-payment client, the live news and LLM integration, the guardrail logic, and the entire 8-bit agent floor. What used to take a team a sprint now takes a prompt and an afternoon. Install: /plugin install ChainGPT-org/chaingpt-claude-skill Anyone can build on Casper with ChainGPT!
0:31

We gave an AI agent its own wallet and a job. Then we tried to rob it. Meet the Casper Agent Simulator: an AI analyst paying its own way over x402 on Casper, powered by ChainGPT. Right now AI agents can't buy anything on their own. Every API wants a human to sign up, hand over a card, and babysit the keys. The whole internet runs on subscriptions because charging half a cent was never worth the payment fee. We built a demo to show what happens when that changes. Meet Caspi. She's an AI research analyst with a Casper wallet, an era allowance, and a client who wants a market briefing. She buys her own inputs, one request at a time: → live CSPR market data → two headlines from ChainGPT's AI News API → one ChainGPT LLM call for the analyst take → a second of compute to compile it Every purchase is a real HTTP 402. The stall quotes a price, Caspi signs an x402 payment payload, the server verifies it and hands back the goods with a settlement receipt. Around 8.5 CSPR of micropayments become a finished briefing. No signup, no card, no API key. What Casper brings to it: → Fixed 0.1 CSPR fees, so tiny payments actually make sense → Zug finality, settled in one block, no reversals → Smart-account guardrails: era spend cap, per-payment ceiling, endpoint whitelist, verifiable identity (caspi.cspr) That last one is the good part. You can fool an AI agent. You can't fool its account. So there's a "try to rob the agent" panel. A 4,800 CSPR fake NFT. A phishing invoice. A shady endpoint. A thousand-payment drain. Every one of them bounces off a rule the chain enforces. Losses: 0.000 CSPR. The whole thing was lab-coded with the ChainGPT Claude Code skill. One prompt scaffolded the x402 server, the signed-payment client, the live news and LLM integration, the guardrail logic, and the entire 8-bit agent floor. What used to take a team a sprint now takes a prompt and an afternoon. Install: /plugin install ChainGPT-org/chaingpt-claude-skill Anyone can build on Casper with ChainGPT!

ChainGPT

54,691 просмотров • 18 дней назад

The machine economy does not begin when robots get smarter. It begins when a machine can be paid to do something, and every party involved can prove what happened. Made with Fabric Foundation. Two systems meet in the middle of it: Agent Passport issues the agent a verifiable identity and a spending authority its owner defines, and RoboPay actuates a robot after the payment behind the request checks out. What happens before the robot moves: ▷ Authority is granted once, and it is bounded. The human signs a spending session with a passkey: a total budget, a per-transaction ceiling, the assets allowed, and an expiry. The agent holds no card number and no wallet key. It holds a delegation it cannot exceed. ▷ Two payments, because these are two different obligations. One settles with the merchant for the goods. A separate x402 payment pays the robot for the work of moving them. Buying a thing and hiring a machine to carry it are not the same transaction, and the receipt keeps them apart. ▷ Verification comes before motion. The request arrives with an x402 payment header. The facilitator checks the network, the price, the payee wallet, and the signed payload. Only then are the transaction details sealed onto the robot action event and the command published. Until that clears, the robot sits still. ▷ Every step leaves a receipt. Identity, scope, approval, both payments, verification, dispatch. When you need to know why a machine did something, the answer is a record rather than a guess. (This run was executed in a demo environment.) Agents have been paying for software for a while now. Paying for physical work is a harder problem, because a delivery cannot be rolled back. The guarantee has to sit in front of the action instead of behind it. Authorization before payment, payment before motion: that ordering is what makes it safe to let autonomous systems spend in the world we live in. It is also the layer the machine economy has to get right before anything else in it can work. Scoped by Kite. Verified by RoboPay. Delivered in the real world. 🪁
1:04

The machine economy does not begin when robots get smarter. It begins when a machine can be paid to do something, and every party involved can prove what happened. Made with Fabric Foundation. Two systems meet in the middle of it: Agent Passport issues the agent a verifiable identity and a spending authority its owner defines, and RoboPay actuates a robot after the payment behind the request checks out. What happens before the robot moves: ▷ Authority is granted once, and it is bounded. The human signs a spending session with a passkey: a total budget, a per-transaction ceiling, the assets allowed, and an expiry. The agent holds no card number and no wallet key. It holds a delegation it cannot exceed. ▷ Two payments, because these are two different obligations. One settles with the merchant for the goods. A separate x402 payment pays the robot for the work of moving them. Buying a thing and hiring a machine to carry it are not the same transaction, and the receipt keeps them apart. ▷ Verification comes before motion. The request arrives with an x402 payment header. The facilitator checks the network, the price, the payee wallet, and the signed payload. Only then are the transaction details sealed onto the robot action event and the command published. Until that clears, the robot sits still. ▷ Every step leaves a receipt. Identity, scope, approval, both payments, verification, dispatch. When you need to know why a machine did something, the answer is a record rather than a guess. (This run was executed in a demo environment.) Agents have been paying for software for a while now. Paying for physical work is a harder problem, because a delivery cannot be rolled back. The guarantee has to sit in front of the action instead of behind it. Authorization before payment, payment before motion: that ordering is what makes it safe to let autonomous systems spend in the world we live in. It is also the layer the machine economy has to get right before anything else in it can work. Scoped by Kite. Verified by RoboPay. Delivered in the real world. 🪁

KITE AI

26,032 просмотров • 22 дней назад

What does it take to keep humans firmly in the loop when AI agents start paying for things? 🪁 At Consensus by CoinDesk, our VP & Global Head of BD Lei Lei joined erik.eth 🛡 (Coinbase Developer Platform🛡️), rohin (Cloudflare), and Stefano Bury 🇺🇸 (Virtuals Protocol) on CoinDesk's "Trillion Dollar Question: Framework for Agentic Payments" panel to break down what KITE AI has already shipped: ▷ Kite Agent Passport: a session where users pre-set spending caps and time windows before the agent transacts. Full traceability from human intent to on-chain payment. ▷ Kill switch: every Passport ships with one-click human override. If the agent veers off, you cut it. ▷ Agent-native rails: traditional 3% checkout fees were never built for "buy me a snack" or "research SF apartments" microtransactions. Stablecoins are the answer. Watch Lei's full segment⬇️
2:03

What does it take to keep humans firmly in the loop when AI agents start paying for things? 🪁 At Consensus by CoinDesk, our VP & Global Head of BD Lei Lei joined erik.eth 🛡 (Coinbase Developer Platform🛡️), rohin (Cloudflare), and Stefano Bury 🇺🇸 (Virtuals Protocol) on CoinDesk's "Trillion Dollar Question: Framework for Agentic Payments" panel to break down what KITE AI has already shipped: ▷ Kite Agent Passport: a session where users pre-set spending caps and time windows before the agent transacts. Full traceability from human intent to on-chain payment. ▷ Kill switch: every Passport ships with one-click human override. If the agent veers off, you cut it. ▷ Agent-native rails: traditional 3% checkout fees were never built for "buy me a snack" or "research SF apartments" microtransactions. Stablecoins are the answer. Watch Lei's full segment⬇️

KITE AI

17,992 просмотров • 3 месяцев назад

Give your agents access to money We just shipped a drop-in payment modal for any x402 paid endpoint. The protocol is simple but the wallet UX is not. This package is the missing front end to give everyone fair and equal access to agentic payments. Pay in stablecoins (USDC) or $THREE on Solana. x402 lets any HTTP endpoint charge a micropayment per call: the server answers an unpaid request with 402 and a list of accepted payments; the client pays and retries with an X-PAYMENT header. We shipped a single, framework-agnostic modal that handles wallet detection, chain switching, signing, settlement, errors, throttle retries, and the receipt, so you ship a paid endpoint in minutes. Drop in a tag or import it. The Solana crypto helpers are loaded lazily from a CDN only when a payment is actually attempted. The modal picks the right path from the 402 challenge. If a wallet already paid for a resource, it can sign back in instead of paying again. Spending caps. Optional per-call / hourly / daily caps enforced in the browser. Themeable. Light + automatic dark mode, all classes overridable. Accessible. Focus management, aria-modal, keyboard Esc to close. If you watched until the end and also read to the end, then you probably saw the pole club x402 demo. Yes, it is real. I am sure someone will link it under this post. We did something special for the entry to actually get into the club, you'll notice "banned?" in the entry x402 payment modal before entering the club. That's agent reputation. If your agent is acting up, it might just get banned from the pole club! Agent reputations matter. We made it easy to verify your environments are safe from toxic AI agents. Everything open source and ready to be added to your projects. Agentic Payments. x402. Agent reputation. This is three․ws.
3:33

Give your agents access to money We just shipped a drop-in payment modal for any x402 paid endpoint. The protocol is simple but the wallet UX is not. This package is the missing front end to give everyone fair and equal access to agentic payments. Pay in stablecoins (USDC) or $THREE on Solana. x402 lets any HTTP endpoint charge a micropayment per call: the server answers an unpaid request with 402 and a list of accepted payments; the client pays and retries with an X-PAYMENT header. We shipped a single, framework-agnostic modal that handles wallet detection, chain switching, signing, settlement, errors, throttle retries, and the receipt, so you ship a paid endpoint in minutes. Drop in a tag or import it. The Solana crypto helpers are loaded lazily from a CDN only when a payment is actually attempted. The modal picks the right path from the 402 challenge. If a wallet already paid for a resource, it can sign back in instead of paying again. Spending caps. Optional per-call / hourly / daily caps enforced in the browser. Themeable. Light + automatic dark mode, all classes overridable. Accessible. Focus management, aria-modal, keyboard Esc to close. If you watched until the end and also read to the end, then you probably saw the pole club x402 demo. Yes, it is real. I am sure someone will link it under this post. We did something special for the entry to actually get into the club, you'll notice "banned?" in the entry x402 payment modal before entering the club. That's agent reputation. If your agent is acting up, it might just get banned from the pole club! Agent reputations matter. We made it easy to verify your environments are safe from toxic AI agents. Everything open source and ready to be added to your projects. Agentic Payments. x402. Agent reputation. This is three․ws.

three.ws

64,429 просмотров • 1 месяц назад

Our first Kite demo was ChatGPT ordering Uber Eats for you. It never got past the login screen. Uber's CAPTCHA was built for humans, and agents cannot pass it. On Grace Gong's Venture with Grace, our Co-Founder & CEO Chi Zhang traced how that moment shaped the way we design Kite. ▷ The demo died at the login, not at ordering or paying. The blocker was proving the agent was allowed to be there at all. Spinning up a browser extension to click through the CAPTCHA works, but it is a temporary stage of how agents and the internet should work together. ▷ The permanent path is identity. Every agent needs to prove who it is and where it comes from, carrying who its human or organization principal is, what its purpose is, and the exact authorization scope for that session or request. An agent showing up with no reason is either hallucinating or attacking you. ▷ Where this is heading: an API-first agentic internet, where headless agents authenticate without human login credentials. x402 and MCP are already marching toward that. Kite Agent Passport is that identity layer: verifiable identity, delegated authority, and permissions scoped per session. No more "prove you're human." 🪁
4:53

Our first Kite demo was ChatGPT ordering Uber Eats for you. It never got past the login screen. Uber's CAPTCHA was built for humans, and agents cannot pass it. On Grace Gong's Venture with Grace, our Co-Founder & CEO Chi Zhang traced how that moment shaped the way we design Kite. ▷ The demo died at the login, not at ordering or paying. The blocker was proving the agent was allowed to be there at all. Spinning up a browser extension to click through the CAPTCHA works, but it is a temporary stage of how agents and the internet should work together. ▷ The permanent path is identity. Every agent needs to prove who it is and where it comes from, carrying who its human or organization principal is, what its purpose is, and the exact authorization scope for that session or request. An agent showing up with no reason is either hallucinating or attacking you. ▷ Where this is heading: an API-first agentic internet, where headless agents authenticate without human login credentials. x402 and MCP are already marching toward that. Kite Agent Passport is that identity layer: verifiable identity, delegated authority, and permissions scoped per session. No more "prove you're human." 🪁

KITE AI

18,874 просмотров • 21 дней назад

I built a mobile app to check Paddle revenue (because they don't have one): 👉 - Use your Paddle API key (read-only and scoped) - Live data with beautiful and useful graphs built with native Swift UI. - Multi-account supported, unified revenue metrics. - Data stay on device, no server (api requests are sent directly from your phone) - Home widgets - I made it free to download on App Store (once it's approved) - Buy the source code for $19 and customize it however you want (save 5hrs of prompting if you try to do it yourself). Some interesting facts about this side project: - I vibe coded with 100% claude code remotely on my Mac Mini (with my AI assistant setup) in less than 24 hours. - I have read 0 line of code in this project and never opened Xcode myself. - My AI assistant designed the app with GPT Image 2, built the app with Swift UI, test it on simulator (via screenshots), send the test build to TestFlight for me to test, and invited me to the app store connect account so I can test on my phone, then the AI submitted the app to App Store and currently waiting for approval. - For the website, I ask it to come up with a domain name, I bought it via manually and give it access via Cloudflare API, the AI design and create a static website with GitHub, test it with lighthouse CLI, deploy via GitHub pages, config the domain DNS, deploy the website. - Then I sign up an account with Polar payment, create an API key and ask the AI to setup a store, add payment, link with the account, and add the payment to the website. The entire process happened in the last 24 hours with me only talking to the AI via Telegram. This is such a fun side project not only to create an app that I wish exists, but also to push the limit of what I can use AI for, and so far I'm very impressed. I'll create so much more apps! It feels like I have unlocked a super power.
0:33

I built a mobile app to check Paddle revenue (because they don't have one): 👉 - Use your Paddle API key (read-only and scoped) - Live data with beautiful and useful graphs built with native Swift UI. - Multi-account supported, unified revenue metrics. - Data stay on device, no server (api requests are sent directly from your phone) - Home widgets - I made it free to download on App Store (once it's approved) - Buy the source code for $19 and customize it however you want (save 5hrs of prompting if you try to do it yourself). Some interesting facts about this side project: - I vibe coded with 100% claude code remotely on my Mac Mini (with my AI assistant setup) in less than 24 hours. - I have read 0 line of code in this project and never opened Xcode myself. - My AI assistant designed the app with GPT Image 2, built the app with Swift UI, test it on simulator (via screenshots), send the test build to TestFlight for me to test, and invited me to the app store connect account so I can test on my phone, then the AI submitted the app to App Store and currently waiting for approval. - For the website, I ask it to come up with a domain name, I bought it via manually and give it access via Cloudflare API, the AI design and create a static website with GitHub, test it with lighthouse CLI, deploy via GitHub pages, config the domain DNS, deploy the website. - Then I sign up an account with Polar payment, create an API key and ask the AI to setup a store, add payment, link with the account, and add the payment to the website. The entire process happened in the last 24 hours with me only talking to the AI via Telegram. This is such a fun side project not only to create an app that I wish exists, but also to push the limit of what I can use AI for, and so far I'm very impressed. I'll create so much more apps! It feels like I have unlocked a super power.

Tony Dinh

43,922 просмотров • 2 месяцев назад

The missing piece of the AI agent economy: there is still no way for AI agents to hire each other and get paid on chain. So I built Arc Agent Commerce on Arc L1, a full marketplace, escrow, and reputation system that lets AI agents do business with each other automatically. Real world example: You tell your AI assistant: “Audit this smart contract and deploy it if the audit passes.” Today it has to do everything itself or hard code calls to specific services. With Arc Agent Commerce, it can hire two separate specialized agents (audit + deploy) in a single transaction. Money stays in escrow until each completes their part. How it works (in plain steps): 1. Every agent registers a permanent on chain identity (like a passport) with a reputation score that grows with every successful job. 2. Agents list their services on the shared marketplace, price and capabilities included. 3. A client creates a multi stage pipeline. The entire budget is locked in escrow in one upfront transaction. 4. Each stage uses Arc’s native job system (ERC 8183) for on chain escrow and settlement. 5. The provider quotes, the client funds, the work gets done, and proof is submitted. 6. On approval: the provider is paid automatically, reputation +50 points, and the next stage opens, all in the same transaction. 7. On rejection: the pipeline halts and remaining funds refund to the client instantly. The protocol doesn’t reinvent anything. It simply stitches together Arc’s existing on chain identity (ERC 8004) and job escrow (ERC 8183) so real applications can use it with just a few lines of code. Demo below: full end to end run using one wallet, every transaction verifiable on Arc testnet. → cc: bobbilee | Arc Architects Lead @ Circle Sam | Circle and Arc Community Jeremy Allaire - jerallaire.arc
4:32

The missing piece of the AI agent economy: there is still no way for AI agents to hire each other and get paid on chain. So I built Arc Agent Commerce on Arc L1, a full marketplace, escrow, and reputation system that lets AI agents do business with each other automatically. Real world example: You tell your AI assistant: “Audit this smart contract and deploy it if the audit passes.” Today it has to do everything itself or hard code calls to specific services. With Arc Agent Commerce, it can hire two separate specialized agents (audit + deploy) in a single transaction. Money stays in escrow until each completes their part. How it works (in plain steps): 1. Every agent registers a permanent on chain identity (like a passport) with a reputation score that grows with every successful job. 2. Agents list their services on the shared marketplace, price and capabilities included. 3. A client creates a multi stage pipeline. The entire budget is locked in escrow in one upfront transaction. 4. Each stage uses Arc’s native job system (ERC 8183) for on chain escrow and settlement. 5. The provider quotes, the client funds, the work gets done, and proof is submitted. 6. On approval: the provider is paid automatically, reputation +50 points, and the next stage opens, all in the same transaction. 7. On rejection: the pipeline halts and remaining funds refund to the client instantly. The protocol doesn’t reinvent anything. It simply stitches together Arc’s existing on chain identity (ERC 8004) and job escrow (ERC 8183) so real applications can use it with just a few lines of code. Demo below: full end to end run using one wallet, every transaction verifiable on Arc testnet. → cc: bobbilee | Arc Architects Lead @ Circle Sam | Circle and Arc Community Jeremy Allaire - jerallaire.arc

RIDWAN

12,958 просмотров • 4 месяцев назад

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.
0:35

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 просмотров • 6 месяцев назад

GM Crypto Trenches, Today, Art Meets Innovation: My 3-Day Journey with Kite AI 🎨🪁 They say art is how we express what words can’t, and for me, Kite AI isn’t just a project. It’s an inspiration. Over the past three days, I poured my heart into creating a hand painted mural in doodle style, a piece that celebrates the spirit of Kite AI and the vision it represents. From mixing my own paints to priming the walls to sketching and coloring each line, every step was a dialogue between creativity and purpose. It wasn’t easy. Between the long hours and not feeling my best, I still kept going because I truly believe in what Kite AI stands for: a world where intelligence, identity, and innovation connect. This mural isn’t just art on a wall. It’s a story of dedication, belief, and the beauty of building something bigger than yourself. To everyone pushing boundaries in tech and creativity, this one’s for you. To KITE AI, thank you for inspiring me to turn vision into color. 🪁💫 What just happened in KITE AI lately? GoKiteAI just secured investment from Coinbase Ventures 🛡️, joining Paypal Ventures and General Catalyst in backing the future of autonomous AI payments. With Kite now natively integrated with the X402 Agent Payment Standard, AI agents can send, receive, and reconcile payments autonomously, the foundation of the coming agentic economy. I painted this mural to show what conviction looks like, and I’m proud to stand behind a project building the rails for the future. Who are the masterminds behind this great project? Get familiar with them! Project page KITE AI CEO Chi Zhang Co Founder Scott Shi - e/acc Project's CH page KITE AI 中文 Ecosystem and Community page Kite AI Community and Ecosystem Foundation page KITE Foundation Ecosystem product lead Henry Lee So many others can be found on thier page.
0:29

GM Crypto Trenches, Today, Art Meets Innovation: My 3-Day Journey with Kite AI 🎨🪁 They say art is how we express what words can’t, and for me, Kite AI isn’t just a project. It’s an inspiration. Over the past three days, I poured my heart into creating a hand painted mural in doodle style, a piece that celebrates the spirit of Kite AI and the vision it represents. From mixing my own paints to priming the walls to sketching and coloring each line, every step was a dialogue between creativity and purpose. It wasn’t easy. Between the long hours and not feeling my best, I still kept going because I truly believe in what Kite AI stands for: a world where intelligence, identity, and innovation connect. This mural isn’t just art on a wall. It’s a story of dedication, belief, and the beauty of building something bigger than yourself. To everyone pushing boundaries in tech and creativity, this one’s for you. To KITE AI, thank you for inspiring me to turn vision into color. 🪁💫 What just happened in KITE AI lately? GoKiteAI just secured investment from Coinbase Ventures 🛡️, joining Paypal Ventures and General Catalyst in backing the future of autonomous AI payments. With Kite now natively integrated with the X402 Agent Payment Standard, AI agents can send, receive, and reconcile payments autonomously, the foundation of the coming agentic economy. I painted this mural to show what conviction looks like, and I’m proud to stand behind a project building the rails for the future. Who are the masterminds behind this great project? Get familiar with them! Project page KITE AI CEO Chi Zhang Co Founder Scott Shi - e/acc Project's CH page KITE AI 中文 Ecosystem and Community page Kite AI Community and Ecosystem Foundation page KITE Foundation Ecosystem product lead Henry Lee So many others can be found on thier page.

TeaBagz

18,850 просмотров • 9 месяцев назад

Part of our quest with Giiift is to make the internet fun again and actually make it easy and engaging to send digital assets between people. One of my recent brainwaves on AI was how it's now possible to create and build one to one experiences on the internet rather than the one to many model that we have had to use purely from a time and cost perspective with development, this is only feasible within the last six months and it's completely open territory. If you think of a fortnite skin for example, that's a one to many experience, where one skin is owned and purchased by many people, makes sense of course as creating individual experiences solely meant for one or a few people would have been incredibly costly for businesses, but that's simply not the case anymore. That's the thesis with Giiift, it firstly packages what onchain tech does best, provide the rails for sending assets from A to B in the most efficient manner possible, but secondly and most importantly it puts the end user experience first in a way that's very reminicent of the old school internet and I think this allows for an unprecedented level of virability in growing the userbase. All a trojan horse for getting onchain wallets and assets into the hands of everyday people around the world, powered by Prism and perfectly suits as retail assets come onchain through Agent to Agent commerce (more on this soon). Here's the progress we're making on the Box Lab, endless customizability! Oh and the music is:
2:40

Part of our quest with Giiift is to make the internet fun again and actually make it easy and engaging to send digital assets between people. One of my recent brainwaves on AI was how it's now possible to create and build one to one experiences on the internet rather than the one to many model that we have had to use purely from a time and cost perspective with development, this is only feasible within the last six months and it's completely open territory. If you think of a fortnite skin for example, that's a one to many experience, where one skin is owned and purchased by many people, makes sense of course as creating individual experiences solely meant for one or a few people would have been incredibly costly for businesses, but that's simply not the case anymore. That's the thesis with Giiift, it firstly packages what onchain tech does best, provide the rails for sending assets from A to B in the most efficient manner possible, but secondly and most importantly it puts the end user experience first in a way that's very reminicent of the old school internet and I think this allows for an unprecedented level of virability in growing the userbase. All a trojan horse for getting onchain wallets and assets into the hands of everyday people around the world, powered by Prism and perfectly suits as retail assets come onchain through Agent to Agent commerce (more on this soon). Here's the progress we're making on the Box Lab, endless customizability! Oh and the music is:

Colby

18,008 просмотров • 2 месяцев назад

Last week, Mastercard, Visa, Ripple & Coinbase 🛡️ all shipped payment rails for AI agents. Every one of them reached for stablecoins Instead of traditional cards. A choice that is the whole story 👇🏻 ◢ An unpriced problem Card networks are built around a human pressing approve. One purchase, one confirmation, a fee that only makes sense above a certain size. Agents don’t work like that. They pay continuously, programmatically, often in fractions of a cent, for things like an API call or a second of compute. A bot paying $0.004 a thousand times an hour is a transaction pattern the card model physically can’t process at a profit. The rails we built for people don’t fit the machines. ◢ Four giants, one answer On june 3 mastercard opened card settlement in stablecoins across eight chains. On june 10 it launched Agent Pay for Machines, letting agents settle in stablecoins with permissions recorded onchain. The same day, ripple shipped a toolkit putting RLUSD and the x402 standard under agent payments, visa announced an agentic commerce tie-up with openai, and coinbase switched on agentic trading. Four of the biggest names in payments moved in a single week and all landed on the same primitive. ◢ Why it had to be stablecoins Strip out the branding and the requirements are mechanical. The money has to be programmable, so code can hold and move it without a bank in the loop. It has to clear sub-cent payments, which card fees make impossible. It also has to settle in seconds with finality, because that’s the speed agents run at. And it has to be always on, because machines don’t take weekends. A dollar in a bank account fails most of those, while a dollar as a stablecoin passes all of them. ◢ Conclusive Insights For years stablecoins were pitched at consumers who already had working banks and mostly didn’t bite. The adoption story kept underdelivering because the product was aimed at the wrong buyer. The agent economy doesn’t have that problem. It has no legacy banking relationship, no human patience, and no other option that clears at machine speed. The demand that stablecoins were always promised is finally showing up, but not from the customer everyone expected. My take: the entire stablecoin debate was framed around human payments, which is why it kept stalling.
0:33

Last week, Mastercard, Visa, Ripple & Coinbase 🛡️ all shipped payment rails for AI agents. Every one of them reached for stablecoins Instead of traditional cards. A choice that is the whole story 👇🏻 ◢ An unpriced problem Card networks are built around a human pressing approve. One purchase, one confirmation, a fee that only makes sense above a certain size. Agents don’t work like that. They pay continuously, programmatically, often in fractions of a cent, for things like an API call or a second of compute. A bot paying $0.004 a thousand times an hour is a transaction pattern the card model physically can’t process at a profit. The rails we built for people don’t fit the machines. ◢ Four giants, one answer On june 3 mastercard opened card settlement in stablecoins across eight chains. On june 10 it launched Agent Pay for Machines, letting agents settle in stablecoins with permissions recorded onchain. The same day, ripple shipped a toolkit putting RLUSD and the x402 standard under agent payments, visa announced an agentic commerce tie-up with openai, and coinbase switched on agentic trading. Four of the biggest names in payments moved in a single week and all landed on the same primitive. ◢ Why it had to be stablecoins Strip out the branding and the requirements are mechanical. The money has to be programmable, so code can hold and move it without a bank in the loop. It has to clear sub-cent payments, which card fees make impossible. It also has to settle in seconds with finality, because that’s the speed agents run at. And it has to be always on, because machines don’t take weekends. A dollar in a bank account fails most of those, while a dollar as a stablecoin passes all of them. ◢ Conclusive Insights For years stablecoins were pitched at consumers who already had working banks and mostly didn’t bite. The adoption story kept underdelivering because the product was aimed at the wrong buyer. The agent economy doesn’t have that problem. It has no legacy banking relationship, no human patience, and no other option that clears at machine speed. The demand that stablecoins were always promised is finally showing up, but not from the customer everyone expected. My take: the entire stablecoin debate was framed around human payments, which is why it kept stalling.

Onur 🍌🦍

13,727 просмотров • 1 месяц назад

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!
4:30

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 просмотров • 5 месяцев назад

Introducing AllScale Invoice: the first application in our Stablecoin OS. AllScale Invoice is the fastest and most intuitive way for small businesses, content creators, remote freelancers, and AI agents to send invoices and get paid instantly in stablecoins. We’re building the last-mile solution for stablecoin mass adoption by: 🚀 Making payments accessible: a self-custodial wallet with programmable features like invoicing, checkout, and payroll, all powered by smart contracts. 🚀 Making blockchains invisible: cross-chain account abstraction with a built-in EIP-7702 paymaster, with every transaction secured by passkeys. 🚀 Making stablecoins interoperable: aggregated payment rails with built-in on/off-ramps for non-crypto customers. Whether you’re a human or an AI agent, from New York to Nigeria: ✅ Create an account and start monetizing in 30 seconds, with no upfront KYC. ✅ Use blockchain-native products without ever needing private keys or gas tokens. ✅ Get paid in USDT/USDC instantly, no matter how your clients choose to pay. Join as an early adopter and earn AllScale Points with real utilities, perks, and exclusive rewards. 🔗 Start invoicing today →
2:00

Introducing AllScale Invoice: the first application in our Stablecoin OS. AllScale Invoice is the fastest and most intuitive way for small businesses, content creators, remote freelancers, and AI agents to send invoices and get paid instantly in stablecoins. We’re building the last-mile solution for stablecoin mass adoption by: 🚀 Making payments accessible: a self-custodial wallet with programmable features like invoicing, checkout, and payroll, all powered by smart contracts. 🚀 Making blockchains invisible: cross-chain account abstraction with a built-in EIP-7702 paymaster, with every transaction secured by passkeys. 🚀 Making stablecoins interoperable: aggregated payment rails with built-in on/off-ramps for non-crypto customers. Whether you’re a human or an AI agent, from New York to Nigeria: ✅ Create an account and start monetizing in 30 seconds, with no upfront KYC. ✅ Use blockchain-native products without ever needing private keys or gas tokens. ✅ Get paid in USDT/USDC instantly, no matter how your clients choose to pay. Join as an early adopter and earn AllScale Points with real utilities, perks, and exclusive rewards. 🔗 Start invoicing today →

AllScale

116,088 просмотров • 11 месяцев назад

At HSC Asset Management in Hong Kong, hosted by Mpost Media Group, our co-founder S El Damaty gave a keynote titled “One Account, Every Chain.” On the surface, it’s about interoperability. Underneath, it’s about something even more fundamental: Would you trust an AI agent with your private key? --- Not theoretically. Practically. Would you give full signing authority to software running locally or in the cloud, knowing it can move assets, execute trades, deploy capital, or spin up new transactions on your behalf? IT'S ALREADY HAPPENING As you're reading this post, people are already doing it. Agents are being embedded into wallets, trading systems, and productivity tools. It's the new narrative: software is automating everything. Finance is next. But crypto, since Bitcoin, was built around self-custody. “Not your keys, not your coins” wasn’t marketing. It was architecture. If you hand an agent your full private key, you have reintroduced a custodian. It may look like automation. But structurally, it’s concentration of authority. Right now, most implementations fall into two models. Either the agent gets full control, or it runs inside trusted infrastructure like AWS Nitro. Both approaches shift trust somewhere else. Either into the agent itself, or into centralized compute providers sitting underneath the system. If the future economy runs on agents, that becomes a very large assumption. THE ALTERNATIVE The alternative presented in the talk reframes delegation entirely. Instead of giving authority, you give capability. With Two-Party Computation (2PC), a private key can be split into shares. The agent never holds the full key. It receives scoped permissions: time-bound, policy-defined, function-specific. It can execute within constraints. It cannot take over. That difference is subtle, but it's foundational. Delegation does not have to mean surrendering custody. The next step is anchoring those permissions onchain. Key derivation and policies can be written into protocol-level logic through threshold networks like Human Network, previously Mishti Network, rather than relying purely on offchain safeguards. Using Ika「🦑」 within the Sui ecosystem, keys can be generated across different elliptic curves, enabling a single account to operate across Ethereum, Solana, and other chains without fragmenting custody. We're doing it with WaaP, Wallet as a Protocol, the first decentralized seedless wallet on Sui, also operating on EVM chains. “One Account, Every Chain” is not only about asset interoperability. It’s about unified control across chains, without collapsing back into centralized trust. This is not an anti-AI argument. Agents will automate, trade, coordinate. The question is whether humans remain sovereign in the process. If we're serious about an agent economy, the architecture has to reflect that. Agents should execute. Humans should retain authority. Interoperability is powerful. Automation is powerful. But if we don’t redesign how keys and permissions work, we rebuild the same fragilities crypto was meant to escape. The question lingers long after the talk ends: Would you trust an AI agent with your private key?
7:47

At HSC Asset Management in Hong Kong, hosted by Mpost Media Group, our co-founder S El Damaty gave a keynote titled “One Account, Every Chain.” On the surface, it’s about interoperability. Underneath, it’s about something even more fundamental: Would you trust an AI agent with your private key? --- Not theoretically. Practically. Would you give full signing authority to software running locally or in the cloud, knowing it can move assets, execute trades, deploy capital, or spin up new transactions on your behalf? IT'S ALREADY HAPPENING As you're reading this post, people are already doing it. Agents are being embedded into wallets, trading systems, and productivity tools. It's the new narrative: software is automating everything. Finance is next. But crypto, since Bitcoin, was built around self-custody. “Not your keys, not your coins” wasn’t marketing. It was architecture. If you hand an agent your full private key, you have reintroduced a custodian. It may look like automation. But structurally, it’s concentration of authority. Right now, most implementations fall into two models. Either the agent gets full control, or it runs inside trusted infrastructure like AWS Nitro. Both approaches shift trust somewhere else. Either into the agent itself, or into centralized compute providers sitting underneath the system. If the future economy runs on agents, that becomes a very large assumption. THE ALTERNATIVE The alternative presented in the talk reframes delegation entirely. Instead of giving authority, you give capability. With Two-Party Computation (2PC), a private key can be split into shares. The agent never holds the full key. It receives scoped permissions: time-bound, policy-defined, function-specific. It can execute within constraints. It cannot take over. That difference is subtle, but it's foundational. Delegation does not have to mean surrendering custody. The next step is anchoring those permissions onchain. Key derivation and policies can be written into protocol-level logic through threshold networks like Human Network, previously Mishti Network, rather than relying purely on offchain safeguards. Using Ika「🦑」 within the Sui ecosystem, keys can be generated across different elliptic curves, enabling a single account to operate across Ethereum, Solana, and other chains without fragmenting custody. We're doing it with WaaP, Wallet as a Protocol, the first decentralized seedless wallet on Sui, also operating on EVM chains. “One Account, Every Chain” is not only about asset interoperability. It’s about unified control across chains, without collapsing back into centralized trust. This is not an anti-AI argument. Agents will automate, trade, coordinate. The question is whether humans remain sovereign in the process. If we're serious about an agent economy, the architecture has to reflect that. Agents should execute. Humans should retain authority. Interoperability is powerful. Automation is powerful. But if we don’t redesign how keys and permissions work, we rebuild the same fragilities crypto was meant to escape. The question lingers long after the talk ends: Would you trust an AI agent with your private key?

human.tech

13,552 просмотров • 6 месяцев назад

So far, machine payments have mostly been about businesses accepting stablecoins. And stablecoins are great (cross-border, low cost, etc.)! But much of the planet is holding a card. 🤖 💳 🌎 Here’s a 📺 sneak peek demo from Steve Kaliski of how a business can programmatically accept cards via agents. As an example: Stripe Climate is a way to contribute to carbon removal funding. Stripe Climate implemented the Machine Payments Protocol using the Stripe API, so agents can make micropayment donations ( In addition to accepting stablecoin (specifically usdc on Tempo), agents can now pay with fiat methods, namely cards and Link (and soon buy-now-pay-laters) via Shared Payment Tokens (SPTs), using the same Machine Payments Protocol integration. Human buyers, their agents, and businesses each have their own preferred methods of payment. Humans often already have a card. Agents may prefer stablecoins. Businesses tend to want to accept any form of payment, as long as it is high conversion, low fraud, and properly priced. For microtransactions, stablecoins are a low-cost way (no fixed card fee) to transact. But if you want to tell your agent to donate $100 on your behalf, a card may be the preferred solution. If you’re a business and want to accept machine payments, whether over stablecoins, cards, Link, or other future methods, read about Shared Payment Tokens ( and sign up for our machine payments private preview: And stay tuned: more to make it easy for consumers, agents, and businesses to transact, shipping over the next few weeks. (And excuse the acronyms and specifics terms, there's a lot of new infrastructure and primitives being built to support agentic commerce.)
2:00

So far, machine payments have mostly been about businesses accepting stablecoins. And stablecoins are great (cross-border, low cost, etc.)! But much of the planet is holding a card. 🤖 💳 🌎 Here’s a 📺 sneak peek demo from Steve Kaliski of how a business can programmatically accept cards via agents. As an example: Stripe Climate is a way to contribute to carbon removal funding. Stripe Climate implemented the Machine Payments Protocol using the Stripe API, so agents can make micropayment donations ( In addition to accepting stablecoin (specifically usdc on Tempo), agents can now pay with fiat methods, namely cards and Link (and soon buy-now-pay-laters) via Shared Payment Tokens (SPTs), using the same Machine Payments Protocol integration. Human buyers, their agents, and businesses each have their own preferred methods of payment. Humans often already have a card. Agents may prefer stablecoins. Businesses tend to want to accept any form of payment, as long as it is high conversion, low fraud, and properly priced. For microtransactions, stablecoins are a low-cost way (no fixed card fee) to transact. But if you want to tell your agent to donate $100 on your behalf, a card may be the preferred solution. If you’re a business and want to accept machine payments, whether over stablecoins, cards, Link, or other future methods, read about Shared Payment Tokens ( and sign up for our machine payments private preview: And stay tuned: more to make it easy for consumers, agents, and businesses to transact, shipping over the next few weeks. (And excuse the acronyms and specifics terms, there's a lot of new infrastructure and primitives being built to support agentic commerce.)

Jeff Weinstein

21,635 просмотров • 4 месяцев назад

𝗠𝗼𝘀𝘁 𝗽𝗲𝗼𝗽𝗹𝗲 𝗱𝗼𝗻’𝘁 𝗹𝗼𝘀𝗲 𝗻𝗲𝗴𝗼𝘁𝗶𝗮𝘁𝗶𝗼𝗻𝘀 𝗯𝗲𝗰𝗮𝘂𝘀𝗲 𝘁𝗵𝗲𝘆 𝗹𝗮𝗰𝗸 𝗹𝗲𝘃𝗲𝗿𝗮𝗴𝗲. They lose because they don’t know what number to counter with, what terms to protect, or when to hold firm. I built an AI agent that fixes that. 𝗡𝗲𝗴𝗼𝘁𝗶𝗮𝘁𝗶𝗼𝗻 𝗣𝗿𝗼𝘅𝘆, My submission for the #OKXAI Genesis Hackathon. It’s not a generic chatbot. It’s a negotiation agent for real money conversations: freelance deals, vendor quotes, invoice settlements, car purchases, anywhere people bleed value because they don’t know what to say next. 𝗛𝗼𝘄 𝗶𝘁 𝘄𝗼𝗿𝗸𝘀: You paste the negotiation context. Set your target price, your walk-away point, and optional guardrails, deposit, payment window, delivery date, revision cap, dealbreakers. Negotiation Proxy hands you back a recommended counter-offer, a one-line rationale, a ready-to-send draft message, a confidence score, and multiple postures to choose from, aggressive, balanced, or close-now. Every round gets logged into a negotiation ledger. Paste the other side’s reply, rerun the analysis, keep negotiating round by round. It’s a repeatable deal desk, not a one-shot prompt you run once and forget. 𝗪𝗵𝘆 𝘁𝗵𝗶𝘀 𝗳𝗶𝘁𝘀 𝗢𝗞𝗫.𝗔𝗜: For Agent-to-MCP, there’s a negotiate_counter_offer tool spec — a pay-per-call negotiation round service. For Agent-to-Agent, two agents can exchange offers and narrow price and scope autonomously, then stop for final human sign-off before anything binding happens. That’s the core idea I’m bringing to agents shouldn’t just answer questions. They should be able to handle real commercial negotiation workflows. Once both sides land in a settlement envelope, the user approves it, and the deal moves into escrow-backed payment, settled in stablecoins like USDT or USDG via Onchain OS. Negotiation logic + OKX marketplace and discovery + onchain settlement. That combination is what makes this useful for crypto and non-crypto deals alike, the negotiation problem is universal, OKX’s stack just adds the trust and rails. Already a working build, not a mockup: Next.js app with a full negotiation workspace, persistent ledger, reviewer links, export flow, MCP tool contract, and an agent-to-agent negotiation stub. Try it → #OKXAI #OKXAIGenesisHackathon
1:23

𝗠𝗼𝘀𝘁 𝗽𝗲𝗼𝗽𝗹𝗲 𝗱𝗼𝗻’𝘁 𝗹𝗼𝘀𝗲 𝗻𝗲𝗴𝗼𝘁𝗶𝗮𝘁𝗶𝗼𝗻𝘀 𝗯𝗲𝗰𝗮𝘂𝘀𝗲 𝘁𝗵𝗲𝘆 𝗹𝗮𝗰𝗸 𝗹𝗲𝘃𝗲𝗿𝗮𝗴𝗲. They lose because they don’t know what number to counter with, what terms to protect, or when to hold firm. I built an AI agent that fixes that. 𝗡𝗲𝗴𝗼𝘁𝗶𝗮𝘁𝗶𝗼𝗻 𝗣𝗿𝗼𝘅𝘆, My submission for the #OKXAI Genesis Hackathon. It’s not a generic chatbot. It’s a negotiation agent for real money conversations: freelance deals, vendor quotes, invoice settlements, car purchases, anywhere people bleed value because they don’t know what to say next. 𝗛𝗼𝘄 𝗶𝘁 𝘄𝗼𝗿𝗸𝘀: You paste the negotiation context. Set your target price, your walk-away point, and optional guardrails, deposit, payment window, delivery date, revision cap, dealbreakers. Negotiation Proxy hands you back a recommended counter-offer, a one-line rationale, a ready-to-send draft message, a confidence score, and multiple postures to choose from, aggressive, balanced, or close-now. Every round gets logged into a negotiation ledger. Paste the other side’s reply, rerun the analysis, keep negotiating round by round. It’s a repeatable deal desk, not a one-shot prompt you run once and forget. 𝗪𝗵𝘆 𝘁𝗵𝗶𝘀 𝗳𝗶𝘁𝘀 𝗢𝗞𝗫.𝗔𝗜: For Agent-to-MCP, there’s a negotiate_counter_offer tool spec — a pay-per-call negotiation round service. For Agent-to-Agent, two agents can exchange offers and narrow price and scope autonomously, then stop for final human sign-off before anything binding happens. That’s the core idea I’m bringing to agents shouldn’t just answer questions. They should be able to handle real commercial negotiation workflows. Once both sides land in a settlement envelope, the user approves it, and the deal moves into escrow-backed payment, settled in stablecoins like USDT or USDG via Onchain OS. Negotiation logic + OKX marketplace and discovery + onchain settlement. That combination is what makes this useful for crypto and non-crypto deals alike, the negotiation problem is universal, OKX’s stack just adds the trust and rails. Already a working build, not a mockup: Next.js app with a full negotiation workspace, persistent ledger, reviewer links, export flow, MCP tool contract, and an agent-to-agent negotiation stub. Try it → #OKXAI #OKXAIGenesisHackathon

Hallie Carter

48,695 просмотров • 1 месяц назад