Discovery for agent-transactable services

Submit an endpoint

The Service Record is the submission format. Prepare it once for verification and discovery.

One record, one path

The intended submission format is the Service Record itself. The index should not require a second application after verification. Live admission and automated indexing are not operational yet.

Publish. Start with the complete L1 template. Use your own identity, URLs, coverage, pricing, and required capability actions. Serve it at /.well-known/agent-service.json.
Pass preflight, then prepare conformance. Browser checks find structural issues. L2 needs safe, repeated live probes; L3 needs applicable credentials and synthetic transactions.
Become discoverable. The launch design automatically admits eligible L2 records after verification, without a separate form. Failures, stale evidence, or suspension update the index from verification events.

The first operational target is a real verified booking in Spokane. Reference candidates must actually pass their applicable evidence gates before any live L3 label is displayed.

Before you submit

A stable domain and well-known JSON record.All required record fields and capability actions.Documented input/output schemas and safe probe access.Unauthenticated quote and availability where appropriate.Required credentials and a reachable operator contact.

Run browser preflight →Get starter JSON ↓Read the specification

Preparation is available now. Live verification, index admission, and final contracts remain launch work.