Not a model router
Routing is cost, quality, and reliability infrastructure. It can use multiple providers without becoming the company's moat.
About CommandLayer
Build the things agents spend money on.
Model routers, wallets, payment rails, registries, and general-purpose agents are becoming infrastructure. CommandLayer is focused on the other side of that market: useful machine services those agents can actually buy.
Positioning
Seller-side infrastructure for machine commerce.
Not a payment protocol
Settlement rails are adapters. Metering, pricing, execution economics, and outcome quality remain independent of one rail.
Not a generic registry
Directories and identity systems help buyers find a service. They do not replace the service, its contract, or its execution evidence.
What compounds
Composition, state, and execution evidence.
The factory is designed around three durable sources of value: combining primitives into better outcomes, maintaining state over time, and producing evidence about execution or observed state that a third party can inspect later.
M1 · Composition
Turn several providers and primitives into one accepted result.
M2 · Durable state
Remember what changed, what was observed, and what must happen next.
M3 · Execution evidence
Preserve provenance, integrity, timestamps, checks, and output linkage without overstating truth.
Open core + commercial factory
Keep the standard boring. Charge for useful execution.
CommandLayer's open components remain useful as reference schemas, cryptographic receipt primitives, verification rules, runtimes, and SDK surfaces. The commercial factory is where pricing, metering, provider composition, state, distribution, and hosted outcomes live.
Commons / open surfaces
Schemas, receipt formats, verification, reference runtime behavior, and SDK primitives should remain understandable and independently inspectable.
Commercial factory
One production control plane owns service manifests, routing, economics, adapters, execution state, telemetry, and outcome delivery.
Identity
Readable names are a layer, not a religion.
A machine service can simultaneously have an HTTPS endpoint, wallet, ENS name, ERC-8004 identity, platform ID, or future identifier. Premium functional names can be valuable public service identities without requiring ENS to become universal.
Design principle: identity, discovery, settlement, model providers, and directories stay replaceable. The service contract and evidence boundary stay stable.