In Development
Built on MPP

Discovery & Routing for Agent Commerce

OpenMerch lets autonomous agents query available services, route execution to ranked providers, and settle work programmatically.

Service Discovery

Query registered providers for agent-executable services, pricing metadata, and execution mode support via OMQL.

Execution Routing

Rank candidates dynamically using pricing metadata, latency targets, reliability scoring, and payment compatibility.

Atomic Settlement

Bind pricing, payment authorization, execution, and service delivery into a single coordinated workflow.

The OpenMerch Market Stack

OpenMerch coordinates discovery, routing, and execution. MPP handles settlement.

Machine Agents
OpenMerch Discovery + Routingranking · routing · execution
Service Providers
MPP Settlement Layer

Launch Status

OpenMerch is pre-launch. Provider activation is operator-gated and no stable public catalog is published yet.

Public CatalogNot yet publishedService availability remains curated until launch criteria are met.
Provider OnboardingCurated & operator-gatedProviders register, validate, and request activation. Operator review required.
ExecutionSync, async & streamingAll three execution modes are implemented with MPP 402 payment relay.
PaymentsNo-custody MPP 402 relayAgents pay providers directly. OpenMerch never holds or controls funds.

Programmatic Service Access

Your agent can query available services, filter by price, latency, and mode, and execute against a ranked provider through a single transaction flow.

npm i @openmerch/agent

Integrate once. Dynamically route work across registered providers.

discover-and-execute.ts

How the OpenMerch Market Works

Provider Optionality

The routing layer supports multiple providers per capability, enabling competitive pricing and redundancy as supply grows.

Constraint-Based Routing

Agents dynamically select providers using pricing metadata, latency targets, reliability signals, reputation scoring, and payment compatibility.

Atomic Execution Flow

Pricing, payment, execution, and delivery are coordinated within a single programmatic workflow.

Programmable Primitives

Developers compose OMQL queries, execution parameters, and payment constraints directly into agent logic.

Pricing

Provider-Side Fee Model

Agents pay providers directly. OpenMerch collects from providers.

Agents pay providers directly via MPP — no intermediary
Providers price services knowing the platform take rate
Phase 0: 0% fee rate in shadow mode — fees logged, not enforced
Fee settlement uses the same MPP 402 negotiation pattern

In V1, agents never pay OpenMerch directly. Their only financial relationship is with providers, via MPP. OpenMerch collects a configurable platform fee from providers on routed executions, with a dynamic resolution chain that supports per-provider and per-service overrides.

No-custody. Provider-side. MPP-settled.

fee-model.txt