Agentic-Payments

The A2A (Agent-to-Agent) Protocol: How Agents Delegate to Each Other, and Where Payments Plug In

The A2A (Agent-to-Agent) Protocol: How Agents Delegate to Each Other, and Where Payments Plug In

A2A (Agent2Agent) standardizes how to delegate work to an independently operated agent and receive progress and results. A client reads an Agent Card for capabilities, endpoints and authentication requirements, then tracks longer work as a Task. MCP connects each agent to tools and data; separate protocols such as AP2 and x402 handle purchase authorization and payment settlement. Collaborating over A2A requires neither a blockchain nor a wallet. A2A specification, division of responsibilities with MCP

Read More
Apify x402 and Coinbase Wallets, in Depth: How Agents Buy Web Automation Tools Directly

Apify x402 and Coinbase Wallets, in Depth: How Agents Buy Web Automation Tools Directly

Apify, the web scraping platform, announced x402 support: AI agents can now run more than 20,000 Apify Actors by paying with USDC on Base, with no Apify account and no API key. Apify frames the prior x402 ecosystem as roughly 2,000 endpoints, so by its own count this integration expanded the paid-tool surface by about 10x.

Read More
Agentic Payments in June 2026: x402, UCP, and MPP Implementation Progress

Agentic Payments in June 2026: x402, UCP, and MPP Implementation Progress

Agentic payments in June 2026 moved from “can an agent pay” toward “who authorized the payment, how is it verified, and how is it traced.” The major open protocols (x402, UCP, MPP/pay.sh, and ACP) each had meaningful implementation changes. All figures and commit details below come from GitHub API, PyPI, and npm registry checks.

Read More
Categories
Tags