Independent MeasurementEndpoint record (L0 · L1)Published state: unverifiedLast probed: 2026-09-16 · 18 days ago

finance.payapi.market/interest-rates

1.Catalog declaration

Catalog declaration for this endpoint
Resource URL	https://finance.payapi.market/interest-rates
Source	cdp_bazaar
Declared method	POST
Network	eip155:8453
Receiving address	0xffc458db291b4abce020fe3de4f91f2770e537b1
Declared price (base units)	1000
Catalog status	delisted (since 2026-09-17 01:03 UTC)
First seen / last seen	2026-08-14 08:39 UTC / 2026-09-16 01:03 UTC
Catalog-reported calls / payers (30d)	9 / 5

2.Probe history

2026-08-142026-09-16

Figure 1. Probe timeline, last 15 probes for this endpoint (UTC). Filled = pass, crossed = fail, dashed = unverified. Same-day probes overlap. Marks closer than one mark width are stepped down one lane.

L0 probe history, newest first
Probed at	Method	Verdict	HTTP	Latency	Reason
2026-09-16 22:40 UTC	POST	unverified	—	54 ms	tlsThe TLS handshake failed; vet402 cannot tell its own side from the seller's, so nothing is published against the seller.
2026-09-16 13:40 UTC	POST	unverified	—	322 ms	tlsThe TLS handshake failed; vet402 cannot tell its own side from the seller's, so nothing is published against the seller.
2026-09-15 13:40 UTC	POST	pass	402	127 ms	—
2026-09-14 22:40 UTC	POST	pass	402	1984 ms	—
2026-09-14 04:40 UTC	POST	pass	402	173 ms	—
2026-09-13 16:40 UTC	POST	pass	402	278 ms	—
2026-09-12 22:40 UTC	POST	pass	402	155 ms	—
2026-09-12 13:40 UTC	POST	pass	402	172 ms	—
2026-09-11 16:40 UTC	POST	pass	402	159 ms	—
2026-09-11 04:40 UTC	POST	pass	402	258 ms	—
2026-09-10 17:40 UTC	POST	pass	402	380 ms	—
2026-09-10 05:40 UTC	POST	pass	402	705 ms	—
2026-09-09 11:24 UTC	POST	pass	402	150 ms	—
2026-09-05 11:24 UTC	POST	pass	402	149 ms	—
2026-08-14 08:53 UTC	POST	pass	402	103 ms	—

3.L1 — real purchases

1 of 3 paid attempts settled on-chain, and 1 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 (amount + payee): vet402 confirmed the USDC transfer on-chain; the on-chain re-read matched amount, payee, asset and chain; no nonce was on record (rows before 2026-09-04).
delivered_no_receipt: the paid request answered 2xx without a settlement receipt.
L2 match: the response had the fields the listing's output schema declares.
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).

1/3

Figure 2. Settle-through: one cell per paid attempt. Filled = settled on-chain, crossed = signed, and not settled on-chain.

L1 purchase history, newest first
Attempted at	Result	HTTP	On-chain tx	Latency
08-28 12:202026-08-28 12:20 UTC	settled (amount + payee)tx from our index	200	0x793e746e…61ac	1522 ms
1000 units (≈ $0.001 USDC) · L2 matchWhose side: no failure (delivered)
08-21 08:322026-08-21 08:32 UTC	delivered_no_receipt	200	—	2164 ms
1000 units (≈ $0.001 USDC) · L2 matchWhose side: not sorted: no charge
08-14 09:562026-08-14 09:56 UTC	delivered_no_receipt	200	—	1551 ms
1000 units (≈ $0.001 USDC) · L2 matchWhose side: not sorted: no charge

Embed this record

Run this endpoint? Show the settle-through record vet402 measured — the badge reads 1/3 settled · 1 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.

[![vet402 receipt](https://vet402.com/api/badge/endpoint/177a56ed-1a2d-492b-b608-d39f8d4299be.svg)](https://vet402.com/observatory/e/177a56ed-1a2d-492b-b608-d39f8d4299be)

4.Catalog listing events

Catalog listing events, newest first
Detected on	Event	Before	After
2026-09-17	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.