Discovery plane

Unknown machines should be able to find us without an introduction.

CommandLayer is built around zero-touch machine acquisition: discover a service, understand its contract, obtain a quote, settle through a supported adapter, invoke the outcome, and verify the resulting execution evidence.

Open machine catalog JSON Read integration docs

Canonical flow

The directory is not the product.

External listings are caches and acquisition surfaces. The authoritative service definition stays with CommandLayer so a listing can be refreshed, revoked, or republished without splitting product truth across ecosystems.

Canonical manifest

Identity, schemas, execution mode, economics, evidence class, endpoints, and adapter metadata originate from one service definition.

Generated adapters

OpenAPI, MCP, ENS, x402, ERC-8004, and future discovery surfaces are generated or mapped from that definition.

Attributed acquisition

Discovery source follows the buyer through manifest read, quote, payment, execution, receipt, and repeat use.

Machine buyer path

From need to verified result.

1 · Discover

Find a service through the owned catalog or an external directory adapter.

source attributed

2 · Understand

Read the request schema, result schema, execution mode, pricing contract, and acceptance conditions.

machine contract

3 · Quote

Request a bounded, expiring, input-bound quote without coupling the canonical contract to one payment provider.

rail neutral

4 · Settle

Use the service's supported settlement adapter when payment is required.

adapter specific

5 · Execute

Run the service graph, providers, state, retries, and acceptance checks.

observable

6 · Verify

Inspect signed execution evidence independently from payment evidence and factual-truth claims.

proof boundary

Current public catalog

Machine-readable before machine-payable.

The public catalog intentionally reports no live paid outcome services until evidence selection is complete. That keeps discovery truthful while the factory foundation is built.

GET /catalog.json

{
  "schema": "commandlayer.catalog.v0",
  "program": "machine-service-factory",
  "status": "evidence-gated",
  "live_services": [],
  "human_catalog": "/services",
  "verification": "/verify.html"
}

Adapter strategy

Go where agents already look.

Discovery surfaces are earned in stages. The factory does not wait for any single registry or naming system to become universal.

Stage A

Owned catalog, canonical HTTP manifest, OpenAPI, ENS where controlled, x402 where appropriate, basic attribution, MCP when mapping is straightforward.

ownedOpenAPIENSx402

Stage B

MCP registries, x402 discovery surfaces, practical wallet/payment ecosystems, and publication verification/refresh.

earned next

Stage C

Selective ERC-8004 publication, 8004scan visibility, ownership proofs, reputation signals, and A2A only when demand warrants it.

service selective

Identity is plural: the same service or agent can simultaneously have an HTTPS endpoint, wallet, ENS name, ERC-8004 registration, platform identity, and other identifiers. CommandLayer does not require one system to replace the rest.