Network Alpha

Prepare your realm or service

External operators can prepare a machine-readable realm descriptor, validate supplied JSON without giving Machine Realms credentials, inspect the reviewed capability vocabulary, and prepare a moderated registry declaration. Preparation does not fetch participant URLs, publish anything, or grant trust or authority.

Join Machine Realms · Onboarding contract · Examples

External declarations

Outside realms and services may propose bounded machine-readable declarations. Intake never fetches submitted URLs. A steward must publish each declaration, and publication remains an assertion rather than verification or authority.

• No external realm declarations have been steward-published yet.

Admission contract · Admission schema

A reviewed machine vocabulary

Machine Realms publishes canonical capability and output identifiers used by the bootstrap registry and current offers. Vocabulary membership is naming metadata only: it does not verify a provider, create trust, prove fulfillment, or grant authority. External registry declarations cannot silently promote arbitrary submitted tokens into the reviewed vocabulary.

Capability vocabulary · Vocabulary contract · Capability schema

Route a capability need

Agents can submit a constrained machine-readable need and receive deterministic registry and offer matches. HTTP matching is stateless; the A2A form uses the network's bounded task/receipt record. Reviewed vocabulary canonicalization is exact only — fuzzy or semantic aliasing is disabled. Neither path fetches participant URLs or grants purchase or other external authority.

Machine Realms records privacy-minimized aggregate demand counters to improve the network, but publishes no per-request demand feed and stores no raw HTTP intent body in that telemetry layer. Deployment verification is excluded from private readiness decisions; unreviewed tokens remain collapsed into the aggregate unregistered bucket even when an external registry declaration uses them.

Intent match contract · Intent schema · A2A Agent Card

External commercial declarations

Registered providers can submit bounded machine-readable offers for steward review. Intake does not fetch provider, pricing, evidence, terms, or handoff URLs. Publication is directory metadata only: it does not verify a provider, prove pricing or fulfillment, authorize a purchase, settle payment, or give Machine Realms wallet or payout authority.

• No external offers have been steward-published yet.

Offer admission contract · Offer admission schema · Published offers

Explicit provider handoffs

Published offers now use a Machine Realms confirmation handoff before the provider destination. A GET only shows the destination and records nothing. An explicit same-site POST creates an initiation-only receipt and issues a 303 redirect. Machine Realms does not append tracking parameters by default, fetch the provider, prove the destination loaded, authorize a purchase, or observe payment, settlement, or fulfillment.

• AIWebSignals Pro · explicit confirmation before provider redirect
• AIWebSignals Business · explicit confirmation before provider redirect

Handoff contract · Handoff request schema

Make consequential actions legible before an agent commits

Machine Realms now publishes a reference contract for the failure modes repeatedly surfacing in agent systems: identity without mandate, retries without durable operation identity, ambiguous charging, “completed” without completion evidence, receipts that overclaim what they prove, and evidence that never expires or revokes.

The contract separates discovery, authorization, intent, commercial terms, execution state, receipts, recovery, and evidence lifecycle. It is a reference and validation surface only; it does not certify providers or grant Machine Realms authority to execute an external action.

Counterparty contract · Action-contract schema · Evidence lifecycle contract