Tools · Builder

MSP-1 Declaration Builder

Create a minimal, schema-valid MSP-1 declaration without hand-writing JSON. The builder walks through each declaration step by step and shows the generated output live as you type. It produces a page-level JSON-LD block for your page's <head> and a site-level msp.json for your /.well-known/ directory.

MSP-1 Aligned · 1.0.2 msp-1.org/tools Runs entirely in your browser — nothing you enter leaves this page

1 · Scope
2 · Identity
3 · Meaning
4 · Trust & provenance
5 · Review & output

What are you declaring?

A homepage or root URL should normally carry both declarations. An interior page usually needs only a page-level declaration.

Site and page — recommended for a homepage Generates the site-level msp.json and a page-level JSON-LD block for the root page. Page only A JSON-LD declaration for one interior page. Assumes a site-level declaration already exists. Site only Just the /.well-known/msp.json discovery file.

Declaration status Initial declaration The first MSP-1 declaration for this scope. Revision starts at rev-1 / 1.0.0. Updating an existing declaration Amends a published declaration. You supply the next revision number and revision version.

Identity

This step establishes the required identity fields for the selected declaration scope. Optional naming and canonical details should be declared only when they carry useful signal.

Site

Site URL required The root URL, e.g. https://example.com. The site id is derived automatically.

Enter a full URL including https://

Site name required A plain string — the schema does not accept an object here.

Site name is required.

Page

Page URL required The full URL of this page. Also used as the page id and canonical URL unless you override the canonical below.

Enter a full URL including https://

Page name Optional. A human-readable name for the page, emitted as a plain string.

Canonical URL Optional override. Leave blank to use the page URL.

Meaning

Declare only what a capable model could not infer on its own. If a field would just restate what the content makes obvious, leave it blank — absence returns the agent to normal inference.

Site

Site description One or two factual sentences. Emitted as a plain string.

Site intent Why the site exists, as a plain string.

Page

Short description A concise factual summary, emitted as description.short.

Intent statement Why this page exists — the purpose an agent cannot see from the content alone.

Intent category

Interpretive frame How this content should be read — e.g. that it is opinion, satire, historical, or provisional. Skip it if the framing is self-evident.

Frame category

Trust & provenance

Conservative defaults are preloaded. Raising a trust claim above its evidence undermines the declaration — and the protocol — more than a modest claim ever could.

Applies to each declaration

Provenance type

Provenance confidence

Trust level Defaults to medium. Only raise this when independent evidence supports it.

Verification level A form cannot verify anything, so this builder emits self-declared only.

Revision notes Optional. Leave blank for the standard initial-declaration note.

Add author Only when a responsible author or organization should be named for this page.

Author name

Author type

Add reviewer Only if the declaration was actually reviewed. Name and type are both required by the schema.

Reviewer name required if enabled

Reviewer type required if enabled

Role Optional, e.g. "Managing editor".

Add authority Only when a real responsible entity stands behind the content. Never invent one.

Authority name required if enabled

Authority type required if enabled

Review & output

Structural checks applied by the builder. This is a first draft — review the high-signal fields (intent, interpretive frame, trust) before publishing.

Page-level declaration (JSON-LD)

Paste the block below into the page's <head>.

Site-level declaration (msp.json)

Save as /.well-known/msp.json at the site root. It must be publicly accessible and return HTTP 200.

Run the output through the MSP-1 Validator as a final structural check before publishing.

Live preview

Updates as you type. Empty optional fields are omitted from the output — absence is a valid state in MSP-1.