debtpulse.theaslangroupllc.com/api/debt/rights
1.Catalog declaration
| Resource URL | https://debtpulse.theaslangroupllc.com/api/debt/rights |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0x50ab2018c06c6e4eaa9ba52057eb55ed284912fc |
| Declared price (base units) | 50000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-10-18 13:04 UTC |
| Catalog-reported calls / payers (30d) | 6 / 2 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-18 13:40 UTC | GET | pass | 402 | 1913 ms | — |
| 2026-10-17 04:40 UTC | GET | pass | 402 | 150 ms | — |
| 2026-09-17 16:19 UTC | GET | pass | 402 | 184 ms | — |
| 2026-09-15 11:24 UTC | GET | pass | 402 | 226 ms | — |
| 2026-09-11 11:24 UTC | GET | pass | 402 | 83 ms | — |
| 2026-09-07 11:24 UTC | GET | pass | 402 | 120 ms | — |
| 2026-09-02 11:25 UTC | GET | pass | 402 | 67 ms | — |
| 2026-08-21 10:55 UTC | GET | fail | 402 | 57 ms | price_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change). |
3.L1 — real purchases
1 of 1 paid attempts settled on-chain, and 0 of those also returned a 2xx response (delivered). Each settled row carries its on-chain transaction hash, and that transaction is the evidence. On this page a receipt means the seller's own settlement receipt (PAYMENT-RESPONSE); a settled row can have none (see “tx from our index”). A settled row reads as nonce-bound when the on-chain re-read also matched the one-time signature nonce we generated for that purchase, and amount + payee when it matched amount, payee, asset and chain with no nonce on record — the binding shipped on 2026-09-04, so earlier rows carry the weaker evidence and keep their label rather than being demoted (methodology). settled is the transfer we confirmed on-chain; delivered is the response arriving. A settled row whose paid request answered 5xx counts as settled and not as delivered — definitions.
A row marked tx from our index came back with no settlement receipt from the seller. Our own index of on-chain settlements found the transfer afterwards — our payer, this endpoint's payee, the exact amount, inside the time window — and the row goes through the same on-chain re-read as any other before it reads settled. The seller did not name that transaction; we did (methodology).
Terms in this table
settled (nonce-bound)- vet402 confirmed the USDC transfer on-chain, and the on-chain re-read also matched the one-time nonce vet402 signed for that purchase.
L2 not_checked- not checked: the paid request did not answer 200, so there was no response to check against the listing's output schema.
Whose side- the same words as the seller page: seller's side only after failures on two different days (UTC), marked “under re-check”; vet402's side; or not sorted (the rules).
| Attempted at | Result | HTTP | On-chain tx | Latency |
|---|---|---|---|---|
| 10-16 17:012026-10-16 17:01 UTC | settled (nonce-bound)tx from our index | — | 0x5f28a361…3219 | 20176 ms |
| 50000 units (≈ $0.05 USDC) · L2 not_checkedWhose side: not sorted: vet402 stopped waiting | ||||
Embed this record
Run this endpoint? Show the settle-through record vet402 measured — the badge reads 1/1 settled · 0 delivered and updates as the record grows. It carries the host it is about and the date it was last measured, so a saved copy cannot pass itself off as current. It states a measurement, not a rating.
[](https://vet402.com/observatory/e/2591b02e-f7cd-4bcc-9e33-e89ec615722c)4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-10-16 | relisted | {"status":"delisted"} | {"status":"active"} |
| 2026-09-20 | delisted | {"status":"active"} | {"status":"delisted"} |
unverified is not a failure; a fail is published only after two consecutive failing probes. Definitions: methodology.
5.Dispute this record
Think a measurement above is wrong? Say which probe or purchase and what you observed instead. One person reads it and replies. The record is never deleted on dispute: if it was wrong, the correction is published with the same weight; if it was right, it stands. Operators who control the receiving address can also sign a dispute via POST /api/v1/observatory/disputes (API reference), which re-measures through the normal publication gate.