Choose the evidence you need.

Acceptance · 0.299 USDC

Up to three distinct public pages on the same origin. Up to ten requirements across those pages, identified by an ID, a zero-based page number, a CSS selector and expected text. Each page gets desktop and mobile rendering evidence. Requirement assertions run in mobile Chromium.

{
  "package": "acceptance",
  "url": "https://your-site.com/",
  "pages": [
    "https://your-site.com/",
    "https://your-site.com/contact"
  ],
  "requirements": [
    {
      "id": "contact-heading",
      "page": 1,
      "selector": "h1",
      "text": "Contact"
    }
  ]
}

The result contains each requirement’s passed, failed or untested status and its observed evidence. Missing evidence stays untested. If any page cannot complete, the package is not settled.

Journey · 0.999 USDC

One staging origin and its allowed write paths must already be configured by the operator. Buyers cannot grant that permission themselves. Up to ten fill, click and expect steps; the last step must be an expected visible outcome. Live purchase controls and unapproved network writes remain blocked.

{
  "package": "journey",
  "url": "https://your-approved-staging-site.com/form",
  "mode": "sandbox",
  "journey": [
    {
      "action": "fill",
      "selector": "#email",
      "value": "fixture@example.com"
    },
    {
      "action": "click",
      "selector": "#submit"
    },
    {
      "action": "expect",
      "selector": "#result",
      "text": "Confirmed"
    }
  ]
}

This example requires staging setup; it is not an approved target. Authentication and customer-configurable staging access are outside this launch. A visible assertion alone does not prove business-side fulfilment or payment completion.

Use the same payment helper

Pass the selected package and its inputs to buyFinalSentryBrowserReport with your existing signer and durable lock, load and save callbacks. The helper requests the exact quote, enforces the selected package’s price ceiling and preserves the original authorization for recovery. Never sign a replacement while a previous payment is unresolved.

Package prices are per requested report. An Acceptance package can consume three browser jobs from the existing three-jobs-per-wallet daily allowance. Capacity is shared across packages; failed attempts can consume browser capacity. The service does not purchase more infrastructure when a limit is reached.

Live fixtures verified three pages and ten Acceptance requirements, and a ten-step staging submission on 11 October 2026. No payment was initiated by those fixture tests. Previous owner self-payments verified the shared x402 settlement and report delivery path; they are not independent customer sales.