Systems | Development | Analytics | API | Testing

Everyone is talking about vibe coding—Claude Code, MCP, custom CLIs—using LLMs to turn intent into working logic. It’s fast. And if you aren’t leaning into it, you’re already behind. At Appian, we meet developers where they are. But speed alone doesn’t define success, and there’s a massive difference between a good workflow and a better one. Locking developers into one way of doing things is a losing strategy. That’s why we are releasing MCP and CLI tools.

DevOps has transformed how quickly software can be delivered, but speed alone does not guarantee resilience. As organizations scale, their systems become increasingly interconnected, with more services, more dependencies, and more edge cases that must be considered in every release. What once felt manageable with a handful of regression tests can quickly become opaque when dozens of teams are contributing to the same ecosystem1.

Schema validation ensures AI agents interact with APIs accurately by enforcing strict rules for requests and responses. OpenAPI provides a clear, machine-readable contract for APIs, reducing errors and improving reliability. This approach eliminates issues like ambiguous responses or schema drift, ensuring predictable behavior and secure data access.

The right question returns a deal name, an owner, and a dollar value. The wrong one returns a framework about pipeline health. The difference is not the model, it’s how you ask. It’s 7:47am Monday. Your pipeline review starts at 8. You have thirteen minutes to find out which deals need attention, which reps are behind pace, and whether you’re actually going to hit the number this quarter.

Part of the motivation for this post is how cloud API economics are shifting: Anthropic is moving large enterprise customers toward per-token, usage-based billing (unbundled from flat seat fees), which makes “always call the API” a moving cost line for teams at scale. A hybrid or local layer is one way to keep spend bounded while you still use premium models where they matter.

Scaling LLM and agentic AI adoption from pilot programs to enterprise-wide deployments is a massive logistical rollout. As AI and agentic usage grow, so does a nagging question for leadership: **Are agents using the right tools to get the job done?** While raw infrastructure metrics might tell you if a server is "up," they fail to tell you if your AI investment is being leveraged.

I spent years building dashboards that nobody used. Not because they were bad dashboards — they were actually pretty good. Clean visualizations, real-time data, all the metrics leadership said they wanted. But here’s what I learned: the problem was never the dashboard. The problem was the gap between seeing what happened and doing something about it. You look at a dashboard. It doesn’t act.