Local proof report + optional $149 written audit

AgentProof

Real checks, screenshots, CI status, and stop rules for one public repo, PR, or demo. Free when you run it yourself; paid when you need an outside proof packet.

Use the free local report when it answers the question. Buy only when you need an outside written proof packet for launch, handoff, posting, or PR review.

Report to buyer path

One AP reference follows the proof packet.

The demo report already emits a buyer-safe handoff with source artifacts, a report reader URL, checkout, intake, handoff, and sample delivery links tied to AP-0BQ7O9S.

AP-0BQ7O9S - agentproof-demo-app - 82/100 Source artifacts: index.html, results.json, proof-card.svg, report-handoff.md
1 - report Open the machine-readable run. Report reader
2 - checkout Carry the same audit ref into payment. Targeted checkout
3 - handoff Keep public inputs and boundaries attached. Buyer handoff
4 - delivery Compare against a written output sample. Sample deliverable
Release proof

Installable outside this repo, not just dogfooded locally.

Open v0.1.7 release

Current release: v0.1.7

The GitHub release ships nicdunz-agentproof-0.1.7.tgz with a tarball install-smoke pass before buyers are routed to the paid proof packet.

Outside repo proof

The consumer demo installs dicnunz/agentproof@v0.1.7 from a separate repository and publishes an AgentProof report artifact.

View outside repo workflow

Outside PR proof

The same released action runs on a public pull request, proving the maintainer-review path before the $149 async audit pitch.

View outside PR proof

Current public signal snapshot

Traffic is real. Intake is still the bottleneck.

Latest loop: 108 GitHub views, 47 unique viewers, 3,755 clones, and 1,169 unique cloners with no paid intake or reply-safe lead. The right next move is a sharper owned buyer path, not unsolicited contact.

20 public high-fit signals
4 quantified review-load examples
27 low-proof PRs in sample
0 reply-eligible leads
Cloned the repo?

Use it free, or pay for the proof packet.

If you already cloned AgentProof, the free route is local and self-serve. The paid route is for when you want the report generated, interpreted, and turned into a written launch or review handoff for one public repo, demo, or PR.

Add one public target to generate scoped links.

Free local path

Run AgentProof yourself and open the generated report locally. No API key, no telemetry, no upload.

npm install
npm run build
node dist/src/cli.js audit . \
  --no-browser
open agentproof-report/index.html
Done-for-you path: $149

Buy the async mini-audit, then send one public target through the handoff. I return the AgentProof report, score, blockers, first fixes, and stop rules.

Buy only if the proof pass is cheaper than the review churn or launch risk it replaces: $149 breaks even after 3 hours saved at $50/hour, or 1.5 hours at $100/hour.

Best fit

Public AI-built app, demo, local web tool, or public PR where the claim needs proof before launch, handoff, posting, or review.

Deliverable

AgentProof HTML report, machine-readable JSON, route, PR, or DX evidence, first fixes, and a written launch/review-proof summary.

Boundary

No calls, meetings, secrets, credentials, private customer data, private repo access, or outcome guarantees.

What the report catches

1. Buy

Start with the AgentProof checkout handoff so the AP audit reference, public target, and post-payment packet stay attached through Gumroad.

2. Send public inputs

Use the buyer handoff or intake builder, then email the public repo or PR from the same address used at checkout, or open the GitHub intake without receipt details.

3. Get the report

Delivery target is 72 hours after complete safe inputs. The result is written and async.

What to send

Repo or demo

A public repo URL, public PR URL, safe local start command, or deployed demo link.

Proof goal

The routes or claims that need evidence before you launch, post, or hand off.

Safe inputs

Only public/test data. Never send secrets, customer data, payment data, or credentials.

For maintainers

Use one public PR URL to get CI status, changed-file scope, review-risk signals, maintainer objection flags, and a stop rule.

Use the AI PR proof checklist when a PR needs evidence before review.

For builders

Use one public repo or demo to get route proof, screenshots, command checks, DX gaps, broken-link findings, first fixes, and launch stop rules.

Need proof for one AI-built app?

Keep it public, safe, scoped, and async.