GeneralLive

Dom Change Diff

DOM diff for two HTML snapshots of the same page or component, built for browser-automation scripts whose CSS selectors quietly break after a site redesign.

$0.0115USDC per call · settled on Base · no subscription, no API key

Overview

DOM diff for two HTML snapshots of the same page or component, built for browser-automation scripts whose CSS selectors quietly break after a site redesign. Send before_html and after_html plus the selectors your workflow watches, and get back per-selector added/removed/moved/attribute-changed status, stale DOM detection for targets that vanished, and selector stability hints: replacement selectors built from an element's id, data-testid, or aria-label so a broken automation step can self-repair. Use it as a browser workflow repair tool, a selector-stability checker, or a pre-flight check before re-running a scraping or RPA script against a site that may have changed.

Endpoint

MethodEndpointPriceDescription
POST/v1/marketplace/api/dom-change-diff$0.0115Invoke Dom Change Diff (General) and return the upstream response.

How to call it

Requests are paid per call over the x402 protocol. Call the endpoint, receive a 402 Payment Required quote, then repeat the request with the signed payment header. The SDKs do both steps for you.

# 1. Ask for a quote
curl -i -X POST https://api.jarvisclaw.ai/v1/marketplace/api/dom-change-diff \
  -H 'Content-Type: application/json' \
  -d '{}'

# 2. Pay it (the SDK signs and retries for you)
curl -X POST https://api.jarvisclaw.ai/v1/marketplace/api/dom-change-diff \
  -H 'Content-Type: application/json' \
  -H 'X-PAYMENT: <signed-payload>' \
  -d '{}'
Open in the marketplace

Docs: Getting started · x402 payments · x402 discovery · All APIs