Coinbase

Binance launches Agent OS for AI agent trading

Binance launched Agent OS, a platform that allows AI agents to analyze markets and execute trades on users’ behalf by connecting developer-built agents to Binance’s financial infrastructure. Agent OS integrates with Binance APIs, its Agentic Wallet, x402 payments, and the Model Context Protocol (MCP), and supports tools such as OpenAI and Anthropic models. Binance uses configurable sub-accounts to sandbox agents, blocks withdrawals by default, and lets users choose whether agents require approval for each order. Binance does not impose a separate trading cap on sub-accounts (user-deposited funds act as limits), while Agentic Wallet and payments carry company-set daily limits. Rival exchanges including Kraken, Coinbase and OKX have launched similar agent-access tools.

Kraken affiliate launches cashback debit card

Kraken’s payments app affiliate, Krak, has launched the Krak Card, a U.S. debit card that offers up to 2% back in cash or bitcoin and lets customers spend from more than 600 fiat currencies and crypto assets. Rewards are paid as money rather than points and the cashback rate can increase based on the value of assets a user holds. The card is issued through a partner bank subject to U.S. debit interchange limits. Kraken — founded in 2011 and owned by parent Payward — is using the product to retain deposits, drive spending and deepen customer asset holdings; the company also has a Wyoming bank charter and secured a Federal Reserve master account earlier in 2026. CNBC published the report on August 18, 2026.

x402: HTTP-Native Payments Let AI Agents Pay APIs

The x402 protocol is an open, HTTP-native payment standard (built on HTTP 402 Payment Required) that enables software — including autonomous AI agents — to pay for APIs and digital resources directly at the HTTP request/response layer. Created by Coinbase and governed by the x402 Foundation, x402 typically uses stablecoins such as USDC for on-chain settlement and relies on a three-party flow involving a client, a resource server, and a facilitator that verifies payment proofs. The protocol supports multiple chains (Base, Ethereum, Polygon, Arbitrum, Solana) and aims to replace account- and API-key-based billing with per-request, wallet-backed payments. The article discusses implementation trade-offs, security risks (wallet custody, replay protection, metadata exposure), compliance questions (KYC/AML, accountability), and implications for API monetization and machine-to-machine commerce.