Start with a complete record
Preparation is available now. Live applications, scheduled probes, credential checks, badges, and automatic index admission are not operational in this preview.
- Publish your record. Serve
application/jsonat/.well-known/agent-service.json, directly or through a stable redirect. Replace every sample identity and action URL. - Prepare the probes. Document input/output schemas and make required actions callable. Use consented sandboxes for booking and cancellation tests.
- Prepare credentials. Supply the applicable license, insurance, identity, and jurisdiction evidence when the program opens.
- Keep evidence current. Plan renewals, failure response, monitoring, and outcome reporting before relying on a level.
The target is record publishing in under an hour. L1→L2 should require no manual handoff once repeated probes and policy requirements pass. “Automatic” does not mean an instant unsupported verification claim. At launch, L2 admission should create an indexed listing without another application form.
Check your record in the browser
Checks run locally: Draft 2020-12 structure and formats, required actions for specified capabilities, and price-range ordering. This does not verify credentials, ownership, signatures, external action schemas, or current freshness.
Ready for a record. Maximum size: 256 KiB. Your input is not uploaded.
Before live verification
Example vertical requirements
| Vertical | Draft planning examples |
|---|---|
| Home services | Trade license where required; general liability coverage; identity; domain control. |
| Legal | Bar admission in each claimed jurisdiction; identity; domain control. |
| Beauty | Professional licensing where required; coverage; identity; domain control. |
Exact requirements depend on published extensions. Missing extensions are a gap to resolve, not permission to imply credentials were checked.
Start at L1
The intended L1 entry point is free. Final pricing will be published before launch. Indicative timelines range from hours or days for integration fixes to days or weeks for authority checks; these are planning examples, not service commitments.