www.bitcoind.app/api/v1/methods
1.Catalog declaration
| Resource URL | https://www.bitcoind.app/api/v1/methods |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0x3130cd1cab59a15dc75931ecb006b6f8c0b4a3fa |
| Declared price (base units) | 1000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-10-01 01:03 UTC |
| Catalog-reported calls / payers (30d) | 4 / 4 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-01 04:40 UTC | GET | pass | 402 | 301 ms | — |
| 2026-09-30 13:40 UTC | GET | pass | 402 | 459 ms | — |
| 2026-09-29 16:40 UTC | GET | pass | 402 | 236 ms | — |
| 2026-09-28 22:40 UTC | GET | pass | 402 | 153 ms | — |
| 2026-09-28 04:40 UTC | GET | pass | 402 | 173 ms | — |
| 2026-09-27 13:40 UTC | GET | pass | 402 | 315 ms | — |
| 2026-09-26 16:40 UTC | GET | pass | 402 | 229 ms | — |
| 2026-09-25 22:40 UTC | GET | pass | 402 | 425 ms | — |
| 2026-09-25 04:40 UTC | GET | pass | 402 | 116 ms | — |
| 2026-09-24 13:40 UTC | GET | pass | 402 | 2314 ms | — |
| 2026-09-23 16:40 UTC | GET | pass | 402 | 218 ms | — |
| 2026-09-23 04:40 UTC | GET | pass | 402 | 378 ms | — |
| 2026-09-22 13:40 UTC | GET | pass | 402 | 247 ms | — |
| 2026-09-21 16:40 UTC | GET | pass | 402 | 225 ms | — |
| 2026-09-20 22:40 UTC | GET | pass | 402 | 184 ms | — |
| 2026-09-20 04:40 UTC | GET | pass | 402 | 2143 ms | — |
| 2026-09-19 13:40 UTC | GET | pass | 402 | 189 ms | — |
| 2026-09-18 16:40 UTC | GET | pass | 402 | 118 ms | — |
| 2026-09-17 22:40 UTC | GET | pass | 402 | 517 ms | — |
| 2026-09-17 13:40 UTC | GET | pass | 402 | 2072 ms | — |
| 2026-09-16 16:40 UTC | GET | pass | 402 | 172 ms | — |
| 2026-09-15 16:40 UTC | GET | pass | 402 | 165 ms | — |
| 2026-09-15 04:40 UTC | GET | pass | 402 | 194 ms | — |
| 2026-09-14 13:40 UTC | GET | pass | 402 | 226 ms | — |
| 2026-09-13 22:40 UTC | GET | pass | 402 | 258 ms | — |
| 2026-09-13 04:40 UTC | GET | pass | 402 | 179 ms | — |
| 2026-09-12 16:40 UTC | GET | pass | 402 | 114 ms | — |
| 2026-09-12 04:40 UTC | GET | pass | 402 | 191 ms | — |
| 2026-09-11 13:40 UTC | GET | pass | 402 | 106 ms | — |
| 2026-09-10 23:40 UTC | GET | pass | 402 | 218 ms | — |
3.L1 — real purchases
3 of 3 paid attempts settled on-chain, and 3 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.
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.
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).
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 |
|---|---|---|---|---|
| 09-16 18:012026-09-16 18:01 UTC | settled (nonce-bound) | 200 | 0x995f724d…c12f | 1397 ms |
| 1000 units (≈ $0.001 USDC) · L2 not_checked (recorded mismatch)Whose side: no failure (delivered) | ||||
| 09-10 01:002026-09-10 01:00 UTC | settled (nonce-bound) | 200 | 0x7cab86c6…cbe7 | 996 ms |
| 1000 units (≈ $0.001 USDC) · L2 not_checked (recorded mismatch)Whose side: no failure (delivered) | ||||
| 09-02 00:022026-09-02 00:02 UTC | settled (amount + payee) | 200 | 0xfc2c7276…7631 | 1037 ms |
| 1000 units (≈ $0.001 USDC) · L2 not_checked (recorded mismatch)Whose side: no failure (delivered) | ||||
Embed this record
Run this endpoint? Show the settle-through record vet402 measured — the badge reads 3/3 settled · 3 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/7238ec18-5650-464e-ad23-185e3c886e68)4.Catalog listing events
No listing changes observed.
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.