--- title: "Market Pulse" canonical: "https://current.tinyfish.ai/issue/34/market-pulse" publication: "TinyFish" publisher: "TinyFish" language: "en-US" guide: "https://current.tinyfish.ai/llms.txt" permalink: "https://current.tinyfish.ai/issue/34/market-pulse" issue: 34 section: "market-pulse" description: "Reading the agent ecosystem through a practitioner's lens" authors: ["Nora Kaplan","Rina Takahashi"] published: 2026-06-22 updated: 2026-06-19 articles: 21 --- # TinyFish > CURRENT is a journal about AI agents in production, for the engineering and product leaders who have to make them work. Drawing on experience building enterprise web agents, it explains why the demo succeeded and the deployment didn't, and what that means for choosing vendors, briefing the board, and avoiding mistakes others have already made. [Read on the website]() ## Issue 34 — Market Pulse Reading the agent ecosystem through a practitioner's lens ### Governance Gap - [What Governance Governs]() — By [Nora Kaplan]() · Published 2026-06-18 · Format: Governance Gap Companies with governance tooling deploy twelve times more AI projects to production. Only 4 of 13 frontier-autonomy agents disclose safety evaluations for agentic deployment. The first figure tells you whether a system has been authorized to run. The second tells you whether anyone has rigorously checked what it does once running. They share a vocabulary. They measure fundamentally different things. And the infrastructure accumulating around the first may be quietly relieving pressure to build the second. ### Ecosystem Snapshot Consolidation is outpacing the conversation about it. Protocols are shedding statefulness. Competing frameworks are merging under shared foundations. Platforms are wiring billing meters into workloads that had no price signal six months ago. The thread running through this week: infrastructure is being rebuilt for agents that run without someone pressing enter. Scheduled execution, stateless servers, supervisor architectures, portable governance specs. The plumbing is catching up to the ambition. Whether the economics can keep pace is a question at least one company just postponed answering. - **MCP Release Candidate Drops State, Adds Governance** — [Source]() — Published 2026-06-18 Tag: Protocol Layer The 2026-07-28 RC, locked since May 21, strips out the initialize handshake and session pinning entirely. Remote MCP servers can now sit behind ordinary load balancers. OAuth 2.1 hardening, an Extensions framework, and Server Cards round out the release. Breaking changes from the current stable spec (still 2025-11-25). Final ship targeted for July 28. - **Microsoft Build Rewires the Stack Around Agents** — [Source]() — Published 2026-06-18 Tag: Platform Strategy The Build keynote introduced Microsoft IQ, folding Work, Foundry, Fabric, and a new Web IQ into a single intelligence layer with live web grounding. Agent Framework 1.0 hit GA. Copilot Credits become the consumption meter for agent workloads. Agent Control Specification previews portable governance policies across the platform. - **Anthropic Pulls Back Agent Billing Split at Launch** — [Source]() — Published 2026-06-18 Tag: Pricing Economics The June 15 plan to move Agent SDK, claude -p, and third-party agents onto separate metered credit pools at API rates did not take effect as scheduled. Anthropic told users "nothing changes for now," citing the need to better align with usage patterns. The gap between interactive and programmatic pricing remains open. - **Agent Frameworks Merge Faster Than Anyone Expected** — [Source]() — Published 2026-06-18 Tag: Framework Consolidation Microsoft Agent Framework 1.0 ships GA, folding AutoGen and Semantic Kernel into one surface. IBM's ACP merges into A2A under the Linux Foundation's Agentic AI Foundation. Google releases ADK 1.0 for Java and Go. MCP crosses 97 million monthly SDK downloads. The standards layer is solidifying quickly. - **Claude Ships Scheduled Agents, Vaults, and Nesting** — [Source]() — Published 2026-06-18 Tag: Managed Agents Public beta brings cron-based scheduling and vault-stored environment variables to Claude's managed agents, targeting the operational plumbing that keeps agent projects stuck in pilot. Sub-agent nesting now goes five levels deep. A searchable plugin marketplace rounds out the release. - **Databricks Telemetry Shows Multi-Agent Workflows Surging** — [Source]() — Published 2026-06-18 Tag: Adoption Data Platform data from 20,000 organizations (60% of the Fortune 500) shows 327% growth in multi-agent workflows over four months in 2025. More than a third of agent usage now follows supervisor patterns, with a central agent delegating sub-tasks to specialized sub-agents. Worth noting: this is Databricks customer data, not an independent survey. ### Research Digest - **The 2025 AI Agent Index: Documenting Technical and Safety Features of Deployed Agentic AI Systems** — [Source]() — Published 2026-06-18 Researchers from nine institutions catalogued what 30 deployed AI agents actually disclose about safety versus capability. The gap is stark: of 13 agents operating at frontier autonomy levels, only 4 share agentic safety evaluations. Capability benchmarks get published; safety documentation often doesn't. Who's behind it? Cambridge, MIT, Harvard Law, Stanford, and five other institutions. Presented at ACM FAccT '26 in Montreal, June 25–28. Where does autonomy drift? Enterprise agents designed for Level 1–2 autonomy regularly deploy at Level 3–5. Prompt injection vulnerabilities appear in 2 of 5 browser agents studied. - **TrajAD: Trajectory Anomaly Detection for Trustworthy LLM Agents** — [Source]() — Published 2026-06-18 A dedicated runtime verifier that audits agent execution step by step, pinpointing where trajectories go wrong so systems can roll back precisely rather than restart entirely. General-purpose LLMs, even with careful prompting, perform poorly at this task, which suggests process supervision needs its own tooling. What shifts here? Agent safety moves from static input/output filtering to mid-execution trajectory auditing, catching failures as they unfold rather than after damage lands. Why does dedicated tooling matter? With 89% observability adoption but only 52% offline evaluation, confident-but-wrong agents slip through the gap that general monitoring leaves open. - **JADE: Expert-Grounded Dynamic Evaluation for Open-Ended Professional Tasks** — [Source]() — Published 2026-06-18 A two-layer evaluation framework from Alibaba, Zhejiang University, and Peking University. It breaks agent outputs into individual claims and checks each against expert knowledge, targeting professional domains where holistic scoring by LLM evaluators misses critical failures. What does claim-level decomposition catch? Evidence-dependency gating invalidates conclusions built on refuted claims, surfacing cascading errors that aggregate scores quietly absorb. Where could this apply? Legal analysis, medical reporting, complex underwriting. Domains where "correct" resists simple definition and evaluation itself requires domain expertise. - **Stanford HAI 2026 AI Index Report: Foundation Model Transparency** — [Source]() — Published 2026-06-18 Foundation Model Transparency Index scores fell from 58 to 40, reversing two years of improvement. The pattern: the most capable models now disclose the least. Documented AI incidents rose 55% year-over-year, reaching 362 in 2025. What's disappearing from public view? Google, Anthropic, and OpenAI stopped disclosing dataset sizes and training duration. Eighty of 95 notable 2025 models shipped without training code. How much of the decline is structural? The index penalizes closed-source models, and the most capable models are increasingly closed-source, which may inflate the apparent transparency retreat. ### Pricing Signal - [When the Meter Starts Running]() — By [Rina Takahashi]() · Published 2026-06-18 Anthropic [announced](https://www.techtimes.com/articles/317625/20260602/anthropic-ends-subscription-subsidy-agents-june-15-credit-pool-replaces-flat-rate-access.htm) a billing split in May separating agent workloads from subscription pools into metered credits. The change was [paused](https://www.digitalapplied.com/blog/anthropic-claude-credit-overhaul-june-15-2026) before its June 15 go-live, but the logic is visible elsewhere: GitHub Copilot shifted to [usage-based AI Credits](https://windowsforum.com/threads/github-copilot-ai-credits-usage-based-billing-starts-june-1-2026.415470/) on June 1, and one agentic coding session now costs [$30–40](https://www.abhs.in/blog/github-copilot-usage-based-billing-ai-credits-cost-developer-teams-june-2026). ### Further Reading - **The 2025 AI Agent Index** — [Source]() — Published 2026-06-18 Catalogues 30 deployed agents and finds capability disclosures vastly outnumber safety evaluations, quantifying the specification gap in practice. - **MCP Is Growing Up** — [Source]() — Published 2026-06-18 The maintainers explain why MCP went stateless and what the extensions framework changes for authorization. Best primary source on the protocol's direction. - **State of Agent Engineering** — [Source]() — Published 2026-06-18 1,300 practitioners confirm the pattern: 89% trace agent behavior, but only 52% evaluate whether outputs are actually correct. The gap is structural. - **Databricks Report: 327% Surge in Enterprise AI Systems** — [Source]() — Published 2026-06-18 Telemetry across 20,000 organizations showing supervisor-agent patterns now dominate, and the 12x governance-to-deployment correlation worth scrutinizing. - **MCP Protocol Updates 2026: The Migration Map** — [Source]() — Published 2026-06-18 Practical changelog for the July 28 RC. Useful for teams running remote MCP servers who need to know exactly what breaks. ### Past Articles - [The Test Suite Was the Hero]() — By [Nora Kaplan]() · Published 2026-06-12 · Format: Verification at Scale Anthropic's Dynamic Workflows can now orchestrate a thousand subagents in parallel. The showcase was a Bun runtime port: 750,000 lines of Zig to Rust, 99.8% test pass rate, eleven days. Impressive. But research on Claude's failure patterns finds that 71% of failures are consistent misinterpretation, not random error. A thousand agents inheriting the same flawed specification converge, confidently, on the same wrong answer. The Bun port had a deterministic test suite to catch that. Most enterprise domains don't. - [What the Bill Can't Measure]() — By [Rina Takahashi]() · Published 2026-06-03 · Format: The Meter Drops GitHub Copilot moved to metered billing on June 1, and organizations can finally see where their AI development spend is going. That's a real step forward. The natural parallel is cloud FinOps, which saved billions by making waste visible. An idle VM is idle, and the bill reflects it. A confident, systematically wrong code suggestion consumes exactly the same credits as a correct one. Cost now has real infrastructure behind it, so organizations will build discipline around consumption. Consumption, meanwhile, has no reliable relationship to correctness. - [The Data Perimeter Split Both Architectures in Half]() — By [Rina Takahashi]() · Published 2026-05-27 · Format: The Perimeter Problem Last week, Anthropic and OpenAI both responded to the same brute constraint: regulated enterprise data cannot leave the building. Each vendor split the agent to accommodate that boundary. Anthropic moved tool execution inside the customer perimeter but kept the reasoning loop on its own infrastructure. OpenAI announced an on-premises partnership with Dell without specifying where inference actually runs. Neither architecture co-locates governance with the consequential decisions. When something goes wrong, the person who needs to intervene can kill the connection but has no way to inspect or redirect the reasoning that got there. - [What a Required Field Knew]() — By [Rina Takahashi]() · Published 2026-05-20 · Format: The Headless Shift A validation rule in Salesforce fires when a rep moves a deal to "Closed Lost" — won't save without a reason. Nobody calls that governance. It's just how the system works. But as enterprise software goes headless so agents can bypass the UI entirely, that quiet enforcement starts to matter. The interface was encoding what "correct" looked like, thousands of times a day, often without documentation. Now that specification work has to live somewhere else. Most organizations haven't started figuring out where. ## Other sections in Issue 34 - [Daily Brief]() - [Foundations]() - [Practitioner's Corner]() - [Echoes]() - [Vision]() ## More - [Publication guide]() - [Issue archive]()