Independent MeasurementEndpoint record (L0 · L1)Published state: unverifiedLast probed: 2026-10-05 · 41 days ago

grov.fun/api/solana/instasaves

1.Catalog declaration

Catalog declaration for this endpoint
Resource URL	https://grov.fun/api/solana/instasaves
Source	cdp_bazaar
Declared method	POST
Catalog network	solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp
Receiving address	DxnVaGNqTm1yX4Bm5YqtRzfUytF5ZiZ7N2eVXZpVPPP3
Declared price (base units)	50000
Catalog status	delisted (since 2026-10-06 01:01 UTC)
First seen / last seen	2026-09-04 01:03 UTC / 2026-10-03 01:04 UTC
Catalog-reported calls / payers (30d)	38 / 1

2.Probe history

2026-09-052026-10-05

Figure 1. Probe timeline, last 10 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-10-05 10:30 UTC	POST	unverified	400	656 ms	request_shapeUnpaid POST with an empty JSON body answered 400 before any payment challenge; not measured (vet402 does not guess the input).
2026-09-29 07:38 UTC	POST	unverified	400	433 ms	request_shapeUnpaid POST with an empty JSON body answered 400 before any payment challenge; not measured (vet402 does not guess the input).
2026-09-28 10:30 UTC	POST	fail	400	284 ms	no_402HTTP 400 instead of 402 to an unpaid POST. Recorded before the 2026-09-29 change; the POST carried an empty JSON body, and since that change this answer is recorded as request_shape (unverified), not as a fail.
2026-09-23 10:31 UTC	POST	fail	400	476 ms	no_402HTTP 400 instead of 402 to an unpaid POST. Recorded before the 2026-09-29 change; the POST carried an empty JSON body, and since that change this answer is recorded as request_shape (unverified), not as a fail.
2026-09-19 11:24 UTC	POST	fail	400	436 ms	no_402HTTP 400 instead of 402 to an unpaid POST. Recorded before the 2026-09-29 change; the POST carried an empty JSON body, and since that change this answer is recorded as request_shape (unverified), not as a fail.
2026-09-17 11:24 UTC	POST	fail	400	504 ms	no_402HTTP 400 instead of 402 to an unpaid POST. Recorded before the 2026-09-29 change; the POST carried an empty JSON body, and since that change this answer is recorded as request_shape (unverified), not as a fail.
2026-09-13 11:24 UTC	POST	fail	400	456 ms	no_402HTTP 400 instead of 402 to an unpaid POST. Recorded before the 2026-09-29 change; the POST carried an empty JSON body, and since that change this answer is recorded as request_shape (unverified), not as a fail.
2026-09-09 11:24 UTC	POST	fail	400	513 ms	no_402HTTP 400 instead of 402 to an unpaid POST. Recorded before the 2026-09-29 change; the POST carried an empty JSON body, and since that change this answer is recorded as request_shape (unverified), not as a fail.
2026-09-06 11:24 UTC	POST	fail	400	243 ms	no_402HTTP 400 instead of 402 to an unpaid POST. Recorded before the 2026-09-29 change; the POST carried an empty JSON body, and since that change this answer is recorded as request_shape (unverified), not as a fail.
2026-09-05 11:24 UTC	POST	fail	400	502 ms	no_402HTTP 400 instead of 402 to an unpaid POST. Recorded before the 2026-09-29 change; the POST carried an empty JSON body, and since that change this answer is recorded as request_shape (unverified), not as a fail.

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-06	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

A dispute does not start a purchase. The signed dispute route runs one fresh L0 check, an unpaid request.

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. This listing is not active in the catalog, so a dispute filed on the record form does not put it on the re-probe list. The record stays on this page. The scheduled L0 run is at 10:30 UTC. This listing is not on that run. Send the dispute to support@vet402.com. Published corrections are listed at /corrections. Operators who control the receiving address can also sign a dispute via POST /api/v1/observatory/disputes (API reference). That route runs one fresh L0 check under the normal publication gate. A later purchase comes from the regular schedule.