ADI Blog Agent commerce 2 min read

Why shop integrations are trust inputs, not the trust layer

Shopify, WooCommerce, CSV, custom APIs, and marketplace connectors help ADI import merchant product state. They are not the trust layer by themselves. The trust layer begins when ADI normalizes that product state, binds it to a merchant organization, and uses it in mandate and payment checks.

Connectors bring product data into ADI; they do not automatically make every imported object trusted forever.

Trust requires normalization, merchant ownership, active-state control, auditability, and payment-time validation.

A merchant agent can use the merchant shop directly, while ADI uses imported product state as the independent verification reference.

What integrations are for

A merchant should not have to manually retype every product into ADI if the source already exists in Shopify, WooCommerce, a marketplace system, an ERP, or a custom shop API.

Integrations exist to move product data from those systems into ADI so the trust layer can reason about it. That is ingestion, not enforcement.

The three-layer model

Integration input versus trust enforcement

A connector can feed the catalog, but only ADI enforcement turns that catalog into governed agent commerce.

flowchart LR
    source["Shop, ERP, marketplace, CSV, or API"] --> connector["ADI connector"]
    connector --> catalog["Normalized merchant trust catalog"]
    catalog --> verifier["AP2 and policy verification gate"]
    verifier --> payment["Prepaid virtual-card payment"]
    verifier --> audit["Receipts and audit evidence"]

Why the connector alone is not enough

A connector can be stale, misconfigured, rate-limited, or partially synchronized.

A shop product may be visible operationally but not approved for agent-driven purchase.

A marketplace listing may contain fields that are not safe to use as payment evidence without normalization.

Payment decisions need a stable ADI-side reference so the receipt can be reconstructed later.

How merchant agents should use this

The merchant agent can keep working where it belongs: inside the merchant commerce environment. It can search, recommend, bundle, and negotiate using the merchant's operational systems.

When the buyer agent is ready to transact, the resulting AP2 cart is checked against the ADI trust catalog. That is the point where the conversation becomes a governed commercial action.

What a mature integration should prove

When the product was imported or synchronized.

Which merchant organization owns the product reference.

Whether the product is active for governed agent commerce.

Which fields were used for payment validation.

Which catalog version was bound into the receipt.

The honest current-state distinction

A product connector is useful because it reduces manual catalog maintenance. But the connector is not the security boundary. The security boundary is the ADI verification path that rejects mismatched merchants, unknown SKUs, inactive products, insufficient wallet funds, invalid mandates, and unauthorized agent actions.

More articles from the technical reading layer.

OPEN AGENT TRUST Agent interoperability

How external agents verify an ADI merchant agent

A buyer agent does not have to live inside ADI to trust an ADI merchant agent. It needs public discovery, a resolvable agent identity, signed credentials, and a clear payment mandate path. This article shows how those pieces fit together.

A2A discovery makes the merchant agent reachable.

ADI trust discovery makes the merchant agent accountable.

Read article

MERCHANT TRUST Agent commerce

How the merchant trust catalog works

A merchant agent can sell from the merchant shop, but ADI needs an independent trust reference for what that agent is allowed to sell. The merchant catalog in ADI is that reference: a canonical product whitelist used to validate agent commerce before money moves.

The shop catalog runs the business.

The ADI catalog proves what the merchant approved.

Read article

AP2 VALIDATION Agent commerce

How ADI validates what a merchant agent sells

A merchant agent can describe an offer, but ADI should not pay from description alone. ADI validates the AP2 mandates, the merchant organization, the product SKU, the trusted catalog entry, the buyer wallet, and the virtual-card policy before the transaction becomes authorized.

Conversation creates intent.

AP2 creates structured mandates.

Read article

INTEGRATION MODES Agent integration

Three ways to connect an external agent to the ADI trust layer

An external agent does not need to run inside ADI to be governed by ADI. The practical question is how the relying system authenticates that agent and when it asks ADI for trust, delegation, and certificate state.

Standard mode: API key or agent token plus online trust lookup

Enterprise mode: OIDC plus trust lookup

Read article

TRUST FOUNDATIONS Agent trust

Why agents need a trust layer

An API token only tells you whether a request is authenticated. A trust layer tells you which agent is acting, on whose behalf, which proofs are valid, and whether that agent can be stopped.

When OAuth stops being enough

Which questions a trust layer must answer

Read article

ARCHITECTURE System architecture

Separating A2A, trust, and AP2

The key architectural principle is separating the layers. A2A is communication. Trust is governance. AP2 is payment behavior.

What A2A actually standardizes

When trust is additionally required

Read article

PRODUCT ADI stack

How ADI works as an agent trust stack

ADI is not a single interface. It is an operational layer that connects discovery, identity, trust, and payment flows for agentic systems.

The platform’s four layers

Where A2A, MCP, and AP2 meet

Read article

A2A EXPLAINED A2A fundamentals

What A2A is and what it is not

A2A gives agents a shared way to describe themselves, exchange messages, and execute tasks. It does not automatically solve identity binding, delegated authority, auditability, or payment control.

A2A standardizes discovery, messages, tasks, and declared security capabilities.

A2A does not by itself answer who the agent represents or what it is permitted to do.

Read article

AP2 FOUNDATIONS AP2 payments

What AP2 solves for agent commerce

AP2 gives agent commerce a structured model for intent, cart, payment authorization, and receipts. Without that model, every agent-payment integration invents its own fragile semantics.

AP2 introduces a common vocabulary for agent payment flows.

Mandates separate scope, intent, and final payment authorization.

Read article

TRUST FOUNDATIONS Agent trust

What agent trust actually means

Agent trust is not a brand claim. It is the operational ability to prove who an agent is, on whose behalf it acts, what it is allowed to do, and how that authority can be revoked or audited.

Trust begins where authentication alone stops.

A real trust layer must support revocation, inspection, and evidence.

Read article

PRODUCT EXPLAINER ADI stack

What ADI does in an agent stack

ADI is the trust and control layer that sits between agent interoperability and real business action. It helps organizations let agents act without treating those agents like ungoverned black boxes.

ADI is where governance enters the agent stack.

The platform connects external agents, enterprise controls, and transaction policies.

Read article

SIGNATURES AND SEALS Trust services

Human signatures vs organization eSeals

A human signature proves the will or approval of a natural person. An organization eSeal proves that a trust object was issued or sealed by a legal entity. In enterprise agent systems, those are different jobs and they should not be collapsed into one.

Human signatures answer: who personally approved this?

Organization eSeals answer: which legal entity issued or stands behind this artifact?

Read article