Machine-readable first
The planned discovery flow is search_services followed by get_service_record. The resulting record describes how to transact directly with the service. The index is not the payment rail or the operator.
MCP integration is planned, not installed or published. The previously proposed npm package is not available; do not run a speculative package name. A reviewed installation command will be published when a real integration exists.
Proposed tools
{
"name": "search_services",
"description": "Search endpoint candidates by capability and location. Proposed API; not operational.",
"inputSchema": {
"type": "object",
"properties": {
"capability": {"type": "string", "description": "Specified node or dotted prefix."},
"location": {"type": "string"},
"level_min": {"type": "integer", "minimum": 1, "maximum": 4, "default": 1},
"limit": {"type": "integer", "minimum": 1, "maximum": 50, "default": 10}
},
"required": ["capability"]
}
}
{
"name": "get_service_record",
"description": "Retrieve an endpoint's full Service Record. Proposed API; not operational.",
"inputSchema": {
"type": "object",
"properties": {"endpoint_id": {"type": "string", "description": "Reverse-DNS identifier."}},
"required": ["endpoint_id"]
}
}
llms.txt
Endpoints should publish plain-language capabilities and a link to their record. This preview's llms.txt explicitly describes what is available.
# Example Service
Illustrative deck staining in Spokane, WA.
Service Record: https://example.com/.well-known/agent-service.json
Capabilities: home.exterior.deck_staining
Specification: https://agentserviceschema.org
The well-known discovery contract
Serve https://<endpoint-domain>/.well-known/agent-service.json, directly or through a stable redirect. Use application/json. Keep the URL stable and update record_updated_at when the record changes. Validate against the core schema and ignore unknown fields when consuming records.
Domain control uses an appropriately bound verifier challenge or the domain's record. Publishing is the submission format; actual discovery automation is not live in this preview.
Check evidence before a transaction
Select a trusted verifier independently. The planned program key URL is https://verifiedserviceschema.org/.well-known/jwks.json, currently empty. A schema-valid record, self-declared L3, copied badge, or untrusted signing key is not proof.
With trusted keys already obtained, check ES256 signatures, issuer, endpoint binding, capabilities, and expiry offline. Current suspension or revocation requires fresh status information. Attestation guidance.