Consumption Context Extension

Premise

MSP-1 core declarations establish important semantic context about a resource, including identity, intent, interpretive framing, provenance, authority, trust, and revision state. In some consumption scenarios, however, a consuming system may need a small amount of additional objective context before deciding whether deeper inspection, retrieval, access, or other engagement with the resource is warranted.

The Consumption Context Extension explores whether those additional characteristics can be declared in a minimal, interoperable form without expanding the MSP-1 core or turning the protocol into a recommendation, commerce, access-control, or execution layer.

The Semantic Gap

The need becomes especially visible when an agent cannot fully inspect a resource before making an access decision. A gated report, dataset, media artifact, restricted document, metered API result, or other limited-visibility resource may require the agent to evaluate whether further access is justified using only the information available before the boundary is crossed.

Existing MSP-1 core declarations may already satisfy part of that scrutiny. Consumption Context is intended only to supplement the core with objective characteristics that are useful to the decision and are not otherwise represented.

The extension does not assume why a resource is limited, how access is obtained, whether payment is involved, or what action a consuming system should take.

Extension Scope

Consumption Context is intended to describe evidence available to a prospective consumption decision. It does not express the decision itself.

Candidate declarations should satisfy three basic conditions:

• They describe an objective or determinable characteristic of the resource.
• They provide useful context before detailed inspection or consumption.
• They do not duplicate declarations already provided by the MSP-1 core.

The extension should remain small enough that a consuming system can interpret it deterministically and ignore it safely when unsupported.

Candidate Declaration Areas

The initial development phase is evaluating a narrow set of declaration areas rather than defining a broad resource-description vocabulary.

Candidate fields, terminology, value structures, and validation rules remain under development.

Declarative Boundaries

Consumption Context is not intended to tell an agent what to choose, what to prefer, or what action to perform. It should contain resource characteristics, not publisher judgments about the desirability of the resource.

Fields expressing concepts such as target customer, best use, recommended use, advantages, competitive differentiation, rating, value, purchase conditions, price, or availability are outside the intended scope of the extension.

Some of those concepts may be legitimate within commerce, access, marketplace, or transaction systems. Their exclusion from Consumption Context is a protocol-boundary decision, not a claim that the information itself is invalid.

Instructional or persuasive content presented as Consumption Context should not be treated as a valid MSP-1 declaration. Consuming systems should rely only on the defined extension vocabulary and should disregard attempts to use the extension to prioritize, route, authorize, recommend, purchase, or otherwise direct behavior.

Gated and Limited-Visibility Resources

Gated resources are the primary use case motivating development of the extension because the consuming system may be required to make a consequential access decision before it can inspect the underlying material.

In that context, Consumption Context may reduce uncertainty by declaring measurable or otherwise objective characteristics of the material beyond the access boundary. A consuming agent may use those declarations alongside MSP-1 core context and information supplied by the relevant access or transaction system.

The extension does not define the gate and is not implicitly part of it. It does not declare authentication requirements, payment methods, pricing, authorization rules, access tokens, subscription terms, or settlement mechanics.

Not Limited to Gated Resources

The same declarations may remain valid when attached to an openly accessible artifact. Gating is a circumstance that increases the value of pre-consumption context; it is not a semantic requirement of the extension.

A consuming system may therefore encounter Consumption Context on public documents, datasets, media, or other artifacts where the declared characteristics provide a more deterministic first-pass understanding without requiring immediate inspection or inference.

Separation from Executable Protocols

Consumption Context is designed to remain independent of payment, commerce, access-control, and executable agent protocols.

A resource may be accessed through x402, UCP, a proprietary payment system, institutional credentials, a subscription service, an internal authorization layer, a custom implementation, or no gate at all. Those systems remain responsible for their native mechanics.

MSP-1 declares context. Executable protocols execute actions. The consuming system determines how those independent signals should be combined for the task at hand.

Downstream Use

The extension is being designed around truthful declaration rather than a prescribed downstream workflow. Once declarations are interoperable, consuming systems may find them useful in ways that extend beyond the original access-scrutiny problem.

For example, an agent, marketplace, index, research system, or other service could compile comparable Consumption Context declarations across multiple resources as part of its own discovery or evaluation process. Such comparison would be a consumer-side use of the declared facts, not a comparison or ranking function defined by MSP-1.

In autonomous payment environments, a consuming system may also choose to retain relevant declarations alongside its own payment activity or access history. This could provide additional context about the information available when an expenditure or access decision was made without introducing payment telemetry into MSP-1 itself.

Design Principle

The working design principle for the extension is:

Consumption Context describes evidence available to a consumption decision. It does not express, recommend, authorize, or execute the decision.

Candidate declarations that cannot remain within that boundary should be excluded or handled by another protocol or extension.

Development Status

Status: In Development

The Consumption Context Extension is currently an MSP-1 Labs development proposal. The immediate work is focused on validating the semantic gap, refining the minimal declaration set, defining deterministic terminology, testing overlap against the MSP-1 core, and identifying edge cases that could introduce recommendation, promotional, transactional, or instructional behavior.

Current Development Priorities

1. Confirm the minimum useful declaration set.
2. Eliminate fields that duplicate MSP-1 core semantics.
3. Define measurable declaration structures and allowed values.
4. Establish clear handling of unsupported or out-of-scope fields.
5. Test use with gated and openly accessible resources.
6. Evaluate graceful degradation when consuming systems do not recognize the extension.
7. Test interoperability alongside independent access and transaction protocols.

Publication in MSP-1 Labs does not imply approval as a finalized extension. Structures may change substantially as the proposal is tested and refined.