Inspect your fleet
Browse saved local records, filter the view and open a record's details. Stored verification flags and ABI hints are not fresh checks against a chain.
Inspect your fleet. Shape your next asset. Keep the next action explicit.
The mintrr command line connects you to the engine. Its optional terminal workbench gives local records, draft fields and review notes a place to live together.
Fleet records, a draft editor and its review belong to the same workspace. They do not share the same authority.
Example: a loyalty asset
A matching preview is required. Nothing on this page has been validated or saved.
The workbench makes those boundaries visible. It does not turn a local plan into a deployment.
Browse saved local records, filter the view and open a record's details. Stored verification flags and ABI hints are not fresh checks against a chain.
Choose a first-party template, fill the basic fields and request a no-write preview. Read the issues and limits before deciding what to keep.
Export revalidates the reviewed draft and creates a local plan file without replacing an existing file. Generation and compilation remain separate operations.
The ordinary CLI remains the engine and the fallback. Explore a command's help before using it; copying an example here never runs it.
Use plain output when an interactive terminal is unavailable. Use JSON output when another program needs the saved fleet data.
mintrr --helpmintrr manage list --jsonmintrr tui --plainmintrr draft --helpThe workbench has no signing, broadcast, payment or AI controls. Its Create flow ends at an explicitly exported local draft. Schema checks are not proof of feature implementation, wallet control, legal compliance or deployment.
Separate CLI execution paths retain their own review and human-confirmation requirements. Nothing on this overview page connects a wallet or executes a command.