AI disclosure · readiness report

Article 50 readiness report

The same checks the free CLI runs, for up to 10 URLs and 25 AI-generated files, dated and hash-signed with our Ed25519 key, as a PDF and a JSON file you can keep or hand over: $49, once, through Stripe Checkout, with no account. For 30 days after paying, a re-check of the same targets (after a fix, say) is signed too.

Start from the CLI

Name the targets; the command prints the link to pay for exactly those, and reads and sends nothing yet:

$ npx --allow-git=root github:agentwares/agent-disclosure report --site https://your-site.example/ --output generated.png

Repeat --site (up to 10) and --output (up to 25). Files stay on your machine.

How it works

  1. agent-disclosure report --site … --output … names your targets and prints this page's link with their commitment.
  2. You pay $49. The page Stripe returns you to shows a signed token, valid 30 days, for those targets.
  3. You run the report with the token. Both checks run on your machine; only the report's SHA-256, the commitment and the two counts are sent to be signed. It writes agent-disclosure-report-<date>-<id>.json and .pdf.
$ npx --allow-git=root github:agentwares/agent-disclosure report --token <token>

On the same machine the targets are remembered; elsewhere, pass the same --site and --output flags.

What the signature shows

That the report has not changed since it was signed, and when it was signed. It does not show that the findings are true of your site today, or that anything complies: the checks ran on your machine and report what they found. Anyone can check a report with agent-disclosure verify against the key published at /ai-disclosure/report-key.json.

Refunds: our refund policy. The free checks need no payment and print the same findings, unsigned.

The texts, each read on 8 October 2026