Designed, not pretended

Granular website evidence should be cheaper than ignoring it.

The new beta sample covers one page once per day. A new paid cost structure will be published for API and MCP clients when production x402 settlement goes live. The normal website has no paid checkout path by design.

Current status: disabled. No WebsiteIQ endpoint currently requests or accepts payment, and the API will not return a decorative 402.

The client process, in five steps

These are the client-side steps that will apply after GET /api/x402/status reports enabled: true. Today, an agent may complete step one to estimate scope, then use the free single-page beta sample.

  1. Estimate the crawl scope. Send POST https://websiteiq.xyz/api/estimate with {"url":"https://example.com"}. Review estimatedPages, estimateComplete, and pricingStatus. No current price is returned.
  2. Check settlement readiness. Send GET https://websiteiq.xyz/api/x402/status. Continue only when the JSON response says enabled: true.
  3. Request the paid audit. Send the documented JSON body to the paid WebsiteIQ API or MCP resource. A request without payment will receive 402 Payment Required and a Base64-encoded PAYMENT-REQUIRED header containing the exact published requirements and price.
  4. Sign and retry. Confirm the USDC amount, Base network, destination, and resource in an x402 v2-compatible client; retry the identical request with its signed payload in PAYMENT-SIGNATURE.
  5. Keep the evidence. Read the audit response and PAYMENT-RESPONSE settlement header. Save the returned unlisted report URL; anyone with the complete token-bearing URL can view that retained report.

Why x402 fits this service

An agent may need a small evidence object before deciding whether a deeper task is worth doing. Account creation, subscription checkout, and API-key provisioning can cost more coordination than the audit itself. x402 uses HTTP 402 negotiation and wallet-signed payment so a compatible client can pay for one resource request.

That does not make every audit profitable or useful. The unit price must still cover facilitator cost, edge compute, abuse, storage, support, and failed requests. WebsiteIQ will publish a benchmark fixture before making a savings claim.

Planned contract

Item Planned behavior
Resource A paid API or MCP audit. Final inline and queued limits will be published with the production settlement contract.
Pricing status Not published. A new cost structure will be released only when the paid resource, facilitator, settlement verification, execution limits, and refund/accounting policy are production-ready.
Settlement USDC on Base through a production facilitator.
Discovery OpenAPI/API catalog plus the endpoint’s real 402 response; no invented /.well-known/x402 or OKF payment artifact.
Crawl boundary Payment never buys permission to ignore the target site’s robots.txt or access controls.

Beta boundary

The new free beta sample is one comprehensive page per connection per 24 hours and requires a valid requester email plus explicit audit-processing consent. The sitemap scope estimator is active. Pricing, payment collection, paid execution, and the queue required to divide large jobs across safe Worker invocations are not active.

Primary references