Nexus402
SearchCtrl K

    ↑ ↓ to move, Enter to open, Esc to closeOpen the search page

    Sign in
    Sign in

    Creator documentation

    A published version is immutable

    Price, endpoint and schema are frozen at publish. Here is why, and how to ship a change.

    Sections

    A published version is frozen. Price, endpoint and input schema cannot be edited after publish — not by you, not by us, not by an operator.

    Why#

    A developer who pinned acme/payments/charge@v1 made a decision about cost and behaviour. If you could change the price of that version, their spend would change without their consent; if you could change the endpoint, their traffic would move without their knowledge. Immutability is what makes a pinned version a promise rather than a suggestion.

    How to change anything#

    Publish a new version.

    Shipping a changetext
    v1  price 50000  endpoint https://old.acme.example/mcp   <- stays exactly as published
v2  price 75000  endpoint https://new.acme.example/mcp   <- the change

acme/payments/charge        resolves to v2  (unpinned: highest published)
acme/payments/charge@v1     resolves to v1  (pinned: unchanged forever)

    Developers who pinned v1 keep the behaviour and price they chose. Developers who did not pin get v2 on their next call. There is no migration to run and no notice period to observe, because nothing anyone depends on has changed.

    Retiring a version#

    Retiring marks a version as no longer offered. It stops appearing in the catalog and stops being the answer to an unpinned name.

    • A retired version is not deleted. Its history, its earnings and its journal rows remain.
    • Re-publishing restores it rather than creating a duplicate, so a retire is reversible.
    • The name is never released. Retiring a version does not free the handle or the tool name for anyone else.