Marketplaces & Aggregators, TrustPixel
Market 04 · Marketplaces & AggregatorsMarkets / 04

One connection. Thousands of merchants, each with their own rules.

You already solved aggregation once. Asking every merchant to solve agent commerce individually would undo it.

Merchant base · one connection4,180 merchants
{{ l.label }} {{ l.val }}
Per-merchant terms preserved throughout* Illustrative
The marketplace thesis
Can thousands of merchants become executable without erasing merchant rules?

Aggregation is not the same as being executable.

A marketplace already normalises catalog, payment and disputes across a fragmented base. What it cannot yet do is let an outside agent transact against that base under authority the merchant can verify.

Connecting once makes every opted-in merchant reachable without asking one of them to build anything.

merchant opt-ineligibilitycommission termsfulfillment SLAreturn policystructured intent

Four thousand merchants on your platform.
An agent cannot buy from one of them.

Aggregation solved discovery. It did not make anything executable.
One connection, thousands inside it

The platform is supply and infrastructure at once.

Outer boundary · the platformone integration

You connect once and the whole base becomes reachable. Platform-wide defaults set the floor: which categories are exposed, the commission model, the fulfilment standard, the returns window.

Inner boundary · each merchant4,182 of them

Inside the platform's floor, every merchant keeps its own ceiling. Opt in or stay out, set its own prices, refuse a category, close for a holiday. The merchant builds nothing.

OPTED IN
3,410 merchants
CATEGORY LIMITS
611 merchants
OUT BY CHOICE
161 merchants
Innermost · one purchasetp_txn_5512

An agent arrives with a mandate and sees only what the platform exposed and the merchant permitted.

Merchant controls

Marketplace-wide defaults. Merchant-level override.

The hard part of aggregated agent commerce is not connectivity, it is whose rule wins. Set a platform default and see which merchants inherit it and which have overridden.

Platform default

A merchant can always be stricter than your default. It can never be looser than the buyer's mandate.

{{ ctlName }}{{ ctlCoverage }}

{{ ctlBody }}

{{ r.who }}{{ r.state }}
{{ ctlNote }}
* Illustrative
Stale listings

The offer expires. The listing does not have to.

A merchant deactivates a listing four seconds after an agent received an offer for it. Marketplaces live with this; agents cannot. Offer expiry and a pre-commit callback fail the transaction cleanly instead.

Offer carries an expiryseconds to minutes
Pre-commit callback to the platformbefore money moves
Failure returns a class, not a 500agent re-sources
Merchant is never committed by a stale quoteby design
Commission and settlementper merchant
Marketplace remains merchant of recordunchanged
Existing commission structure appliesyour terms
Settlement cadence to merchantsunchanged
Disputes handled in your existing flowwith evidence attached
Agent-channel reporting per merchantnew
Nothing about how you pay merchants changes. What changes is that a new class of buyer can reach them.
Walk one purchase
mnd_6613 · illustrative

One connection, four thousand merchants.

The merchant never built anything. Its rules still decided what the agent was allowed to do.

Ask “Replace the group head gasket on the espresso machine, genuine part only.”
Rules Cap 240.00 USD · genuine parts · returnable within 30 days
Search One integration · 4,100 opted-in merchants · 210ms
Choose Aftermarket removed by the buyer’s rule, two merchants removed by their own
Buy The marketplace stays merchant of record. 186.00 USD captured
Deliver Existing fulfilment network · nothing new to run
Record The merchant receives the intent behind the demand, not just an order

Make the whole base executable in one integration.

Connect your merchant base Build on aggregated supply All markets