Systems | Development | Analytics | API | Testing

How to set up Billing for AI Agents with LangChain and Kong in 15 Minutes | Monetize AI Agents

Want to bill customers for the AI tokens they actually use? This video shows you how to set up a LangChain app that meters LLM token usage and streams it to Kong Konnect Metering & Billing as CloudEvents — turning every prompt and response into invoiced usage, automatically.

Monitoring, Audit Trails, and Compliance with ClearML

The previous posts in this series built the security model layer by layer: identity, configuration governance, service account automation, compute policies, and production model serving. This final post covers what holds all of it together: the monitoring and audit layer that records every action, every API call, and every resource event and makes the full picture visible to the people responsible for it. It accompanies our Enterprise AI Infrastructure Security YouTube series.

How Wix's AI Agents Stay Ahead of the Rest | Life Is But A Stream

Real-time data and AI are converging—and companies that have already solved the data pipeline problem are pulling ahead fast. Wix processes over 40 billion interactions every day across hundreds of millions of websites, and the architecture behind that scale didn't happen by accident. It was built, lane by lane, around the principle that your upstream data must be at least as fast as your fastest use case.

Playwright Test Agents & MCP: A 2026 Architecture Guide

Playwright test agents are LLM-driven execution loops that wrap Playwright's browser automation in a goal-oriented reasoning layer. Instead of executing pre-written scripts, an agent receives high-level intent ("complete checkout and verify the success modal"), inspects the page's accessibility tree, and chooses which Playwright tool to invoke next. The Model Context Protocol (MCP) is the standardized bridge that exposes Playwright capabilities to the LLM and returns structured page context back.

Snowflake Semantic Views + ThoughtSpot: One AI Context Layer

Your data engineers have spent months getting your metric definitions right: revenue recognized the way finance approved it, churn calculated the way your exec team aligned on it, and pipeline logic that your rev ops team actually agrees on. And then a new tool arrives, and someone has to do it all again.

What one performance engineering leader would tell industry newcomers who are worried about AI

Quick summary: AI is creating anxiety and excitement — teams can get more work done faster, but does all this automation leave the worker behind? Not necessarily, says one performance engineering leader. The AI revolution, he says, is another technological wave. To ride it, performance engineers must embrace the change.

Why Your AI Strategy is Breaking: The Power of AI Anywhere with Cloudera

Hey, did you know AI can’t be confined to just one environment? AI is moving faster than ever, but it cannot be confined to a single environment. From the public cloud to on-prem data centers and out to the edge, AI is everywhere. However, when these environments remain siloed, your data strategy breaks—leading to inconsistent governance and scaling roadblocks. In this video, discover the vision of AI Anywhere. To unlock real business value, AI must operate exactly where your data lives, maintaining the same level of control, trust, and security across every platform.

Lenses MCP Server with OAuth 2.1

You can now drive Lenses from Cursor, VS Code, IBM Bob or Claude Code without running any extra piece of infrastructure locally. Lenses MCP offers secure tools across topics, schemas, Kafka Connect, SQL processors, consumer groups, datasets and pod logs: everything an engineer would normally click through in the Lenses UI, now reachable from any MCP-compatible client over HTTP.

Introducing Kafka Skills for AI Engineering Agents

If you've written a line of code in the last 18 months, you already know this. Tools like Claude, Codex, Bob, Kiro and Cursor have made agentic software engineering the default. Most developers today are writing prompts as much as they are writing code. That shift changes what ‘developer experience’ means. Clean UIs, useful tools and good docs are still the foundation but the focus has shifted to ensuring a coding agent actually knows what it is doing, in the hands of a developer.