x402 List Submit a serviceSubmit

LedgerProof Settlement Army

offline

payment-ready 2026-09-07, probe currently failing

Pay-per-call evidence for autonomous agents, settled in USDC on Base via x402 · no account, no API key, no subscription.

Call it x402 v2

x402 v2

Base URL
https://ledgerproofhq.io
Payment
x402 v2, header channel
$ curl -i -X POST 'https://ledgerproofhq.io/api/lain/confidence'

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

Endpoints 1 paid route on ledgerproofhq.io

POST/api/lain/confidenceBase$0.05since 08-21

Prices as captured in the 402 response: $0.05.

Example 402 response

Endpoints and prices

Current paid endpoints; minimum quoted prices in USD where available; first capture dates in UTC
MethodPathDescriptionPriceNetworkAsset402 channelCaptured
POST/api/lain/confidenceNo description$0.05BaseUSDCheadersince 08-21

Payment evidence

402 payload captured at . Check evidence JSON · Measurement methodology.

1 payload captured by the monitor.

139 lines, scroll inside

{
  "error": "Payment required",
  "accepts": [
    {
      "asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
      "extra": {
        "name": "USD Coin",
        "version": "2"
      },
      "payTo": "0x519671b571aE670813B369642A31fE8765827328",
      "amount": "50000",
      "scheme": "exact",
      "network": "eip155:8453",
      "maxTimeoutSeconds": 120
    }
  ],
  "resource": {
    "url": "https://ledgerproofhq.io/api/lain/confidence",
    "mimeType": "application/json",
    "description": "LAIN confidence: independently verifiable evidence about a subject, settled per call in USDC on Base. Proof-gated: payment is captured only after the evidence is assembled and anchored."
  },
  "extensions": {
    "bazaar": {
      "info": {
        "input": {
          "body": {
            "subject": "Acme Corp",
            "settlement": "x402",
            "current_confidence": 0.5,
            "required_confidence": 0.99
          },
          "type": "http",
          "method": "POST",
          "bodyType": "json"
        },
        "output": {
          "type": "json",
          "example": {
            "gap": 0.49,
            "outcome": "resolved",
            "receipt": {
              "verify_url": "https://verify.ledgerproofhq.io/?seq=12345",
              "content_hash": "<sha256>"
            },
            "subject": "Acme Corp",
            "evidence": [
              {
                "source": "sanctions",
                "finding": "no match",
                "checked_at": "2026-08-21T00:00:00Z"
              }
            ]
          }
        }
      },
      "schema": {
        "type": "object",
        "$schema": "https://json-schema.org/draft/2020-12/schema",
        "required": [
          "input",
          "output"
        ],
        "properties": {
          "input": {
            "type": "object",
            "required": [
              "type",
              "method",
              "bodyType",
              "body"
            ],
            "properties": {
              "body": {
                "type": "object",
                "required": [
                  "subject"
                ],
                "properties": {
                  "subject": {
                    "type": "string",
                    "description": "entity, product or firm to gather evidence about"
                  },
                  "settlement": {
                    "enum": [
                      "x402"
                    ],
                    "type": "string"
                  },
                  "current_confidence": {
                    "type": "number",
                    "maximum": 1,
                    "minimum": 0
                  },
                  "required_confidence": {
                    "type": "number",
                    "maximum": 1,
                    "minimum": 0
                  }
                }
              },
              "type": {
                "const": "http"
              },
              "method": {
                "enum": [
                  "POST"
                ],
                "type": "string"
              },
              "bodyType": {
                "enum": [
                  "json"
                ]
              }
            },
            "additionalProperties": false
          },
          "output": {
            "type": "object",
            "required": [
              "type",
              "example"
            ],
            "properties": {
              "type": {
                "const": "json"
              },
              "example": {
                "type": "object"
              }
            },
            "additionalProperties": false
          }
        }
      }
    }
  },
  "x402Version": 2
}

Can I trust it score from our own monitoring

score from our own monitoring

54/100 Weak

#120 of 120 in Verification. Bands: strong 93+, solid 75+, mixed 55+, weak below 55.

Reliability
10.8% uptime 30d
Compliance
A 14/14 checks pass, stale (probe failing)
Price
$0.05 p80 in Verification
Risk
clean no risk flag
Traction
$0.00 30d 0 buyers
14/14 compliance checks
  • 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

402 terms unchanged since 2026-08-21. Last up 2026-09-07.

── Site signals

  • homepage reachable
  • openapi doc
  • pricing page
  • llms.txt
  • robots.txt
  • terms page
How the score works

What the score read on this service: status offline, 10.8% uptime 30d, 3158ms response p95, x402 compliance 14 of 14, $0.05 price against the category, on-chain traction measured. 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.

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.

It is a score inside Verification, 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 120 listings, this one among them: the same 120 the position above is counted against. When the two differ, the field is the wider one, 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.

Traction is a conservative undercount; first settlement seen 2026-08-19.

All measured facts

What it does

Pay-per-call evidence for autonomous agents, settled in USDC on Base via x402 · no account, no API key, no subscription. POST a subject with your current and required confidence, and the service assembles independently verifiable evidence and returns it with a free cryptographically anchored hash receipt carrying a verify_url anyone can check without trusting us. Settlement is proof-gated: payment is captured only after the deliverable passes a published acceptance rule that can genuinely fail, so a failed result is never charged for. Part of the LedgerProof Settlement Army, 21 proof-gated services in total.

LedgerProof Settlement Army is a listed x402 Verification API. Captured payment terms name Base. Monitoring and settlement figures below describe the observations available to this directory; an unpaid HTTP 402 check does not prove that a paid call will deliver.

Assessment computed at . Latest service check observed at . Service data JSON · Measurement methodology.

Page rendered at . This response time is separate from the observation and computation times attached to each measurement.

Latest endpoint observation: . Latest price capture: . Prices are recorded quotes, not a promise of availability. Token assets and payment terms are listed separately. Endpoint data JSON · Price history JSON · Measurement methodology.

Assessment computed at . Uptime uses the stated daily-rollup window; response times are in milliseconds, compliance is passed/evaluated checks, and traction is a measured settlement floor. The comparison score is out of 100 within this category. Assessment JSON · Measurement methodology.

Observed daily coverage: 2026-09-07 to 2026-10-06 UTC. Daily monitoring and settlement rollups do not expose their computation time; a bucket date is not an update timestamp. Latest settlement in the assessment: . Uptime and response JSON · Volume JSON · Buyers JSON · Measurement methodology.

Ranked from the measured category pool, refreshed at most once a minute. The comparison has no persisted computation timestamp; the assessment time above belongs to this service only. Ranking API documentation · Ranking methodology.

x402 List home · Services · Verification

uptime · latest daily rollup
-
uptime 7d
0%
uptime 30d
10.8%
uptime 90d
92.3%
response p95
3158ms
avg response
2107ms
total checks
307

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

price (min)
$0.05
category percentile (min)
p80 in Verification
endpoints / prices
1 / 1
model
flat
stability
100%

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
-
registrar
-
hosting
custom
domain created
---

Identity facts, not a risk score.

assessment volume 30d
$0.00
exact assessment volume 30d (USD)
0
assessment recorded at (UTC)
2026-10-06T01:13:01.346Z
buyers 30d
0
settlements 30d
0
measured since
2026-08-19 (start of our harvest window)
last settlement
2026-08-20
top buyer share
-
trend 7d vs 30d
-
networks
eip155:8453
volume all-time
$0.15
settlements all-time
3
median settlement 30d
-
max settlement 30d
-

Assessment volume uses the latest 30d assessment. Over time sums daily address snapshots, rounded to cents and refreshed separately. The two sources can differ in timing, precision and shared-address attribution. Amounts use cents for comparison; known sub-cent values keep up to 12 significant digits. The exact stored assessment value is shown above.

Conservative undercount: only USDC settlements via facilitators we measure are counted. A measured floor, not an estimate.

Top buyer share is part of the ranking score: a higher share lowers the traction part of the score, by up to half when one address holds all 30d volume.

member since
2026-08-21
Recent checks
Latest 18 unpaid HTTP checks, newest first; response times in milliseconds, observation times in UTC
Checked at (UTC)StatusHTTPResponseEndpoints
Offline502280ms0
Offline502171ms0
Offline502135ms0
Offline50293ms0
Offline502359ms0
Offline502249ms0
Offline502127ms0
Offline502233ms0
Offline502122ms0
Offline502184ms0
Offline502142ms0
Offline50295ms0
Offline502183ms0
Offline502366ms0
Offline502325ms0
Offline5021163ms0
Offline502713ms0
Offline502272ms0

Over time

On-chain volume daily snapshots, USD 30d: $0.00
volume no data in the payload
Distinct buyers per dayDistinct buyers per day
Uptime 29 of 29 completed days below 100%
uptime below 100%, to scale uptime 0%
Volume 30d
$0.00
Uptime
29 of 29 completed days below 100%
Daily on-chain settlement volume in US dollars, 2026-09-07 to 2026-10-06; 30 days have no data in the payload; distinct buyers per day
More charts
Response time daily average, ms min 2107ms, avg 2107ms, max 2107ms

09-07 to 10-06* UTC

Scores over time

x402 compliance low 14/14, high 14/14

09-07 to 10-06* UTC

Price percentile in Verification own low to high; exact values below

09-07 to 10-06* UTC

Site signals present (of 6) own low to high; exact values below

09-07 to 10-06* UTC

Scores: one day per column, 09-07 to 10-06*, on the columns of Response time. Uptime held below 100% on some days in this window, including any partial day. Daily readings remain in the Uptime strip and Values. The checklist grew from 11 to 14 checks on 2026-07-28, before this window. Pillar lines use their own low and high. Exact dated readings are available in each readout and in Values.

Each series spans only the dates it has data for. Every series is also served as JSON at /api/v1/services/ledgerproof-settlement-army/price, /scores, /volume and /buyers.

Values

* today so far, partial (UTC).

The uptime summary counts completed UTC days only. The strip, readouts and table retain today's partial reading.

Daily snapshot total, no volume data in the last 30d. The visible 30d total in Traction comes from the latest assessment. These sources can differ in their window, refresh time, cent rounding and shared-address attribution.

Daily address snapshots: 2026-09-07 to 2026-10-06 UTC; * today so far, partial (UTC). Daily snapshots store cents. A recorded $0.00 with settlements cannot distinguish exact zero from volume rounded away. Lost precision is unavailable here.

Settlement volume uses the stored USD valuation of tracked payments; it is distinct from token quantities. USD-pegged assets are valued at 1 USD per token in these rollups. The measured settlement floor does not cover all payments to this service.

Assessment history last recorded at . Each UTC day uses its last recorded run; missing readings stay unmeasured. Assessment history JSON · Measurement methodology.

Daily values, 2026-09-07 to 2026-10-06: address settlement volume in USD, distinct buyer and settlement counts, uptime percent, average response milliseconds, compliance passed/total, price percentile 0-100, site signals out of 6; UTC dates
DayVolumeBuyersSettlementsUptimeResponseCompliancePrice percentileSite signals
2026-09-07no datano datano data55.56%2106.67ms14/14p773/6
2026-09-08no datano datano data0%no data14/14p783/6
2026-09-09no datano datano data0%no data14/14p780/6
2026-09-10no datano datano data0%no data14/14p780/6
2026-09-11no datano datano data0%no data14/14p783/6
2026-09-12no datano datano data0%no data14/14p783/6
2026-09-13no datano datano data0%no data14/14p783/6
2026-09-14no datano datano data0%no data14/14p793/6
2026-09-15no datano datano data0%no data14/14p793/6
2026-09-16no datano datano data0%no data14/14p793/6
2026-09-17no datano datano data0%no data14/14p790/6
2026-09-18no datano datano data0%no data14/14p790/6
2026-09-19no datano datano data0%no data14/14p793/6
2026-09-20no datano datano data0%no data14/14p793/6
2026-09-21no datano datano data0%no data14/14p813/6
2026-09-22no datano datano data0%no data14/14p813/6
2026-09-23no datano datano data0%no data14/14p803/6
2026-09-24no datano datano data0%no data14/14p803/6
2026-09-25no datano datano data0%no data14/14p803/6
2026-09-26no datano datano data0%no data14/14p823/6
2026-09-27no datano datano data0%no data14/14p813/6
2026-09-28no datano datano data0%no data14/14p813/6
2026-09-29no datano datano data0%no data14/14p793/6
2026-09-30no datano datano data0%no data14/14p793/6
2026-10-01no datano datano data0%no data14/14p793/6
2026-10-02no datano datano data0%no data14/14p793/6
2026-10-03no datano datano data0%no data14/14p793/6
2026-10-04no datano datano data0%no data14/14p793/6
2026-10-05no datano datano data0%no data14/14p803/6
2026-10-06*no datano datano datano datano data14/14p803/6

Alternatives in Verification

scvd.store · evidence observatory for the x402 economy strong 94/100 100% up 30d $515.21 30d
Rubric Protocol · Post-Quantum AI Attestation solid 92/100 99.9% up 30d $35.52 30d
KushBitx AgentProof solid 89/100 100% up 30d $1.52 30d
PHION Agent Services solid 89/100 99.9% up 30d $1.50 30d
767-2676.com - POPCORN solid 89/100 100% up 30d $0.15 30d

5 of 119 other ranked services in Verification, ordered by the same measured score.

Own this service?

Keep this listing accurate. Ownership is proven with a domain check and every change is reviewed by hand.

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)
Embed a badge

HTML

<a href="https://x402-list.com/services/ledgerproof-settlement-army?utm_source=badge&utm_medium=referral&utm_campaign=embed">
  <img src="https://x402-list.com/badge/ledgerproof-settlement-army.svg" alt="LedgerProof Settlement Army listed on x402-list" height="28">
</a>

Markdown

[![LedgerProof Settlement Army on x402-list](https://x402-list.com/badge/ledgerproof-settlement-army.svg)](https://x402-list.com/services/ledgerproof-settlement-army?utm_source=badge&utm_medium=referral&utm_campaign=embed)

HTML, live uptime variant

<a href="https://x402-list.com/services/ledgerproof-settlement-army?utm_source=badge&utm_medium=referral&utm_campaign=embed">
  <img src="https://x402-list.com/badge/ledgerproof-settlement-army.svg?data=uptime" alt="LedgerProof Settlement Army uptime on x402-list" height="28">
</a>
Delisting

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