Systems | Development | Analytics | API | Testing

We’ve been building an AI agent that can take a production bug, find the root cause in captured traffic, write a fix, and validate it before a human reviews it. We call it Agent Factory. Last week we ran it on ourselves, against a real bug in our own production service. The first thing we did was get the workflow wrong.

This is Part 2 of the AI Software Factory series. In Part 1, we established that the Agile methodology is buckling under the weight of “elastic code.” When AI agents can generate functionality in seconds, two-week sprints and manual task management become organizational bottlenecks. We introduced the concept of the AI Software Factory: a shift from managing human tasks to managing business intent through a “Funnel of Increasing Trust.” But a factory requires infrastructure.

While AI accelerates development velocity by a factor of ten, a critical consequence remains: testing hasn’t kept pace. According to SmartBear research, 70% of software professionals report that their application quality has already degraded due to AI-accelerated development. Even more concerning, 60% have experienced quality issues in the past year as development velocity outstrips testing capacity.

In an API-driven setup, a gateway often sits between clients and backend services: it can validate input, aggregate upstream responses, and give you one place to observe traffic. Koa is a strong fit for that role. Its core stays small, async/await is first-class, and middleware composes in a predictable stack. In this article, you will build a compact API gateway with Koa that: You will also wire up AppSignal for the Node.js stack.

Credit used to be a destination. You went to a bank, filled out forms, waited days, sometimes weeks, and hoped for approval. That model is quietly disappearing. Today, credit shows up exactly where you need it. While shopping online. While booking logistics. Even while managing business cash flow inside a SaaS dashboard. No redirects. No friction. No traditional loan journey. This shift is what we call Embedded Lending. It is not just a feature.

A guide to learning how MCP registries help govern AI agent-to-tool connectivity AI agents are only as capable as the tools they can reach. When an agent needs to query a database, file a support ticket, or pull data from a CRM, it has to find the right tool, authenticate, and invoke it — all at runtime. The Model Context Protocol (MCP) standardizes how agents communicate with these tools. But MCP alone does not answer a fundamental question: how does the agent know which tools exist?