Amazon Bedrock AgentCore Payments: AI Agents Can Now Pay for APIs Autonomously
AWS released Amazon Bedrock AgentCore Payments in preview on May 11, 2026, enabling AI agents to autonomously pay for external APIs, MCP servers, web content, and other agents on behalf of their operators — a capability that addresses a friction point in multi-agent architectures where agents need to access paid services mid-workflow.
The feature integrates with Coinbase's CDP wallet infrastructure and Stripe Privy, allowing teams to attach a funding mechanism to an agent session. Developers set session-level spending limits when provisioning the agent, and AgentCore handles billing, credential management, and compliance automatically when the agent encounters a paid endpoint. The agent does not need hardcoded API keys for paid services — it presents credentials managed by AgentCore's identity layer.
The practical use case is agentic workflows that need to call specialized data providers, premium MCP tool servers, or even other agents-as-a-service. Today, this requires manual API key management, per-service billing agreements, and custom credential injection — all of which become overhead when building pipelines with dozens of tool dependencies. AgentCore Payments abstracts that plumbing so developers can focus on the workflow logic. AWS describes the feature as part of the Agent Toolkit for AWS, a production-ready suite replacing earlier MCP server and plugin approaches.
Read more — AWS News Blog
Amazon WorkSpaces Lets AI Agents Operate Legacy Desktop Applications Without APIs
AWS announced public preview of Amazon WorkSpaces for AI Agents in early May 2026, addressing a widely-cited blocker in enterprise AI adoption: 75% of organizations run legacy applications that lack modern APIs, making them effectively opaque to AI automation.
The feature provisions managed virtual desktops that AI agents can connect to via IAM-authenticated pre-signed URLs. Once connected, the agent interacts with the application through computer vision — capturing screenshots to understand UI state — and input simulation for clicking, typing, and scrolling. No modifications to the legacy application are required. The application remains completely unaware of the agent interaction, and the agent never touches the underlying application code or database directly.
This approach mirrors how a human remote desktop operator would work, making it broadly applicable: financial services firms can automate claims processing in mainframe-era back-office systems, healthcare organizations can handle data entry workflows, and any regulated industry can gain AI automation coverage without undertaking costly modernization projects. Security governance matches what IT teams already apply to human WorkSpaces sessions — IAM access controls, CloudTrail audit logging for all agent actions, and desktop-level session isolation. The feature is available in preview in major AWS regions including US East, US West, Europe, and Asia Pacific at no additional cost.
Read more — InfoQ
Google Workspace MCP Server Enters Public Developer Preview
Google released the Workspace MCP Server into public developer preview in early May 2026, making Gmail, Google Drive, and Google Calendar available as callable tools for any MCP-compatible AI agent.
The server exposes structured tool interfaces for each Workspace service: Gmail tools cover profile access, drafting, searching, and read/write email operations; Drive tools handle file fetching, permissions management, listing, and uploading; Calendar tools manage event scheduling, availability lookup, and event management. Any agent built with a framework that supports MCP — LangChain, LlamaIndex, CrewAI, Claude Code, or a custom implementation — can connect to these endpoints using standard tools/list and tools/call methods without custom authentication code.
The release lands alongside two related Apigee announcements: the Apigee MCP is now generally available, allowing developers to transform APIs defined by OpenAPI Specifications into AI-ready tools with managed endpoints and semantic search in API hub, and the API hub itself now exposes its own read-only APIs as MCP tools. Together, these moves indicate that Google's platform strategy around AI agents is converging on MCP as the standard interface layer — Google Workspace becomes a first-class data and action source for agents working within enterprise productivity workflows, and Apigee provides the governance layer for exposing any enterprise API through the same protocol.
Read more — Google Cloud Blog
