View schema JSON
The formal JSON schema defining the MSP-1 intent value.
AI-friendly semantics for trusted information.
MSP-1 schema
Declares the purpose, goal, or intended function of an MSP-1 resource, page, section, action, or communication.
Machine-readable structure supporting either a lean intent string or a structured intent object.
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"$id": "https://msp-1.org/schema/intent/intent.json",
"title": "MSP-1 Intent Schema",
"description": "Schema for expressing the declared purpose, goal, or intended function of an MSP-1 resource, page, section, action, or communication.",
"$comment": "MSP-1 v1.0.2 allows both the lean string form and the structured object form. For object form, statement is required. For string form, the string itself serves as the intent statement.",
"oneOf": [
{
"type": "string",
"minLength": 1,
"description": "A clear natural-language statement describing the purpose or intended function of the resource."
},
{
"type": "object",
"properties": {
"statement": {
"type": "string",
"minLength": 1,
"description": "Primary intent declaration, expressed as a clear human-readable statement."
},
"category": {
"type": "string",
"enum": [
"informational",
"transactional",
"navigational",
"instructional",
"persuasive",
"creative",
"analytical",
"warning",
"meta"
],
"description": "Optional categorization of the type of intent for structured interpretation."
},
"audience": {
"type": "string",
"description": "Optional definition of the intended audience."
},
"scope": {
"type": "string",
"description": "Defines what the intent applies to, such as a site, page, section, action, or communication."
},
"motivation": {
"type": "string",
"description": "Optional explanation of why this intent exists."
},
"interpretiveFrame": {
"type": "string",
"description": "Optional interpretive framing to help agents contextualize the intent statement."
},
"priority": {
"type": "string",
"enum": ["low", "medium", "high", "critical"],
"description": "Optional priority level for the declared intent when resolving competing intent signals."
},
"lastUpdated": {
"type": "string",
"format": "date",
"description": "Date the intent was last reviewed or updated."
}
},
"required": ["statement"],
"additionalProperties": false
}
],
"examples": [
"Explain the purpose and structure of the MSP-1 metadata protocol.",
{
"statement": "Teach beginner photographers how to use window light for portraiture.",
"category": "instructional",
"audience": "beginner photographers",
"scope": "page"
},
"Provide foundational understanding of natural and artificial lighting principles."
]
}
The formal JSON schema defining the MSP-1 intent value.
See the conceptual definition of intent, including purpose, scope, audience, and relationship to description and interpretive frame.
The canonical MSP-1 v1.0.2 form for intent may be either a clear natural-language string or a structured object with statement as the required field.
intent should not be confused with description, type, or interpretiveFrame. description explains what the resource is; intent explains what it is for; type classifies what kind of thing it is; interpretiveFrame guides contextual interpretation.