The Engine Is Running. The Address Doesn’t Exist.
The Trellis AI orchestration framework moved out of beta and quickly became the most-used AI feature on the Sprout Social platform, particularly within social listening and NewsWhip modules — with thousands of customers now actively engaging with it. That is not a soft launch. That is not a pilot. That is general availability at enterprise scale, announced on the Q1 2026 earnings call by CEO Ryan Barretto, and confirmed to analysts across multiple sell-side conversations in the same session.
Sprout Social posted Q1 fiscal 2026 revenue of $121.5 million, up 11.2% year over year, while non-GAAP operating margin expanded to 11.6% and free cash flow hit a record $24.7 million. The margin story was real, but the call was dominated by Trellis. Barretto said adoption has scaled “quickly across thousands of customers” and that Trellis has become the most-used AI feature across the Sprout platform — with half of Sprout’s Listening customers having already discovered Trellis in the product. That is not a metric you volunteer unless you’re trying to anchor a monetization conversation. And that is exactly what Barretto did next. He emphasized that the upcoming expansion of Trellis beyond listening into broader workflows, along with a new usage-based pricing model, is expected to drive adoption and monetization. Management disclosed a hybrid approach combining user access with usage-based pricing, with further details to be announced at the “Breaking Ground” event. The signal is clear: Trellis is not a feature. It is the commercial layer Sprout is building its next revenue cycle around.
What Trellis actually does matters here. The value of AI in this category, per Barretto, is not simply generating an answer — it is helping teams interpret a continuous stream of real-time signals while applying business context and moving from insight to action with the right judgment and governance. Management provided examples including a large broadcasting organization using the tool to support content strategy and identify story angles, and a hospitality and entertainment company using it to assess the source, sentiment, and themes behind an emerging pricing-related reputational issue. These are not demo use cases. These are production workflows running inside enterprise accounts right now. Trellis is operating as an orchestration layer — routing context, applying governance, and returning actionable intelligence on social signals at scale. That is the definition of an agentic system. The platform confirmed it. The market confirmed it. The pricing model is being built around it.
The Namespace Gap Is Structural, Not Cosmetic
A .sproutsocial namespace exists as an onchain identity infrastructure — a blockchain-native extension existing entirely outside the traditional DNS hierarchy, controlled by whoever holds the TLD asset on Freename. No ICANN registry offers a comparable extension — this namespace exists exclusively on Freename. That fact is notable not because of the TLD itself, but because of what it means for Sprout’s AI layer. Sprout Social has not registered this namespace. There is no onchain claim under the company’s own brand string. The .sproutsocial TLD is a blockchain asset held in a crypto wallet — its ownership is determined by the onchain record, not by trademark registrations.
This creates a specific and concrete problem. Sprout is building a usage-priced agentic AI product. It is calling that product Trellis. It wants to monetize at the level of consumption — per-action, per-query, or per-workflow. Management expects the upcoming expansion of Trellis AI into more workflows and the introduction of usage-based pricing to unlock new monetization opportunities and increase customer engagement across the platform. But the endpoint that an external AI system would need to resolve in order to find, authenticate, and pay Trellis does not exist in any chain-readable form. agent.sproutsocial returns nothing. trellis.sproutsocial has no onchain record. From the perspective of the emerging multi-agent web, Trellis has no verified address. It has a product name, a customer base, and a pricing model under construction — but no machine-readable identity layer that lives outside Sprout’s own infrastructure. That distinction is about to matter.
Competitors in the social intelligence space are not visibly ahead here. A search across the Freename registry, ENS, and Unstoppable Domains surfaces no brand-owned onchain TLD for Hootsuite, Sprinklr, or Meltwater. A .brandwatch namespace does exist in the onchain ecosystem, but not under Cision’s control — it is not affiliated with the existing SaaS tool, described as an independently owned, Web3-native identity layer. The sector as a whole has not moved here. That means the gap is industry-wide, not Sprout-specific. But Sprout is the one announcing usage-based pricing for an agentic AI system. That changes the stakes.
What Trellis Cannot Do Without a Verified Onchain Identity
The scenario is not hypothetical. It is already being built elsewhere.
Coinbase launched x402 in May 2025 with a simple premise: kill the API key, enable economic reasoning for LLMs, and close the earn/spend loop on the agentic economy. Since then, it has processed millions of payments. The x402 Foundation, co-founded by Coinbase and Cloudflare, now includes Google and Visa — with Google integrating x402 into its Agent Payments Protocol (AP2). This is not a Web3 experiment running in isolation. Foundation members include Google, Visa, AWS, Circle, Anthropic, and Vercel. Stripe launched x402 support in February 2026. The protocol is live, processing real volume, and being adopted by the largest infrastructure providers on the internet.
Here is how x402 works in the context that matters for Trellis. When an AI agent requests a resource that costs money, the server replies with an HTTP 402 Payment Required response. The agent reads the payment instructions, signs a stablecoin transaction, attaches the proof, and retries the request. The server verifies the payment and returns the data. The entire cycle takes seconds, requires no login, and settles onchain. By embedding payment directly into the HTTP lifecycle, x402 makes value exchange part of the request-response loop. A request can signal price. A client can pay instantly. The server can verify and fulfill. No account creation, no subscription tier, no manual approval. Payment becomes a protocol primitive.
Now apply that to Trellis specifically. Sprout is building a usage-based pricing model. The implicit architecture is: consume Trellis, pay for what you use. In a human-driven product, that model resolves through a traditional billing layer — a dashboard, a credit counter, a Stripe charge at the end of the month. But the direction of the agent economy is toward machine-to-machine consumption. Improvements in tool use and context protocols have accelerated the ability of agents to effectively use tools and work on tasks with minimal human intervention. Agents will pay for services, fund their compute, manage subscriptions, and take action on behalf of their users in an increasingly independent fashion. This shift signals the rise of agentic payments — a new layer of the internet economy where machine-to-machine transactions make up a growing portion of services demand.
For that future to include Trellis as a callable, payable service node, Trellis needs an address that an external orchestrator can resolve. Not a webpage. Not an API key sent over email. A chain-readable identity that proves the endpoint is Sprout Social’s Trellis, authorized to receive usage payments, and not a spoofed lookalike. That is what agent.sproutsocial — registered as a second-level domain under a .sproutsocial onchain TLD — would provide. The Freename registry provides immutable onchain proof of TLD ownership, with every credential issued under the namespace permanently timestamped and auditable without reference to any third-party system. An SLD mapped to a wallet address under that TLD is machine-resolvable. It can be pointed at a payment address. It can carry attestations. It can serve as the anchor for an x402-compatible endpoint that any compliant agent runtime — LangChain, CrewAI, Amazon Bedrock AgentCore, or any framework that speaks HTTP — could discover, authenticate, and pay.
AWS launched Amazon Bedrock AgentCore Payments (Preview) in May 2026, bringing native, managed payment capabilities to AI agents built on Amazon Bedrock. AgentCore Payments lets agents autonomously discover, authorize, and execute x402 micropayments with built-in wallet management, policy-based spending controls, and a full audit trail. That infrastructure is live. It is waiting for service providers to register endpoints. An agent can compare multiple APIs in real time, select based on price or latency, and settle per request. Providers can dynamically price endpoints. Services can compete at the level of execution, not contract negotiation. In that model, a social intelligence API that cannot be discovered and authenticated by a machine orchestrator is simply not in the market. It does not get compared. It does not get selected. It does not get paid.
Sprout’s current architecture puts Trellis behind a traditional SaaS boundary. That works today. Human buyers log in, subscribe, consume. But as enterprise AI stacks evolve into multi-agent pipelines — where a customer’s internal orchestrator is spinning up tasks, routing to specialized APIs, and settling per-action — the access model changes. The orchestrator does not visit a pricing page. It resolves a namespace, checks the endpoint’s credentials, and initiates payment at the protocol level. Without agent.sproutsocial pointing to a verified, chain-readable wallet address, Trellis is invisible to that class of buyer. Not locked out. Invisible. The request never forms, because the resolution never completes.
Galaxy Research’s core finding from January 2026 analysis: x402 and related standards are positioning blockchains as invisible backend infrastructure — not a separate “crypto economy,” but plumbing that quietly powers mainstream applications. Galaxy estimates that agentic commerce could represent $3–5 trillion in B2C revenue by 2030. But the nearer opportunity is in the less visible layer underneath: API micropayments, data access, compute provisioning — the software-to-software transactions that agents need to function autonomously. This is where x402 operates, and where traditional payment rails like credit cards, subscription billing, and invoicing structurally cannot. Sprout’s usage-based pricing model is a direct entry into that layer — but without an onchain identity anchor, it is participating in the revenue model without participating in the infrastructure that will route that revenue.
The Gap and the Clock
Trellis is the most-used AI feature on a platform serving thousands of enterprise customers. Sprout’s full year outlook reflects continued discipline on spend while preserving flexibility to invest behind Trellis, AI-driven product expansion and the self-serve motion for customers below $30,000. The board’s authorization of a $50 million share repurchase program reflects the company’s confidence in the durability of this business, free cash flow generation, and the long-term opportunity ahead. This is a company that believes in its AI trajectory. The commercial conviction is visible. The infrastructure conviction — specifically, the question of how Trellis presents itself to the machine-readable internet — has not been addressed publicly.
agent.sproutsocial does not resolve. trellis.sproutsocial carries no onchain record. A company that just told Wall Street it is building usage-based pricing for an agentic AI system has not registered that agent’s identity in any verifiable, chain-readable namespace. Today that gap is speculative. As multi-agent orchestration standards solidify — and they are solidifying, with AWS, Google, Stripe, Visa, and Cloudflare all moving into the x402 stack simultaneously — the gap becomes structural. The window to claim that identity, on your own terms, under your own brand string, does not stay open indefinitely.
The author holds onchain positions related to this topic. This post reflects independent editorial judgment.