Service catalog

Useful machine services, not a wall of endpoints.

CommandLayer is building a small set of commercially useful outcomes on top of shared primitives. The first paid services are selected by evidence and acceptance contracts—not by domain inventory or developer preference.

Catalog policy

A name is inventory until evidence turns it into a product.

Candidate service identities are deliberately separated from live service claims. A service becomes Live only after its problem, acceptance contract, execution path, economics, and distribution surface are validated.

0paid outcome services publicly declared live
3maximum initial outcome services after selection
1shared factory underneath the catalog
possible buyers without per-buyer onboarding
Outcome candidates

Services that may earn a storefront.

These are candidate problem families for research and selection. They are not claims of availability.

Verify
Validate cryptographic receipt integrity, provenance, and explicit acceptance checks without claiming factual truth.
candidate
Research
Compose retrieval, source handling, synthesis, and evidence into a bounded research outcome.
candidate
Monitor
Observe external state over time and produce evidence when a defined condition changes.
candidate
Document
Ingest, parse, extract, classify, and return structured document outcomes.
candidate
Compare
Normalize alternatives, apply a declared comparison contract, and return a traceable decision surface.
candidate
Lead intelligence
Collect and structure business lead intelligence where source, use, and compliance constraints permit.
candidate
Track
Maintain durable state for an object, event, shipment, record, or recurring process.
candidate
Factory instruments

Primitives support outcomes. They do not drive the roadmap.

Pass-through primitives can be useful for composition, testing, or machine acquisition, but the business is not measured by how many thin wrappers it can publish.

Crawl / Fetch

Retrieve external resources while accounting for provider and origin-side content costs.

primitive
{ }

Parse / Extract

Turn raw inputs into normalized structured data used by composed services.

primitive
Aa

Transcribe / Classify

Convert media or text into machine-usable representations and labels.

primitive
Permissioned actions

High-consequence actions stay gated.

Names such as purchase, sign, refund, payout, authorize, KYC, and other state-changing services are not launch shortcuts. They require authorization scopes, spend limits, replay safety, recovery paths, and service-specific compliance before they can become public products.

purchase · gatedsign · gatedrefund · gatedpayout · gatedauthorize · gatedKYC · gated
Catalog truth rule: this page will never label a service Live merely because an ENS name exists, a handler compiles, or a payment adapter is available.