The economic contract layer of CommandLayer — verbs and schemas for payments, settlement, fulfillment, and verification. Commercial is the commerce-oriented extension to the canonical contract model: stable request/receipt schemas first, runtime execution metadata second. All schemas are permanently free; monetization lives in execution, not in the verb language.
/schemas/v1.1.0/commercial/<verb>/requests/<verb>.request.schema.json/schemas/v1.1.0/commercial/<verb>/receipts/<verb>.receipt.schema.json
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. It extends the same contract model used across CommandLayer, building on Commons semantics while preserving a commerce-oriented compatibility shape where that is useful.
authorize, checkout, purchase, ship, verify. Standardized shapes make these flows easier to route, audit, and compose across providers.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 links are stable for Commercial extension v1.1.0. Future Commercial majors will ship as new versions under /schemas/vX.Y.Z/commercial/... — early adopters can keep targeting v1.1.0 without churn.
| Verb | Category | Purpose | Request | Receipt |
|---|---|---|---|---|
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. View Base registration ↗
As x402 and ERC-8004 adoption grows, these same Commercial extension schemas slot into x402-compatible payment and agent rails. Schemas remain public and portable; routing, pricing, guarantees, and settlement live in the Runtime layer.
Commercial extension v1.1.0 is an intentionally current compatibility surface, not a forgotten branch. Names and schema paths are reserved and stable. Implementations can iterate behind these contracts; breaking changes move to new versions.
Commercial extension 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. Future Commercial extension 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.