Changelog

How versions are numbered and what each one promises: Versioning.

0.3 — 2026-10-27 (draft: search profile)#

Draft, added beside the stable 1.0 parts without changing them.

• Search profile of the MCP binding: one read-only tool intent_search_offers (statement, optional country, category, limit) returning a search-result (schema under /schemas/0.3/): offers on the holder's host, no seller contact, and suggestIntent to turn an empty or thin answer into an intent with the same holder.
• Declared as "search" in profiles (accepted by the 1.0 descriptor schema without change); registry check §5 step 4 (draft).
• Forwarding §9 (draft): search through a forwarder — answers per holder, never merged or re-ranked.

1.0 — 2026-10-27 (stable: consent-link profile, discovery and registry, forwarding)#

Declared stable after four holders in two countries and two categories, the registry and the reference forwarder had run the consent-link profile in production. No field, tool or rule was renamed, removed or made stricter for a holder. A 0.2 holder stays conformant without a change.

• Stable: the consent-link profile of the MCP binding (rules 1–9, exact interface), the Discovery and Registry chapter and the Forwarding chapter. The other parts stay draft (see the table in Versioning).
• Holder descriptor and registry: specVersion is "1.0"; "0.2" stays valid for the whole 1.x line. Schemas moved to /schemas/1.0/; the 0.2 schemas stay online unchanged at /schemas/0.2/.
• Profiles: profiles in a descriptor accepts any lowercase profile name (in 0.2: only consent-link or an x- value), so that a later profile can be declared without a new major version. A receiver ignores a profile it does not know; the registry still requires at least one profile it can check.
• Registry user agent: IstoIntentsRegistry/<version>; a holder SHOULD NOT depend on the version part.

Migration: none required. To declare 1.0, set "specVersion": "1.0" in the descriptor and add "1.0" to a server's specVersions.

0.2 — 2026-10-21 to 2026-10-25 (draft)#

• Discovery and Registry chapter: holder descriptor, registry.json, automated check, statuses, registry_find_holders (2026-10-21).
• Forwarding chapter and the reference forwarder at istointents.com/mcp (2026-10-24).
• Exact interface of the consent-link tools; consentUrl and matches on the holder's host; forwarding terms (2026-10-25).
• consentUrl MUST NOT contain the intentCode; the x-isto-test header; refusing undeclared arguments; the trial run before forwarding; the reference holder; the x-isto-forwarder header with a key per host (2026-10-25).

0.1 — 2026-10-11 (draft)#

• Interface specification: Intent, Offer, DemandSummary, Consent; MCP and AP2 bindings.
• Consent-link profile of the MCP binding (addendum, 2026-10-11).