Every programmatic media transaction today requires a pre-existing technical integration between the buyer's platform and the seller's platform. A DSP cannot bid on inventory from an SSP unless someone has built and maintained the API connection between them. That integration is the prerequisite for trade.

This infrastructure requirement shapes the market in ways that are easy to overlook because the API mesh has existed for long enough to feel like a natural feature of media trading rather than a design choice. It is not. It is an architectural constraint with real consequences for who can trade, with whom, and at what overhead.

Why does the current API model create structural constraints on trading relationships?

An API integration between a DSP and an SSP is not free to build or maintain. It requires engineering resource from both sides, ongoing maintenance as each platform updates, and commercial agreements that define the terms of the connection. The upfront and ongoing cost means that integrations are only built for relationships that justify the investment.

The result is a concentrated market structure. A relatively small number of DSPs and SSPs hold most of the integrations, because they are the only players with the scale to make those integrations economical. A new DSP or SSP entering the market cannot instantly connect to every counterparty: it needs to build integrations, which takes time and creates a dependency on the larger platforms.

Publishers and advertisers who are not represented by one of the major platforms effectively have limited access to the rest of the market. The integration requirement is a structural moat that protects the established intermediaries.

What does agent-to-agent negotiation require instead of a pre-built API connection?

An agent-to-agent negotiation does not require a pre-built API integration between the buyer and seller systems. It requires a shared protocol: a common format for deal proposals, responses, and deal records that both agents can use regardless of the underlying systems they run on.

The distinction is significant. An API integration is bilateral and specific: it connects two specific systems and requires both to agree on the interface. A shared protocol is multilateral and general: any agent that implements the protocol can trade with any other agent that implements the same protocol, without a prior bilateral integration.

This is analogous to the shift from proprietary data formats to open standards in other parts of technology. Before open standards, interoperability required bilateral agreements. After open standards, interoperability is a property of the protocol, not of the relationship.

What stays the same when the API mesh is replaced by a shared protocol?

The underlying infrastructure of ad serving, delivery, and measurement does not change. Creative assets still need to be served. Impressions still need to be measured. Brand safety verification still needs to happen. The reporting systems that advertisers use to understand campaign performance still need to function.

The change is in the negotiation and deal record layer, not in the delivery and measurement layer. An agent-to-agent negotiation agrees the terms of a deal. The execution of that deal, once agreed, flows through the existing delivery infrastructure. The two layers are separable.

Identity resolution, audience data, and contextual targeting also remain relevant. The buyer agent still needs to know what audience it is buying. The seller agent still needs to be able to describe what audience it can deliver. The data infrastructure that supports those functions does not disappear: it becomes an input to the negotiation rather than a parameter in an auction.

What does the transition period look like?

The API mesh does not switch off. For the foreseeable future, most programmatic trading will continue to flow through existing DSP-SSP integrations. The agent-to-agent negotiation layer will develop alongside it rather than replacing it immediately.

The transition is likely to be demand-led. Buyers with agent infrastructure will prefer direct negotiated deals for high-value, high-specificity inventory. They will continue to use programmatic auction buying for commodity inventory where deal-level specificity is not required. Publishers will respond to that demand by building sell-side agent capability for their premium inventory.

The market will run both models in parallel for some years. The practical question for participants is which model will dominate for which category of deal, and how quickly that division of labour becomes clear enough to justify infrastructure investment on both sides.

What is the role of deal record infrastructure in this transition?

In the current model, the API integration between DSP and SSP carries an implicit record of the deal: the bid request, the bid response, and the impression log. That record is held by both parties but in separate systems, and it rarely becomes the basis of a post-campaign dispute resolution because programmatic deals are not structured around bilateral commitments.

In an agent-to-agent model, the deal record is the central artefact. It is what makes a direct connection between buyer and seller trustworthy without the accreditation backstop of a major DSP or SSP. The deal record infrastructure, which Alkimi's DealSheet provides, is therefore not a complementary feature of the agent negotiation model: it is the mechanism that makes the model function at all.

The shift from API connections to direct agent negotiation is, at its core, a shift from infrastructure that enables connection to infrastructure that enables trust. Both are necessary. Only one of them has been built for the agentic trading model.