x402 List

x402 Protocol Service Directory

difftool

Data PAYMENT-READY

payment-ready until 2026-09-15

Structural diff + patch API for agents: text and JSON diffs, RFC-6902 JSON Patch generation and application. Deterministic output suitable for automated pipelines. 0.03 USDC per call via x402 on Base.

Part of the Leeworks operator hub

Pay from $0.03 per request in USDC on Base, settled onchain via the x402 protocol, no signup, no API key needed.

BASE URL https://difftool.leeworks.dev WEBSITE https://difftool.leeworks.dev ENDPOINTS 1 NETWORK Base ASSET USDC MEMBER SINCE 2026-07-25 MONITORED SINCE 2026-07-25

VERDICT

ranking generation 3

solid 86/100 #115 of 284 in Data by measured score

What the score read on this service: status online, 100% uptime 30d, 2218ms response p95, x402 compliance 13 of 14, $0.03 price against the category. Each of those is measured, and each is published in full below.

The score comes from our own monitoring, never from reviews, operator claims, or a language model: reliability, x402 compliance, price against the category, a deterministic risk flag, and a small on-chain traction term, weighted by ranking generation 3. It is not placement anyone can buy: the paid verify tier is reported beside it and is not one of its inputs. Every component below stays published and read-only.

It is a score inside Data, and only there: price and speed are scored against the whole category field, every listing in it that carries no danger flag, the scored service included, which here means 284 listings, this one among them. That set is wider than the 284 the position above is counted against, because a listing we have measured too little of to rank still sits in the field the price and the speed are normalized over. The same service in a different field would read differently. The same engine answers GET /api/v1/best, and asked for a different pool (the whole directory, or another filter) it returns a different number for this service under this same ranking generation. Neither is more correct: they answer different questions, and the methodology states which is which.

Bands on the 0 to 100 measured score: strong at 93 and above, solid from 75, mixed from 55, weak below 55. Price and speed are scored against the whole category field, every listing in it that carries no danger flag, the scored service included, so the score places a service in its own field.

ALTERNATIVES IN DATA

Other Data services in this directory, ordered by the same measured score. The figures are ours: 30-day uptime from our own probes, 30-day settlement volume read on-chain (a conservative undercount, and null where we cannot measure it, never a zero).

Ranked alternative x402 services in the same category, with band, measured score, 30-day uptime and 30-day on-chain settlement volume
SERVICE BAND SCORE UPTIME 30D VOL 30D
agentstools strong 99 100% ---
AgentBIT strong 99 100% ---
WhaleTape strong 99 97.8% ---
ThirdMade Shelf strong 98 100% ---
AgentToll strong 98 100% ---
5 of 283 other ranked services in Data · see the whole category

ASSESSMENT

updated 1h ago

The parts the verdict above is computed from, each with its proof. Click any chip. Measured values stay read-only; unknown is honest, and an unknown is never counted as a zero.

reliability 100%
uptime 24h
100%
uptime 7d
99.8%
uptime 30d
100%
uptime 90d
99.8%
response p95
2218ms
avg response
1212ms
total checks
2,759

Measured on the unpaid 402 handshake, not the paid call. A service can 402 correctly and still fail after payment.

compliance A (13/14): declares the current x402 version (2)

13 of 14 x402 conformance checks pass; failing: declares the current x402 version (2). Full checklist below.

jump to compliance checklist

price $0.03 (p81 in Data)
price (min)
$0.03
category percentile (min)
p81 in Data
endpoints / prices
1 / 1
model
flat
stability
100%
risk clean

No deterministic risk flag. Risk fires only on an exact blocklist match, or a reserved-brand name with a mismatched verified payTo. Never from low uptime, a high price, or a model guess.

domain age
768d
registrar
CloudFlare, Inc.
hosting
custom
domain created
2024-07-30

Identity facts, not a risk score.

traction ---

This service settles on a network x402-list does not measure yet, so on-chain volume is not counted here. Shown as unmeasured, not zero.

WHAT IT DOES

ai-derived

The service generates and applies structured diffs using RFC-6902 JSON Patch format.

category
diff-tool
in
body
diff-patchdata-comparison

AI-generated summary. The measured data is never altered by it.

ENDPOINTS

Service endpoints with HTTP method, path, description, pricing, and network
METHOD PATH DESCRIPTION PRICE NETWORK ASSET 402 CHANNEL
POST /v1/diff Structured diffs + RFC-6902 JSON Patch generate/apply $0.03 Base USDC body (v1 style)
1 endpoints

REQUEST / RESPONSE EXAMPLE

An unpaid request to POST /v1/diff returns HTTP 402 with the payment terms. Settle onchain via your facilitator, then retry with the X-Payment header.

// request
curl -i -X POST 'https://difftool.leeworks.dev/v1/diff'
// 402 response (captured by monitor) · 1 payload · click to expand
[
  {
    "error": "payment required",
    "accepts": [
      {
        "asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
        "extra": {
          "name": "USD Coin",
          "input": {
            "method": "POST",
            "schema": {
              "type": "object",
              "required": [
                "op"
              ],
              "properties": {
                "a": {
                  "description": "text_diff: string A. json_patch/json_diff: doc A"
                },
                "b": {
                  "description": "text_diff: string B. json_patch/json_diff: doc B"
                },
                "op": {
                  "enum": [
                    "text_diff",
                    "json_patch",
                    "apply_patch",
                    "json_diff"
                  ],
                  "type": "string",
                  "description": "Operation; remaining fields depend on op"
                },
                "doc": {
                  "description": "apply_patch: base document"
                },
                "aName": {
                  "type": "string",
                  "description": "text_diff: label for A (default 'a')"
                },
                "bName": {
                  "type": "string",
                  "description": "text_diff: label for B (default 'b')"
                },
                "patch": {
                  "type": "array",
                  "description": "apply_patch: RFC-6902 patch to apply"
                }
              }
            },
            "example": {
              "a": {
                "n": 1,
                "name": "ada"
              },
              "b": {
                "n": 2,
                "name": "ada"
              },
              "op": "json_patch"
            },
            "contentType": "application/json"
          },
          "output": {
            "example": {
              "ok": true,
              "op": "json_patch",
              "patch": [
                {
                  "op": "replace",
                  "path": "/n",
                  "value": 2
                }
              ]
            },
            "contentType": "application/json",
            "description": "Always includes {ok, op}; other fields depend on op (patch | result | ops/summary | changedHunks)"
          },
          "version": "2"
        },
        "payTo": "0xa8B061d96F69426f11bcC807BfA00f0AF79541a7",
        "scheme": "exact",
        "network": "base",
        "mimeType": "application/json",
        "resource": "https://difftool.leeworks.dev/v1/diff",
        "description": "Structured diffs + RFC-6902 JSON Patch generate/apply",
        "maxAmountRequired": "30000",
        "maxTimeoutSeconds": 120
      }
    ],
    "x402Version": 1
  }
]

OVER TIME

All charts use the 90d selector; each series spans only the dates it has data for. Every series is also served as JSON at /api/v1/services/difftool/price, /scores, /volume and /buyers. On-chain volume and distinct buyers are measured over the service's settlement address and are a conservative undercount (only settlements that reach a measured facilitator are counted). The on-chain series roll up hourly, so the latest day can be up to about an hour behind; distinct buyers are counted per payout address, so a service that settles to more than one address is an upper bound.

UPTIME
07-25 · uptime 100.0% · 1148ms avg07-26 · uptime 100.0% · 910ms avg07-27 · uptime 100.0% · 883ms avg07-28 · uptime 96.7% · 894ms avg07-29 · uptime 100.0% · 813ms avg07-30 · uptime 100.0% · 878ms avg07-31 · uptime 100.0% · 896ms avg08-01 · uptime 100.0% · 1016ms avg08-02 · uptime 100.0% · 1075ms avg08-03 · uptime 100.0% · 1100ms avg08-04 · uptime 100.0% · 1151ms avg08-05 · uptime 100.0% · 1548ms avg08-06 · uptime 95.6% · 982ms avg08-07 · uptime 100.0% · 1025ms avg08-08 · uptime 100.0% · 1159ms avg08-09 · uptime 100.0% · 876ms avg08-10 · uptime 100.0% · 1166ms avg08-11 · uptime 100.0% · 891ms avg08-12 · uptime 100.0% · 955ms avg08-13 · uptime 100.0% · 1290ms avg08-14 · uptime 100.0% · 1257ms avg08-15 · uptime 100.0% · 1061ms avg08-16 · uptime 100.0% · 1074ms avg08-17 · uptime 100.0% · 1357ms avg08-18 · uptime 100.0% · 1220ms avg08-19 · uptime 100.0% · 1366ms avg08-20 · uptime 100.0% · 990ms avg08-21 · uptime 100.0% · 721ms avg08-22 · uptime 100.0% · 803ms avg08-23 · uptime 100.0% · 882ms avg08-24 · uptime 100.0% · 1050ms avg08-25 · uptime 100.0% · 1249ms avg08-26 · uptime 100.0% · 1103ms avg08-27 · uptime 100.0% · 1305ms avg08-28 · uptime 100.0% · 1349ms avg08-29 · uptime 100.0% · 1582ms avg08-30 · uptime 100.0% · 1426ms avg08-31 · uptime 100.0% · 1492ms avg09-01 · uptime 100.0% · 1839ms avg09-02 · uptime 100.0% · 1259ms avg09-03 · uptime 100.0% · 1463ms avg09-04 · uptime 98.9% · 1574ms avg09-05 · uptime 100.0% · 980ms avg09-06 · uptime 100.0% · 1442ms avg09-07 · uptime 100.0% · 1301ms avg09-08 · uptime 100.0% · 1209ms avg07-2509-08
90d UPTIME 99.8%
RESPONSE TIME
07-25 · 1148ms avg07-25 · 1148ms avg07-26 · 910ms avg07-26 · 910ms avg07-27 · 883ms avg07-27 · 883ms avg07-28 · 894ms avg07-28 · 894ms avg07-29 · 813ms avg07-29 · 813ms avg07-30 · 878ms avg07-30 · 878ms avg07-31 · 896ms avg07-31 · 896ms avg08-01 · 1016ms avg08-01 · 1016ms avg08-02 · 1075ms avg08-02 · 1075ms avg08-03 · 1100ms avg08-03 · 1100ms avg08-04 · 1151ms avg08-04 · 1151ms avg08-05 · 1548ms avg08-05 · 1548ms avg08-06 · 982ms avg08-06 · 982ms avg08-07 · 1025ms avg08-07 · 1025ms avg08-08 · 1159ms avg08-08 · 1159ms avg08-09 · 876ms avg08-09 · 876ms avg08-10 · 1166ms avg08-10 · 1166ms avg08-11 · 891ms avg08-11 · 891ms avg08-12 · 955ms avg08-12 · 955ms avg08-13 · 1290ms avg08-13 · 1290ms avg08-14 · 1257ms avg08-14 · 1257ms avg08-15 · 1061ms avg08-15 · 1061ms avg08-16 · 1074ms avg08-16 · 1074ms avg08-17 · 1357ms avg08-17 · 1357ms avg08-18 · 1220ms avg08-18 · 1220ms avg08-19 · 1366ms avg08-19 · 1366ms avg08-20 · 990ms avg08-20 · 990ms avg08-21 · 721ms avg08-21 · 721ms avg08-22 · 803ms avg08-22 · 803ms avg08-23 · 882ms avg08-23 · 882ms avg08-24 · 1050ms avg08-24 · 1050ms avg08-25 · 1249ms avg08-25 · 1249ms avg08-26 · 1103ms avg08-26 · 1103ms avg08-27 · 1305ms avg08-27 · 1305ms avg08-28 · 1349ms avg08-28 · 1349ms avg08-29 · 1582ms avg08-29 · 1582ms avg08-30 · 1426ms avg08-30 · 1426ms avg08-31 · 1492ms avg08-31 · 1492ms avg09-01 · 1839ms avg09-01 · 1839ms avg09-02 · 1259ms avg09-02 · 1259ms avg09-03 · 1463ms avg09-03 · 1463ms avg09-04 · 1574ms avg09-04 · 1574ms avg09-05 · 980ms avg09-05 · 980ms avg09-06 · 1442ms avg09-06 · 1442ms avg09-07 · 1301ms avg09-07 · 1301ms avg09-08 · 1209ms avg09-08 · 1209ms avg07-2509-08
AVG RESP 1212ms
PRICE (captured 402, USD)
07-25 · $0.0309-08 · $0.03$0.0307-2509-08
SUB-SCORES (uptime + x402 compliance)
07-25 uptime: 100.0% compliance: 100% checks07-26 uptime: 100.0% compliance: 100% checks07-27 uptime: 100.0% compliance: 100% checks07-28 uptime: 99.0% compliance: 93% checks07-29 uptime: 99.2% compliance: 93% checks07-30 uptime: 99.4% compliance: 93% checks07-31 uptime: 99.5% compliance: 93% checks08-01 uptime: 99.5% compliance: 93% checks08-02 uptime: 99.6% compliance: 93% checks08-03 uptime: 99.6% compliance: 93% checks08-04 uptime: 99.7% compliance: 93% checks08-05 uptime: 99.7% compliance: 93% checks08-06 uptime: 99.4% compliance: 93% checks08-07 uptime: 99.4% compliance: 93% checks08-08 uptime: 99.4% compliance: 93% checks08-09 uptime: 99.5% compliance: 93% checks08-10 uptime: 99.5% compliance: 93% checks08-11 uptime: 99.5% compliance: 93% checks08-12 uptime: 99.6% compliance: 93% checks08-13 uptime: 99.6% compliance: 93% checks08-14 uptime: 99.6% compliance: 93% checks08-15 uptime: 99.6% compliance: 93% checks08-16 uptime: 99.7% compliance: 93% checks08-17 uptime: 99.7% compliance: 93% checks08-18 uptime: 99.7% compliance: 93% checks08-19 uptime: 99.7% compliance: 93% checks08-20 uptime: 99.7% compliance: 93% checks08-21 uptime: 99.7% compliance: 93% checks08-22 uptime: 99.7% compliance: 93% checks08-23 uptime: 99.7% compliance: 93% checks08-24 uptime: 99.7% compliance: 93% checks08-25 uptime: 99.7% compliance: 93% checks08-26 uptime: 99.7% compliance: 93% checks08-27 uptime: 99.9% compliance: 93% checks08-28 uptime: 99.9% compliance: 93% checks08-29 uptime: 99.9% compliance: 93% checks08-30 uptime: 99.9% compliance: 93% checks08-31 uptime: 99.9% compliance: 93% checks09-01 uptime: 99.9% compliance: 93% checks09-02 uptime: 99.9% compliance: 93% checks09-03 uptime: 99.9% compliance: 93% checks09-04 uptime: 99.8% compliance: 93% checks09-05 uptime: 100.0% compliance: 93% checks09-06 uptime: 100.0% compliance: 93% checks09-07 uptime: 100.0% compliance: 93% checks09-08 uptime: 100.0% compliance: 93% checksuptimecompliance07-2509-08

checklist grew 11->14 on 2026-07-28; a step here is a metric change, not a regression

PILLARS OVER TIME (measured)

Measured site and economics pillars from the assessment history, so the latest value shown elsewhere on this page reads as a point on a trend rather than a permanent state.

VOLUME (on-chain settlement, USD)
This service settles on a network x402-list does not measure yet, so on-chain volume is not counted here. Shown as unmeasured, not zero.
DISTINCT BUYERS
This service settles on a network x402-list does not measure yet, so distinct on-chain buyers are not counted here. Shown as unmeasured, not zero.

COMPLIANCE

13/14 checks pass · grade A · failing: declares the current x402 version (2)

last 402 captured 2026-07-25 · last up 2026-09-08

  • 402 payload captured
  • accepts[] array present
  • payTo address recoverable
  • payTo at accepts[0].payTo (conformant shape)
  • payTo is a valid on-chain address
  • atomic price declared
  • atomic price in a sane range
  • asset (token) address declared
  • network resolves to CAIP-2
  • payment scheme declared
  • served over HTTPS
  • declares the current x402 version (2)
  • EIP-712 domain parameters present on every EVM entry
  • x402 v2 envelope delivered in the payment-required header

SITE PILLARS

  • homepage reachable
  • openapi doc
  • pricing page
  • llms.txt
  • robots.txt
  • terms page
recent checks (18) live · click to expand
TIME STATUS RESP CAUSE
● OK 1065ms
● OK 1686ms
● OK 1305ms
● OK 1205ms
● OK 1467ms
● OK 786ms
● SLOW 1854ms
● OK 807ms
● OK 906ms
● OK 1484ms
● SLOW 1982ms
● OK 998ms
● OK 1065ms
● OK 955ms
● OK 1591ms
● OK 658ms
● OK 642ms
● OK 408ms

EMBED THIS BADGE

Show that difftool is monitored on x402-list. Paste this on your site or README, it links back to this live listing.

difftool listed on x402-list
status
difftool uptime on x402-list
live uptime
// HTML
<a href="https://x402-list.com/services/difftool?utm_source=badge&utm_medium=referral&utm_campaign=embed">
  <img src="https://x402-list.com/badge/difftool.svg" alt="difftool listed on x402-list" height="28">
</a>
// Markdown
[![difftool on x402-list](https://x402-list.com/badge/difftool.svg)](https://x402-list.com/services/difftool?utm_source=badge&utm_medium=referral&utm_campaign=embed)
// HTML · live uptime variant
<a href="https://x402-list.com/services/difftool?utm_source=badge&utm_medium=referral&utm_campaign=embed">
  <img src="https://x402-list.com/badge/difftool.svg?data=uptime" alt="difftool uptime on x402-list" height="28">
</a>

RUN THIS SERVICE?

Keep this listing accurate: propose changes to the name, description, website, category or add new endpoints to monitor. Ownership is verified with a domain proof and every change is reviewed manually; measured data stays read-only.

[ update this listing ]

Earn the verified tier: x402list pays a real call to this endpoint and, if it delivers, the service is delivery-verified. The fee covers the cost of the probe, not the badge; there is no refund if the call does not deliver. Agent and API only, no in-browser signing. See /api.

[ verify this service ($0.25) ]

To request delisting, email info@x402-list.com or update your listing at /services/difftool/update.