--- title: "Market Pulse" canonical: "https://current.tinyfish.ai/issue/35/market-pulse" publication: "TinyFish" publisher: "TinyFish" language: "en-US" guide: "https://current.tinyfish.ai/llms.txt" permalink: "https://current.tinyfish.ai/issue/35/market-pulse" issue: 35 section: "market-pulse" description: "Reading the agent ecosystem through a practitioner's lens" authors: ["Rina Takahashi","Nora Kaplan"] published: 2026-06-29 updated: 2026-06-25 articles: 22 --- # 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 35 — Market Pulse Reading the agent ecosystem through a practitioner's lens ### The Furniture Arrives - [The Furniture Is Arriving Before the House Is Built]() — By [Rina Takahashi]() · Published 2026-06-25 · Format: The Furniture Arrives Across the agent ecosystem, multiple players are simultaneously shipping the same category of development: admin consoles, spend controls, identity federation, observability conventions. Institutional furniture that normally arrives after a technology category has settled. But with 88% of organizations using AI regularly and only 23% scaling agents anywhere, the furniture is showing up in the gap between experimentation and production. That timing suggests something specific about where this market actually sits, and what's quietly becoming the real bottleneck. ### Furniture Catalog The flashy part of the agent ecosystem gets plenty of coverage. The part that determines whether agents actually survive in production gets less. Over recent weeks, several developments have quietly filled in scaffolding that enterprises need before autonomous systems can touch real work. Metering consoles, identity protocols, observability vocabularies, regulatory deadlines, partner certifications. None of them generate breathless headlines. All of them address the same underlying tension: agents are gaining capabilities faster than organizations can govern, audit, or even account for them. Six recent pieces of institutional furniture, each filling a specific gap between what agents can do and what organizations require before letting them. - **OpenAI Gives Enterprises One View of Agent Costs** — [Source]() — Published 2026-06-25 Tag: Spend Controls OpenAI's Global Admin Console (June 18, 2026) pulls ChatGPT and Codex credit usage into one dashboard, broken out by user, product, and model, with layered spend limits at the workspace, group, and individual level. The problem is basic but stubborn: you can't budget for agent costs you can't see. - **OpenAI Puts $150M Behind Deployment Capacity Gap** — [Source]() — Published 2026-06-25 Tag: Partner Networks OpenAI committed $150 million on June 14, 2026, to a partner network targeting 300,000 certified consultants by year-end. The subtext is telling: the bottleneck for enterprise AI has shifted from what models can do to whether organizations can rewire workflows and absorb the change. - **A2A Protocol Finds Neutral Ground at Linux Foundation** — [Source]() — Published 2026-06-25 Tag: Protocol Governance Google's Agent2Agent protocol moved under Linux Foundation governance in June 2025, backed by 100+ companies including AWS, Cisco, Salesforce, and Microsoft. The playbook is familiar: interoperability standards don't earn adoption across competing vendors without stewardship that sits on neutral ground. - **Anthropic Swaps Static Keys for Scoped Agent Credentials** — [Source]() — Published 2026-06-25 Tag: Agent Identity Anthropic's Workload Identity Federation (GA June 17, 2026) replaces long-lived API keys with short-lived, scoped credentials verified against OIDC-compliant identity providers. Each workload gets its own service account, roles, and audit trail. When agents touch systems of record, "who did what" stops being optional. - **OpenTelemetry Builds a Vocabulary for Agent Instrumentation** — [Source]() — Published 2026-06-25 Tag: Observability Standards OpenTelemetry's GenAI semantic conventions (v1.42.0) define spans, metrics, and events for model calls, agent operations, tool execution, and MCP interactions. Still maturing, but the premise holds: shared instrumentation vocabulary is a prerequisite for debugging, optimizing, or accounting for agent behavior at any scale. - **EU AI Act Turns Governance Language Into Build Requirements** — [Source]() — Published 2026-06-25 Tag: Regulatory Calendars EU AI Act transparency rules take effect August 2026, with high-risk obligations following from December 2027. Activity logging, technical documentation, human oversight, incident reporting. What reads as policy language on paper becomes engineering work in practice: logs, provenance records, and reversal paths someone actually has to build. ### Protocol Governance - **Linux Foundation Launches the Agent2Agent Protocol Project** — [Source]() — Published 2026-06-25 A2A shifts from Google's stewardship to Linux Foundation governance with 100+ supporting companies. Foundation neutrality changes the adoption calculus, though it sidesteps the authorization questions the spec itself leaves deliberately open. Why does governance matter here? AWS, Cisco, Salesforce, SAP, Microsoft, and ServiceNow backing a foundation-governed protocol signals interoperability is now an institutional priority, not a vendor play. Does neutrality resolve the hard problems? Multi-stakeholder governance removes single-vendor friction but says nothing about who authorizes what across organizational boundaries. - **A2A Protocol v0.3.0 Specification** — [Source]() — Published 2026-06-25 The v0.3.0 spec standardizes transport, task lifecycle, and agent discovery while explicitly deferring authorization to implementers. Credential handling stays out-of-band; authorization logic is "implementation-specific." These remain design goals, not compliance claims. Where does the spec draw its own boundaries? Discovery, delegation, collaboration, task management, and async operations are scoped in. Authority and scope enforcement are scoped out. What does auth-required reveal? The spec encodes a task state for authority gaps mid-execution, acknowledging that agents will hit permission boundaries the protocol itself cannot resolve. - **MCP Authorization Specification (2025-06-18)** — [Source]() — Published 2026-06-25 MCP's authorization spec explicitly prohibits token passthrough to prevent confused-deputy attacks, mandating audience-bound credentials via OAuth 2.1 and RFC 8707. Authorization remains optional for implementations, but the prohibitions reveal where designers see real risk. Why ban token passthrough specifically? Forwarding credentials looks like delegation but creates confused-deputy risk. The prohibition shows protocol designers treating connection and authority as fundamentally distinct. Optional but opinionated? Authorization is not required for all implementations, yet the spec's sharp prohibitions signal that common integration shortcuts carry risks the designers want foreclosed. - **Announcing the Agent2Agent Protocol (A2A)** — [Source]() — Published 2026-06-25 Google's original A2A launch framed the protocol as complementary to MCP: tools versus coordination. Launched with 50+ partners, the protocol moved to foundation governance in under three months, a pace that suggests institutional urgency around standardization. How fast is too fast? Moving from company announcement to foundation governance in roughly three months compresses a timeline that usually takes years in standards work. Complementary in architecture, separate in risk? MCP expands what an agent can access; A2A expands whom it can coordinate with. Each surface carries distinct authorization challenges. ### Implementation Bottleneck - [The Binding Constraint Moved]() — By [Nora Kaplan]() · Published 2026-06-25 Nearly nine in ten organizations [report regular AI use](https://www.mckinsey.com/capabilities/quantumblack/our-insights/the-state-of-ai/). But when McKinsey asked about scaling agents, the picture inverted: 23 percent are scaling them anywhere, and no single business function has crossed 10 percent. A lot of experimentation. Very little that looks like deployment. ### Source Material - **The State of AI in 2025: Agents, Innovation, and Transformation** — [Source]() — Published 2026-06-25 88% adoption, yet no function has scaled agents past 10%. That gap is a demand signal for operational infrastructure, not more models. - **New Usage Analytics and Updated Spend Controls for Enterprises** — [Source]() — Published 2026-06-25 Per-user credit tracking and model-level spend caps signal that AI cost governance is becoming a first-class admin surface, not a finance afterthought. - **Secure Access to the Claude Platform with Workload Identity Federation** — [Source]() — Published 2026-06-25 Replacing static API keys with scoped, auditable, per-workload credentials. Agent authorization is quietly becoming its own infrastructure layer. - **Linux Foundation Launches the Agent2Agent Protocol Project** — [Source]() — Published 2026-06-25 A2A moves from Google-originated spec to neutral governance. A specific kind of institutional furniture: shared standards nobody owns. - **EU AI Act: Regulatory Framework Overview** — [Source]() — Published 2026-06-25 Transparency rules hit August 2026, high-risk obligations by December 2027. Governance language on a regulatory calendar becomes system requirements with deadlines. - **Visa and OpenAI: Building the Future of AI Commerce** — [Source]() — Published 2026-06-25 Spending limits, merchant restrictions, tokenized credentials, fraud monitoring. Payment networks are shipping pre-built operational guardrails before agentic commerce fully arrives. ### Past Articles - [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. - [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. ## Other sections in Issue 35 - [Daily Brief]() - [Foundations]() - [Practitioner's Corner]() - [Echoes]() - [Vision]() ## More - [Publication guide]() - [Issue archive]()