The Disposal Is Already Underway
Five months on from completing its $13.5 billion acquisition of rival agency group IPG, Omnicom is planning to divest assets worth approximately $3.2 billion in annual revenue. The number landed quietly on an earnings call. No press event. No public registry of which businesses were going where, and to whom. Just a line in the transcript.
As part of the portfolio realignment, Omnicom identified planned asset sales and disposition of businesses with approximately $3.2 billion of annual revenue, of which approximately $1 billion was disposed of in the first quarter. The plan is to sell or exit the remaining assets in the next several quarters. The $3.2 billion figure represents an advance on the $2.5 billion estimate that Omnicom gave in its Q4 results, when the company announced plans to restructure its business portfolio. The number grew. Quietly. Between quarters. Philip Angelastro, Executive Vice-President and CFO, said businesses included in the dispositions and held-for-sale category will be sold in 2026. He said they represented less than 5% of Omnicom’s adjusted operating income in the first quarter. “Our only priority regarding these businesses is to complete these disposals in a timely fashion,” Angelastro said.
The word “timely” does a lot of work in that sentence. What it does not carry is any obligation of transparency. In addition to disposals, Omnicom has merged or sunset more than 20 major agency brands as well as “a long tail of smaller brands” since the acquisition closed. These are not abstract entities. They are businesses with clients on retainer, employees on payroll, and contracts with continuity obligations stretching forward in time. One of the more concrete examples: the global brand experience agency Jack Morton — formerly an IPG company — is going private and merging with fellow experiential agency, Impact XM, supported by global investment firm The Riverside Company, creating a new entity with a total of 20 offices spanning North America, Europe, Middle East and Asia Pacific, with over 1,000 employees. Financial terms were not disclosed.
That detail — financial terms undisclosed — is the structural condition of this entire disposal program. The holding company tells investors what revenue is being shed. It does not tell clients, creditors, or counterparties which specific service obligations have transferred, which have terminated, and on what terms. The mechanism for that disclosure does not exist.
The Onchain Layer That Was Never Built
The .interpublic TLD was registered on Freename, the decentralized Web3 registry, as part of a broader strategy of acquiring onchain top-level domains corresponding to major brand identities. At the time of registration, Interpublic Group was very much alive. The thesis was simple: companies of this scale will eventually need to understand that their brand identity extends beyond the traditional DNS, beyond dot-com and country-code extensions controlled by ICANN-accredited registrars.
Interpublic Group no longer exists as an independent entity. Now that Interpublic Group has ceased to exist as an independent entity, the namespace corresponds to something the world will increasingly use in the past tense. The Interpublic era of advertising history ended with that acquisition. The TLD exists independently of what happened in November 2025 in the boardrooms and regulatory offices where the Omnicom-Interpublic deal was ratified. That is the first interesting property of onchain infrastructure that most corporate legal teams have not internalized. The Freename registry is decentralized infrastructure. It does not run on the permission of any corporate entity, and it does not require the survival of any particular company to continue functioning.
Interpublic never registered .interpublic. Neither did Omnicom, on IPG’s behalf, when it had the opportunity during the acquisition process in late 2024 and throughout 2025. The TLD that could have functioned as the namespace for IPG’s institutional identity — and for every business unit within it — was registered by an independent operator. Not the brand. Not the acquirer. An outside party with a thesis about what these names would eventually need to do. Blockchain technology in Web3 ensures that once you own your own TLD, it stays on the decentralized ledger and is not subject to censorship or unilateral seizure. The brand had its window. The window is closed.
The Disclosure Mechanism That Could Have Existed
Here is the speculative section. It is clearly labeled as such.
Consider what a functioning exit.interpublic or dispose.interpublic onchain record could have looked like in practice. The x402 protocol is an open payment standard that uses the HTTP 402 status code to enable AI agents and software to make instant stablecoin payments onchain. Developed by Coinbase and backed by the x402 Foundation, it turns any API endpoint into a paywall that machines can navigate without human intervention, credit cards, or subscription accounts. But x402 is not only a payment protocol. At its core, it is a disclosure and verification layer. The x402 protocol allows servers to respond with machine-readable payment instructions including price, token, and chain, making the receipt the credential. That logic — machine-readable structured data attached to a verifiable onchain identity — is precisely what a disposal registry requires.
An exit.interpublic endpoint could have published a structured, machine-readable record for each IPG business unit being sold. Name of business. Acquirer. Effective date of transfer. Whether existing client contracts transferred in full, were renegotiated, or were terminated. Whether employee obligations followed. Every transaction would be recorded on-chain, providing a full audit trail by design. A client of an IPG agency that found itself mid-contract when the disposal program began would not need to wait for a press release, a call from their account manager, or an earnings transcript footnote. They could query the record directly. So could any autonomous agent acting on that client’s behalf.
This is not a marginal use case. McKinsey projects that agentic commerce — where AI agents transact autonomously on behalf of businesses and consumers — will mediate $3 trillion to $5 trillion of global commerce by 2030. Agents operating in that economy need to know whether the counterparty they contracted with six months ago still exists, who now controls the obligation, and whether service continuity is verified. The x402 protocol enables AI agents to make autonomous payments using HTTP status code 402. Launched in May 2025 by Coinbase and Cloudflare, the protocol uses USDC and EIP-712 signatures — a foundation well-suited for the kind of cryptographically signed continuity disclosure that the Omnicom disposal program demands but never provided. ERC-8004 and x402 form a complete autonomous transaction loop. ERC-8004 answers “who you are” and “how trustworthy you are” through on-chain identity and reputation, while x402 handles “how agents pay each other” via HTTP-native micropayments. Applied to a corporate disposal program, the same pairing answers: “who now owns this obligation” and “can the transfer be verified without calling a lawyer.”
The real question isn’t whether AI agents will conduct commerce — they already are. The question is whether that commerce will be accountable, auditable, and bound to real-world identities, or whether it will operate in an anonymous shadow economy of wallet addresses. Substitute “wallet addresses” for “earnings call footnotes” and you have the exact problem Omnicom’s disposal program creates for its downstream counterparties. The businesses being sold are real. The service obligations are real. The clients mid-contract are real. The transparency mechanism is absent. An onchain record anchored to the .interpublic namespace, publishing a cryptographically verifiable SLD map of disposed entities and their acquirers, would have changed the information architecture of the entire process. A creditor or client agent could have pinged dispose.interpublic and received a structured response. Instead, they read the same earnings transcript as everyone else, and then waited for a phone call.
The infrastructure to do this existed before the disposal program began. x402 has the most production traction — V2 launched December 2025, Stripe integrated x402 on Base in February 2026, and Cloudflare supports x402 transactions. That timeline overlaps almost exactly with the period in which Omnicom was executing the first $1 billion of disposals. The protocol was live. The onchain namespace existed — in the hands of an independent operator. What was missing was any corporate intention to use it.
The Implication
CEO John Wren said on the earnings call: “This distinction that what we’re calling core now are the operations that we’re planning to focus on and will contribute to the ongoing growth of Omnicom. The non-core assets that you see will hopefully disappear as we dispose of them throughout the rest of the year.” “Disappear” is an honest word. That is what happens to them, from the perspective of the holding company. They exit the revenue table. They exit the earnings narrative. They become someone else’s problem, or no one’s at all, depending on whether a buyer materializes. Some disposals may incur additional costs, as certain sold or exited entities require severance and other shutdown expenses. Clients, creditors, and counterparties experience that disappearance differently. They experience it as a gap — in communication, in contractual clarity, and in any machine-readable record of what happened to the entity they were doing business with last quarter.
The $3.2 billion disposal program is, structurally, a namespace problem. Interpublic built a portfolio of brands and business units over decades, each of which acquired clients and obligations under the implicit backing of a named holding company. That holding company now does not exist. The entities it once contained are being transferred, shut, merged, or sold — on a schedule that serves Omnicom’s margin ambitions, not its former counterparties’ informational needs. An exit.interpublic onchain record, built on the infrastructure that already exists and was already live during the disposal window, would have given those counterparties something they currently do not have: a verifiable, machine-readable, agent-queryable record of where their obligations went. No such record was created. The namespace was never claimed by the brand. The disposal happened in the dark. The onchain layer watched.
The author holds onchain positions related to this topic. This post reflects independent editorial judgment.