Independent MeasurementEndpoint record (L0 · L1)Published state: passLast probed: 2026-10-20 · today

tienda.textokit.store/api/dolar-ar

1.Catalog declaration

Catalog declaration for this endpoint
Resource URL	https://tienda.textokit.store/api/dolar-ar
Source	cdp_bazaar
Declared method	POST
Network	eip155:8453
Receiving address	0x6b5af9924f4cd35643c11a9fd1c983f77261a6e1
Declared price (base units)	2000
Catalog status	active
First seen / last seen	2026-10-13 13:03 UTC / 2026-10-20 13:01 UTC
Catalog-reported calls / payers (30d)	— / —

2.Probe history

2026-10-142026-10-20

Figure 1. Probe timeline, last 6 probes for this endpoint (UTC). Filled = pass, crossed = fail, dashed = unverified. Same-day probes overlap.

L0 probe history, newest first
Probed at	Method	Verdict	HTTP	Latency	Reason
2026-10-20 13:40 UTC	POST	pass	402	633 ms	—
2026-10-18 22:40 UTC	POST	fail	530	147 ms	no_402HTTP 530 instead of 402 to an unpaid POST.
2026-10-17 16:40 UTC	POST	fail	530	199 ms	no_402HTTP 530 instead of 402 to an unpaid POST.
2026-10-16 10:30 UTC	POST	fail	530	60 ms	no_402HTTP 530 instead of 402 to an unpaid POST.
2026-10-14 10:30 UTC	POST	fail	530	123 ms	no_402HTTP 530 instead of 402 to an unpaid POST.
2026-10-14 03:40 UTC	POST	fail	530	301 ms	no_402HTTP 530 instead of 402 to an unpaid POST.

3.L1 — real purchases

No paid purchases recorded for this endpoint yet.

4.Catalog listing events

Catalog listing events, newest first
Detected on	Event	Before	After
2026-10-16	relisted	`{"status":"delisted"}`	`{"status":"active"}`
2026-10-15	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.