Added5
The command line's wallet now pays uploads, extends files, sends, swaps, gifts, and reshapes or hands over storage resources.
Every one of these signs with the wallet the NMTS key derives and runs under the wallet unlock above. Each prints a review with the fee measured by a dry run and signs only after --yes. A hand-over moves the resource alone; the files stay encrypted to this account.
From the command line you can erase files for good, sign a device out, accept a new version of the Terms, and delete the account, each with the NMTS key beside the API key.
An API key on its own still cannot do any of these. The code's proof is the same one the browser presents when you sign in, and the erase asks for the same sentence the browser asks for.
A standing share of every WAL payment can go to the developer as a gift: nmts tip sets it, the default is 0, and the agreement is asked once.
The share lives in your encrypted file list, so the server never learns it. After an upload paid by wallet or an extension, that share of the WAL just paid goes to the published address and the command prints the amount and the transaction id. A gift buys nothing and is not refundable; the browser's version of this setting is not switched on yet.
Two new pages: /dev for people who build on NMTS, and /ai for people who hand their account to an AI agent.
The developer page says what NMTS is and can do, lists the CLI and the packages, and offers a prompt to copy that makes an AI install the CLI and read its guide. The AI page signs you in once and leaves you with the text to paste, with the API key made on the spot.
Sponsored storage is checked against the chain every day on a sample, a confirmed loss is posted on the notice board, and you can ask whether every file you keep is served right now.
A loss is recorded only when the chain answered that the object is gone, never when it said nothing. Which credits come back for a lost file is not decided yet.
Changed3
The command line sorts every act into five risk tiers and four modes, so an AI agent running it cannot sign, gift or erase without a person's unlock.
Until now each command decided on its own what to ask and what to refuse, and the answers did not match. The tier of an act (none, low, medium, high, ultra-high) and the mode the person chose (default, auto-low, auto-high, skip-permissions) now decide together, before the command loads; high acts wait for an unlock a person types at a terminal, with a scope, an expiry and a spending ceiling. The agent guide became one document per command, read with nmts help. The tiers do not apply to the browser.
Every credit-paid file holds 64 credits as a deposit, and an upload that never certified gets its credits back within the hour.
The deposit is spent on an early release and returned when the term ends. An upload that registered on the chain but never certified used to keep its credits taken; an hourly round now returns them.
The notice board, the Terms and the Privacy Policy are served as plain text for programs, and the site describes itself to crawlers in llms.txt and robots.txt.
Fixed1
A sign-in lockout counter now falls back to zero after a window nobody used, instead of staying raised.