AWS gives coding agents a safer way into cloud accounts

What changed: AWS’s managed Model Context Protocol server is now generally available, according to InfoQ, giving coding agents a standard way to reach AWS APIs, documentation, and operational workflows with IAM-based access controls, CloudWatch metrics, and CloudTrail logging. InfoQ also notes support for all AWS APIs, long-running operations, file uploads, and sandboxed Python execution for multi-step work.

Why it matters: If your team lets AI write infrastructure code, this is a more controlled path than pasting cloud credentials into a local agent setup. Builders can give agents current AWS documentation and limited action rights, while security teams get a clearer audit trail.

Try/watch: Start with read-only access and one low-risk workflow, such as checking deployment errors or drafting infrastructure changes. Do not let agents create, delete, or resize production resources until you have approval rules and cost limits in place.

Kore.ai launches Artemis for governed enterprise agent systems

What changed: Kore.ai launched the Artemis edition of its Agent Platform, initially on Microsoft Azure, to build, govern, and optimize multi-agent business workflows. The platform includes Agent Blueprint Language for defining agent behavior, Arch for turning business goals into agent blueprints, and a dual approach that combines AI reasoning with more predictable workflow rules.

Why it matters: This is aimed at companies that are past chatbot pilots and need repeatable, reviewable agent deployments across departments. For buyers, the important question is not whether the demo looks smart, but whether every agent action can be traced, constrained, and approved before it affects a customer, employee, or financial system.

Try/watch: Ask for a proof of concept that shows the full audit trail for one real workflow, such as customer support escalation or invoice exception handling. Make the vendor prove how the system stops an agent from taking an action outside policy.

Agent payments are becoming a real infrastructure category

What changed: CoinDesk reported that AI agents settled more than $73 million across roughly 176 million blockchain transactions over the past year, citing a Keyrock report, while Coinbase, Stripe, Google, and Visa are building competing machine-to-machine payment systems. The article says many agent payments are tiny purchases for things like data, computing, or AI-generated analysis, with 76% of transactions below the 30-cent fixed-fee floor common in card payments.

Why it matters: For founders building agent marketplaces, API products, or autonomous procurement tools, payments may become part of the product design, not a back-office detail. The practical issue is authorization: who allowed the agent to spend, how much, for what purpose, and how refunds or disputes work.

Try/watch: If you are experimenting with agent payments, use strict spending caps, per-task approvals, and vendor allowlists. Avoid building around one payment rail until liability, identity, and chargeback rules are clearer.