stableenrich.dev/api/fullenrich/people-search
1.Catalog declaration
| Resource URL | https://stableenrich.dev/api/fullenrich/people-search |
| Source | cdp_bazaar |
| Declared method | POST |
| Network | eip155:8453 |
| Receiving address | 0x325bdf6f7efab24a2210c48c1b64cab2eae1d430 |
| Declared price (base units) | 150000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-10-03 01:04 UTC |
| Catalog-reported calls / payers (30d) | 1,013 / 58 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-04 13:40 UTC | POST | pass | 402 | 145 ms | — |
| 2026-10-03 16:40 UTC | POST | pass | 402 | 236 ms | — |
| 2026-10-02 16:40 UTC | POST | pass | 402 | 270 ms | — |
| 2026-10-01 22:40 UTC | POST | pass | 402 | 278 ms | — |
| 2026-10-01 04:40 UTC | POST | pass | 402 | 319 ms | — |
| 2026-09-30 13:40 UTC | POST | pass | 402 | 265 ms | — |
| 2026-09-29 16:40 UTC | POST | pass | 402 | 338 ms | — |
| 2026-09-28 22:40 UTC | POST | pass | 402 | 980 ms | — |
| 2026-09-28 04:40 UTC | POST | pass | 402 | 337 ms | — |
| 2026-09-27 13:40 UTC | POST | pass | 402 | 565 ms | — |
| 2026-09-26 16:40 UTC | POST | pass | 402 | 545 ms | — |
| 2026-09-25 22:40 UTC | POST | pass | 402 | 1835 ms | — |
| 2026-09-25 04:40 UTC | POST | pass | 402 | 1107 ms | — |
| 2026-09-24 13:40 UTC | POST | pass | 402 | 2092 ms | — |
| 2026-09-23 16:40 UTC | POST | pass | 402 | 199 ms | — |
| 2026-09-22 22:40 UTC | POST | pass | 402 | 104 ms | — |
| 2026-09-22 04:40 UTC | POST | pass | 402 | 421 ms | — |
| 2026-09-21 13:40 UTC | POST | pass | 402 | 227 ms | — |
| 2026-09-20 22:40 UTC | POST | pass | 402 | 590 ms | — |
| 2026-09-20 04:40 UTC | POST | pass | 402 | 82 ms | — |
| 2026-09-19 13:40 UTC | POST | pass | 402 | 160 ms | — |
| 2026-09-18 16:40 UTC | POST | pass | 402 | 66 ms | — |
| 2026-09-17 22:40 UTC | POST | pass | 402 | 229 ms | — |
| 2026-09-17 12:35 UTC | POST | pass | 402 | 71 ms | — |
| 2026-09-14 11:24 UTC | POST | pass | 402 | 152 ms | — |
| 2026-09-10 11:24 UTC | POST | pass | 402 | 235 ms | — |
| 2026-09-07 11:24 UTC | POST | pass | 402 | 405 ms | — |
| 2026-09-02 11:24 UTC | POST | pass | 402 | 154 ms | — |
| 2026-08-14 08:52 UTC | POST | fail | 402 | 40 ms | accepts_invalid402 without a payable accept in the header or the body (which part was missing was not recorded before the 2026-09-29 change). |
3.L1 — real purchases
0 of 3 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.
Terms in this table
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).
| Attempted at | Result | HTTP | On-chain tx | Latency |
|---|---|---|---|---|
| 09-20 18:002026-09-20 18:00 UTC | delivered_no_receipt | 200 | — | 592 ms |
| 150000 units (≈ $0.15 USDC) · L2 matchWhose side: not sorted: no charge | ||||
| 09-19 12:082026-09-19 12:08 UTC | delivered_no_receipt | 200 | — | 369 ms |
| 150000 units (≈ $0.15 USDC) · L2 matchWhose side: not sorted: no charge | ||||
| 09-18 00:012026-09-18 00:01 UTC | delivered_no_receipt | 200 | — | 6956 ms |
| 150000 units (≈ $0.15 USDC) · L2 matchWhose side: not sorted: no charge | ||||
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.