A performance marketing platform with paying advertisers asked us to make their product operable by AI agents. We delivered the foundation in six weeks, the MCP service twelve weeks later, and the client's CTO now ships production code through his own AI harness inside gates we built. I want to walk through how, because "AI-enabled adtech" is on every deck in the category and almost none of it means an agent can operate the platform. Their codebase had real advertisers, real offer configurations, and real money moving through conversion data. This is brownfield, not a weekend prototype demo. February and March, we didn't touch AI. We built the foundation the agents would need: versioned management APIs, a dedicated API key type with its own authorization gating, an SDK surface, published Swagger docs. Teams skip this constantly. They wire a model to the UI endpoints, the payloads are ten times too large for an agent's context, the first write corrupts a live offer, and the pilot dies. I've seen it across 100+ engagements. When someone says "our platform isn't ready for agents," they almost always skipped the API surface. June 9, the MCP service went live. Tenant-scoped, read-only by design. Offer listings, change logs, performance summaries, conversion data. An early user couldn't damage a live configuration because there was nothing to damage with. July 1, the first write tools: pause, share, clone an offer, update a conversion status. July 9, the second wave: update offers, resume paused ones, create ad-hoc conversions for integrators. The endpoints were purpose-built for language models. Narrow summary calls, current-date context injected for month-only queries, response-size caps, latency work. Large payloads break agent workflows, so the surface was designed around the agent rather than reused from the UI. Their CTO ships production code himself, through his own AI agent harness. We own the API surface, the architecture, code review, QA and release. Same repository, same board, same branching strategy, same quality gates, with guardrails enforced at GitHub level. April 14 was the first production delivery from that workflow: a query optimisation where the agent validated its own work by diffing old and new SQL against production data, row for row. The release count came from three things: automated AI review on every pull request since January, tests scoped from the PR diff with the bulk of new test code generated, and a documentation set of around 70 system documents kept in the repository so it doubles as context for the agents. Behind it, this engagement is one of the first two pilots for Velocity Core, our own agentic delivery system. A ticket status change fires a webhook, an isolated agent plans, executes, runs CI and opens a PR for human review. When CI fails, the failure and the developer's fix are recorded and served back to future runs. Alpha, tested on real tickets, with the client's CTO inside the loop. Their CEO connected his own AI assistant to the platform. As far as we know, very few platforms in performance marketing can say that today. That's what our Velocity Framework was built for.