Purpose

MSP-1 defines a site-level discovery resource located at /.well-known/msp.json. The purpose of this resource is to provide a stable, machine-readable declaration of site identity, intent, provenance, authority, trust posture, and protocol version.

Registration of the msp.json well-known URI suffix would support consistent discovery across agents, validators, crawlers, implementation tools, and other automated systems that choose to recognize MSP-1.

URI suffix

msp.json

Canonical path

/.well-known/msp.json

Example absolute URL

https://example.com/.well-known/msp.json

Intended usage

Site-level discovery of MSP-1 metadata declarations.

Media type

application/json

Specification

MSP-1 Core Specification

Namespace

MSP-1 Namespace

Schema hub

MSP-1 Schema Library

Change controller

MSP-1 Protocol / Mark Semantic Protocol project

MSP-1 discovery is intended to be deterministic and non-inferential. Consumers should use the canonical path /.well-known/msp.json when attempting to locate site-level MSP-1 metadata.

Consumers should not rely on alternate filenames, guessed paths, or pattern-based probing to locate MSP-1 declarations. Where an inline page-level MSP-1 declaration includes a discovery object, its wellKnown value should resolve to the canonical endpoint.

Canonical discovery object

{
  "discovery": {
    "wellKnown": "/.well-known/msp.json",
    "canonical": true
  }
}

The msp.json resource is a JSON document containing a site-level MSP-1 declaration. It may reference MSP-1 schemas and namespace terms, but the resource itself is intended to remain directly readable as JSON.

Page-level MSP-1 declarations may also be embedded inline in HTML as JSON-LD using <script type="application/ld+json">. Inline page-level usage is complementary to the site-level well-known resource and does not replace it.

The MSP-1 well-known resource is declarative only. It does not authenticate a site, authorize access, grant permissions, enforce behavior, or establish trust by itself.

Consumers must treat MSP-1 declarations as claims that may be evaluated against observable site content, provenance, external evidence, and other applicable trust signals. A valid MSP-1 document indicates structural conformance, not guaranteed truthfulness.

Implementers should avoid publishing sensitive operational details, credentials, internal system information, private endpoints, or any information not intended for public machine-readable access.

The /.well-known/msp.json resource should contain only public site-level declarations. It should not expose private user data, personal information that is not already public, authentication details, unpublished editorial processes, or internal business information.

MSP-1 is intended to clarify the meaning, provenance, and authority posture of public resources. It is not intended to create a channel for user tracking, behavioral profiling, or disclosure of non-public operational data.

MSP-1 requests recognition of msp.json as the well-known URI suffix for Mark Semantic Protocol discovery. The intended posture is conservative: the registration supports deterministic discovery but does not imply endorsement, verification, ranking, authentication, or special treatment by any consuming system.

Consumers remain responsible for evaluating MSP-1 declarations according to their own trust, safety, provenance, and content interpretation policies.