Home / Docs / Trust and verification
Trust and verification
How tasks are signed and logged, and the commands to inspect a task, verify the public log, review new task types and report a task.
You should be able to check what runs on your machine rather than take our word for it. Every task is signed, every task is in a public log, and the worker has commands that let you read and check each one. The trust and transparency page lists the rules and the keys. This page is the how-to.
How tasks are signed and logged
- Task types live in task packs: prompt templates, tool permissions and checkers. Each pack release is signed with a SpareTokens release key, and its public key ships inside the worker.
- The release key certifies a separate task key. The task key signs every task: the pack and version, the template, the parameters, the prompt and the budget.
- Every task is written to a public, append-only, hash-chained task log with a Merkle tree head signed by the task key.
- Before a task runs, the worker checks the signature, that the template belongs to a signed pack it trusts, that the task is within the scope rules, and that it appears in the log. If any check fails the task is refused and not run.
Read a task before it runs: sparetokens inspect
sparetokens inspect 1234
Prints the task in plain language: the goal, the exact prompt the AI receives, the tools and network hosts it may use, the budget cap, how the result is checked, and which signatures and which log entry were verified. If a check fails it prints NOT VERIFIED, exits with status 3 and suggests a report. The same task is also public at /tasks/1234 on this site.
Check the whole log: sparetokens verify-log
sparetokens verify-log
sparetokens verify-log --mirror https://sparetokens.ai/data/tasklog
Downloads every log entry and checks the hash chain, that the entries hash to the signed Merkle root, and that the head is signed by the certified task key. It prints a one-line summary on success, or FAILED and a reason with exit status 3. The default reads from the coordinator you are registered with. --mirror reads the public copy on this site, so you can check it without an account.
Be asked first: sparetokens review
sparetokens review --on
sparetokens review --allow code_fill.abundant_count
sparetokens review --deny literature_status
sparetokens review --forget literature_status
Review mode asks you before each new task type runs for the first time, then remembers your answer. A scheduled run with nobody at the keyboard does not run a new type. It leaves the task and tells you how to look at it. --off turns review mode off. With no flags, the command prints the mode and your saved answers.
See what was sent: sparetokens history --show
sparetokens history --show 1234
Prints everything the worker sent to the AI and everything it received back for that task. Transcripts are kept on your machine for 30 days and are never uploaded. Only the result and the usage numbers go to the coordinator.
Report a task: sparetokens report
sparetokens report 1234 --reason wasteful --text "The examples look odd"
Reasons are harmful, not-research, privacy, wasteful, broken and other. The report goes to the public report queue with links and email addresses removed from the text, and every report gets an answer. The text itself is shown once we have reviewed and approved it; until then the queue shows the reason, the state and our response, with a note that the text is awaiting review. There is no web form yet, so the command line is the way to report. Please do not put keys or personal data in the text.
Public data
The same data the site pages use is public JSON, refreshed hourly.
- /data/trust.json: signing status, the release and task keys, the scope rules and the signed log head.
- /data/tasklog/head.json: the signed log head. Entries are at
/data/tasklog/entries/N.json, 1000 per page. - /data/task-types.json: every task type with its checker and quality numbers. A number is null when there is no data yet.
/data/tasks/N.json: 100 tasks per page, each with its signed envelope and log entry number.- /data/reports.json: the public report queue.
Task pages are at /tasks. See also verification for how results are checked and the CLI reference for every flag.
Edit this page on GitHub: available when the repository opens.