Amazon Bedrock's AgentCore Payments service is now generally available, allowing AI agents to autonomously pay for APIs, content, and services using integrated Coinbase and Stripe wallets. The service supports multiple payment protocols including x402 and Machine Payment Protocol, with configurable spending limits and comprehensive audit logging. Enterprises can now deploy agents that handle transactions independently while maintaining security controls and cost visibility across production workloads.
Jumio built a real-time feature store on AWS using Kinesis, Flink, and SageMaker Feature Store to serve fraud detection models with sub-100ms latency. The system achieves 16.9ms at the 95th percentile and processes events through a streaming-first pipeline with tiered storage combining in-memory and standard stores. This centralized approach replaced fragmented team-based feature engineering and saved approximately $120,000 in annual operational costs.
Axonius, a SaaS asset intelligence platform, deployed AI agents on Amazon Bedrock AgentCore using a dedicated-runtime-per-tenant silo model to maintain tenant isolation, integrate with existing authentication systems, and track costs per customer. Each tenant runs a separate agent instance with isolated microVMs, IAM-based access control, and shared knowledge bases with metadata filtering. The architecture enables junior analysts to run complex risk analyses without senior analyst involvement, while maintaining security through infrastructure-level enforcement, cost tracking via CloudWatch token metrics, and integration with Axonius's existing VPC-isolated customer environments.
Every AI story that matters,
in your inbox by 8am.
TLDRocket reads all relevant sources, removes duplicate coverage, and summarises the
day in two minutes. Follow companies and topics for alerts, or get the
briefing in Slack. Free, no spam, unsubscribe anytime.
Reading TLDRocket needs no cookies, and the readership counts we rely on come from
our own cookieless analytics. Google Analytics is the exception: it sets cookies and
reports to Google, so it stays switched off until you allow it. You can change your
mind any time from “Cookie settings” in the footer.
Strictly necessary
Session security and form protection (tldrocket-session,
XSRF-TOKEN, 2 hours). The site cannot work without them,
so they need no consent.
Always on
Google Analytics 4 (_ga,
_ga_<id>, up to 2 years). Measures which
stories and sections readers use. Google acts as a third-party processor and may
store the data outside the EU. No advertising, no profiling, no data sold.
