Live launch QA · x402

Catch the embarrassing stuff before you ship.

One POST request turns a supported managed-hosting page into a deterministic, developer-ready launch report. No account. No API key. Pay exactly 4¢ in USDC.

15+ checksBase + Solana USDCJSON response
launch-report.jsoncomplete
82/100

LAUNCH READINESS

Almost ready.

One blocker deserves attention.

Canonical URLpass
Mobile viewportpass
!Social imagewarn
×Meta descriptionfail

Completed in 1.4s · 6 links sampled

NO SIGN-UPDETERMINISTICMACHINE-READABLEPAY PER RESULTNO SIGN-UPDETERMINISTICMACHINE-READABLE

What gets checked

A preflight list that never gets bored.

ProofDesk focuses on visible, source-level launch mistakes—the kind that erode trust, spoil previews, or make a page harder to discover.

01

Launch metadata

Title, description, canonical, viewport and language.

02

Share previews

Open Graph, Twitter card, favicon and absolute image URLs.

03

Page structure

H1 count, semantic signals, JSON-LD and labeled-form heuristics.

04

Indexability

Robots directives, status, redirects and accidental noindex.

05

Link sample

A bounded same-host link sample for obvious launch-day breakage.

06

Actionable fixes

Evidence and a direct fix for every warning or failure.

Honest scope: this is an automated source-level preflight, not penetration testing, legal advice, or a complete accessibility certification.

Built for agents and scripts

Evidence in. Opinions out.

Every issue includes severity, the observed evidence, and a concise fix. Stable JSON makes the result easy to gate in an agent workflow, CI job, or launch checklist.

  • Clear pass, warn and fail counts
  • Final URL and redirect visibility
  • Bounded runtime and response size
Open the complete free example →
example-response.jsonJSON
{
  "score": 82,
  "summary": { "pass": 13, "warn": 3, "fail": 1 },
  "issues": [
    {
      "severity": "fail",
      "check": "meta-description",
      "evidence": "No meta description found",
      "fix": "Add a concise description between 120–160 characters."
    },
    {
      "severity": "warn",
      "check": "social-image",
      "evidence": "og:image is missing",
      "fix": "Add an absolute og:image URL for link previews."
    }
  ],
  "disclaimer": "Source-level launch heuristics, not a full WCAG audit."
}

How payment works

HTTP already had a price tag. We use it.

1

POST a URL

The endpoint replies with an x402 payment requirement.

2

Pay 4¢ USDC

Your client settles on Base or Solana. No subscription.

3

Receive the report

The paid request returns the audit as structured JSON.

Need interpretation, not just JSON?

Turn the report into a launch plan.

The assisted review adds a careful second pass and converts the raw findings into the five fixes most worth doing before you announce. It is openly AI-assisted and checked for evidence before delivery.

Public pages onlyScope confirmed firstPay after acceptance
Fixed price$10USDC · Base or Solana
  • 01 Full ProofDesk launch report
  • 02 Evidence check on every blocker
  • 03 Prioritized top-five action plan
  • 04 Concrete copy or markup suggestions
  • 05 One follow-up clarification
Request an assisted audit

No payment is requested until the page and scope are accepted.

Proof you can inspect

Public outcomes, not anonymous praise.

Every example below links to the repository, shipped change, tests, or payment confirmation. AI assistance is disclosed; the evidence is independently readable.

Need a focused JavaScript or TypeScript patch? Scope, base commit, acceptance criteria, and price are agreed before implementation.

Request a scoped patch

One request. Four cents.

Give your next launch a final pair of eyes.

Send an HTTPS page on the temporary managed-host allowlist. Payment is requested automatically through the open x402 protocol.

Declared metadata extraction is also available at $0.01 USDC through POST /api/metadata. It reads server-returned HTML only, without JavaScript rendering or link and asset probes.

Temporary safety boundary: arbitrary custom domains are rejected before fetching, and redirects must remain on the same allowlist. Supported apex domains and subdomains: github.io, pages.dev, vercel.app, netlify.app, webflow.io, framer.website, onrender.com, railway.app, surge.sh, firebaseapp.com, web.app, readthedocs.io, gitbook.io, wordpress.com, myshopify.com, wixsite.com, carrd.co, typedream.app, trycloudflare.com, chatgpt.site, example.com.

POST /api/audit$0.04 USDC
curl -X POST "https://proofdesk-audit-api.konstanta-work-x.chatgpt.site/api/audit" \
  -H "Content-Type: application/json" \
  -d '{"url":"https://example.com"}'

This curl command shows the standard 402 challenge; it does not pay. The checked-in Base buyer client requires explicit 4¢ confirmation and refuses a changed price or receiver.

Run the Base payment example →