Build, discover, and monetize AI agents.

Google’s Agent2Agent protocol moves into a dedicated agent standards foundation

What changed: Google’s Agent2Agent (A2A) protocol for communication between independent AI agents is becoming a hosted project of the Agentic AI Foundation, the same specialist organization that stewards the Model Context Protocol. The foundation reports membership growth from fewer than 40 organizations at launch in December 2025 to more than 250, putting both A2A and MCP under a vendor-neutral umbrella.

Why it matters: Shared standards for how agents call each other and exchange context can shrink integration time and reduce brittle custom glue code in complex workflows. A neutral foundation gives buyers more leverage to demand interoperability across platforms instead of accepting one-vendor agent stacks.

Try/watch: For any new agent deployment, map which parts could align with A2A or MCP, and ask vendors explicitly how they plan to support open agent standards.

Zaptiva launches agentic AI services for autonomous digital workforces

What changed: Zaptiva introduced Agentic AI Development Services aimed at building autonomous AI agents that monitor enterprise activity, interpret information, make decisions, and execute multi-step processes across systems like ERP, CRM, EDI, spreadsheets, APIs, accounting tools, and legacy applications. These agents are designed to respond to changing conditions and escalate exceptions to humans when needed instead of following only fixed scripts.

Why it matters: This framing turns AI agents from sidecar tools into embedded digital coworkers that live inside existing workflows, which is where most enterprises can realize value fastest. It also reflects a shift from simple robotic process automation toward agents that handle messy, cross-system work with human oversight.

Try/watch: Start by identifying one cross-system process with frequent handoffs—such as order-to-cash or supplier onboarding—and scope a pilot where an agent monitors events and drafts actions that a human still approves.

RadarFirst adds an agentic layer for privacy and AI compliance work

What changed: RadarFirst announced an Agentic Layer that adds purpose-built AI agents on top of its privacy and AI governance platform. The agents handle tasks like guiding incident intake, identifying missing details, prioritizing higher-risk cases, organizing evidence, and drafting communications, while explicitly stopping short of making regulatory decisions.

Why it matters: Privacy and AI compliance teams are under pressure to move faster without missing regulatory obligations; delegating data gathering and triage to agents lets scarce experts stay focused on judgment calls. Keeping final decisions with humans also aligns with emerging human-in-the-loop regulatory expectations for high-risk AI systems.

Try/watch: If you run privacy or AI governance programs, treat agent layers as structured paralegal support: pilot them on intake and case prep first, then expand only once you trust their summaries and prioritization.

New rankings highlight which agent harnesses are ready for serious coding automation

What changed: CellCog’s August 2026 rankings of AI agent harnesses put Claude Code first for depth of hooks, subagents, and dynamic workflows, and as the default choice for long autonomous coding sessions. Codex CLI is highlighted for cloud-based, pull-request–shaped autonomy, while Cursor leads on in-editor agent workflows, with Gemini CLI and GitHub Copilot rounding out the top five options.

Why it matters: Teams that want agents to do real repository-level work need more than a chat box; they need runtimes that can manage long sessions, tool access, and multi-step plans without falling apart. Clear rankings help engineering leaders standardize on one or two harnesses instead of every developer improvising their own setup.

Try/watch: Pick one harness to standardize for serious automation and define guardrails—such as which repos agents can touch, budget limits per run, and review rules before agents merge code.

Cloudflare’s Kitesurf and x402 aim to make the web and payments more native to AI agents

What changed: An August 2026 roundup reports that Cloudflare launched Kitesurf, a browser runtime built for AI agents that runs on its Workers platform, uses roughly 3–7 times less CPU and memory than Chromium, and passes more than 235,000 web platform tests. Cloudflare also introduced the x402 protocol so agents can pay for services autonomously, with over 20 companies already participating in these agent-initiated payment flows.

Why it matters: Giving agents an efficient, production-grade browser runtime and a standardized way to pay vendors without human clicks makes autonomous digital coworkers far more practical. It also shifts risk and governance questions from individual scripts to shared infrastructure where logs, limits, and policies can be enforced centrally.

Try/watch: Before letting agents spend money or browse internal apps, define hard limits on spend per run, whitelisted merchants or apps, and require traceable logs so finance and security teams can audit agent behavior.