The economic side of CommandLayer — verbs and schemas for payments, settlement, fulfillment, and verification. Commercial builds on Commons semantics and x402 transport, so agents can authorize, checkout, purchase, ship, and verify with stable, shared JSON contracts. All schemas are permanently free; the economics live in execution, not in the verb language.
Commercial verbs capture the higher-value actions agents perform when money, risk, and fulfillment are involved: taking payments, settling purchases, shipping goods, and verifying identities. Commons gives you the shared language for analysis and formatting; Commercial extends that language into economic flows that can plug cleanly into x402 and ERC-8004 rails.
Verbs that map directly to real revenue events:
authorize, checkout, purchase,
ship, verify. Standardized shapes make these
flows easier to route, audit, and compose across providers.
Commercial assumes Commons exists. Analysis, summarization, parsing, and formatting wrap around payment and logistics flows, so you don’t invent new formats every time you connect an economic agent.
Commercial schemas are versioned, pinned, and free to implement under Apache-2.0. Pricing, routing, SLAs, and guarantees live in the Runtime layer, not in the schema definitions.
Initial set of economic verbs. Each row lists the verb, its purpose, and direct
links to the request and receipt JSON Schemas
under https://commandlayer.org. These schemas are the stable contracts
for v1.0.0.
These links are stable for v1.0.0. Future changes ship as new versions
(v1.1.0, v2.0.0) under
/schemas/vX.Y.Z/commercial/... — early adopters can keep targeting
v1.0.0 without churn.
| Verb | Category | Purpose | Request schema | Receipt schema |
|---|---|---|---|---|
authorize |
Auth / payments | Perform payment or access authorizations with traceable outcomes before money moves. | request | receipt |
checkout |
Commerce / cart | Coordinate carts, totals, fees, and payment options as a unified pre-purchase flow. | request | receipt |
purchase |
Commerce / order | Capture and settle orders once authorization and risk checks have passed, with clear order IDs. | request | receipt |
ship |
Logistics / fulfillment | Encode fulfillment instructions, carrier selection, and tracking into a shared logistics verb. | request | receipt |
verify |
Identity / checks | Perform identity, KYC, eligibility, or policy checks with reusable, machine-verifiable verification receipts. | request | receipt |
A typical e-commerce or payments agent chains multiple Commercial verbs together —
for example:
authorize → checkout → purchase → ship → verify — while keeping the
same schema contracts across runtimes and rails.
In CommandLayer’s reference flows, the client builds a
checkout.request, validates it against the Commercial schema, sends it
into a runtime, and receives a checkout.receipt with trace IDs and
result fields. Later steps reuse the same pattern for
purchase, ship, and verify — only the verb
and result shape change.
As x402 and ERC-8004 adoption grows, these same Commercial schemas slot into x402-compatible payment and agent rails. Semantics stay fixed; routing, pricing, and guarantees live in the Runtime layer.
Commercial v1.0.0 names and schema paths are reserved and stable. Implementations can iterate behind these contracts; breaking changes move to new versions.
Commercial schemas are published under Apache-2.0 and treated as open building blocks for the agent economy. Anyone can implement them; there is no per-schema licensing. Monetization sits in Runtime endpoints, SLAs, and routing — not in who is allowed to speak the verb language.
Future Commercial verbs (refunds, payouts, subscriptions, risk, and more) will follow the same pattern: stable names, versioned schema contracts, and free access to semantics so the ecosystem can converge on one economic vocabulary for agents.
