human.twin3.ai/v1/human
1.Catalog declaration
| Resource URL | https://human.twin3.ai/v1/human |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0xcd3273893d1c8df15a4d6bc411aa3d25a60fdc60 |
| Declared price (base units) | 1000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-10-03 01:04 UTC |
| Catalog-reported calls / payers (30d) | 207 / 8 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-04 13:40 UTC | GET | pass | 402 | 382 ms | — |
| 2026-10-03 16:40 UTC | GET | pass | 402 | 384 ms | — |
| 2026-10-02 22:40 UTC | GET | pass | 402 | 379 ms | — |
| 2026-10-01 22:40 UTC | GET | pass | 402 | 313 ms | — |
| 2026-10-01 04:40 UTC | GET | pass | 402 | 236 ms | — |
| 2026-09-30 13:40 UTC | GET | pass | 402 | 387 ms | — |
| 2026-09-29 16:40 UTC | GET | pass | 402 | 416 ms | — |
| 2026-09-28 22:40 UTC | GET | pass | 402 | 274 ms | — |
| 2026-09-28 04:40 UTC | GET | pass | 402 | 483 ms | — |
| 2026-09-27 13:40 UTC | GET | pass | 402 | 322 ms | — |
| 2026-09-26 16:40 UTC | GET | pass | 402 | 354 ms | — |
| 2026-09-25 22:40 UTC | GET | pass | 402 | 2396 ms | — |
| 2026-09-25 04:40 UTC | GET | pass | 402 | 317 ms | — |
| 2026-09-24 13:40 UTC | GET | pass | 402 | 255 ms | — |
| 2026-09-23 16:40 UTC | GET | pass | 402 | 370 ms | — |
| 2026-09-22 22:40 UTC | GET | pass | 402 | 287 ms | — |
| 2026-09-22 13:40 UTC | GET | pass | 402 | 501 ms | — |
| 2026-09-21 16:40 UTC | GET | pass | 402 | 330 ms | — |
| 2026-09-20 22:40 UTC | GET | pass | 402 | 371 ms | — |
| 2026-09-20 04:40 UTC | GET | pass | 402 | 369 ms | — |
| 2026-09-19 13:40 UTC | GET | pass | 402 | 2292 ms | — |
| 2026-09-18 16:40 UTC | GET | pass | 402 | 273 ms | — |
| 2026-09-17 22:40 UTC | GET | pass | 402 | 2146 ms | — |
| 2026-09-17 13:40 UTC | GET | pass | 402 | 1056 ms | — |
| 2026-09-16 16:40 UTC | GET | pass | 402 | 301 ms | — |
| 2026-09-15 16:40 UTC | GET | pass | 402 | 314 ms | — |
| 2026-09-15 04:40 UTC | GET | pass | 402 | 281 ms | — |
| 2026-09-14 13:40 UTC | GET | pass | 402 | 319 ms | — |
| 2026-09-13 22:40 UTC | GET | pass | 402 | 354 ms | — |
| 2026-09-13 04:40 UTC | GET | pass | 402 | 291 ms | — |
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
settle_failed- vet402 signed a payment and got no settlement receipt back.
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-17 12:532026-09-17 12:53 UTC | settle_failed | 402 | — | 1608 ms |
| 1000 units (≈ $0.001 USDC) · L2 not_checkedWhose side: not sorted: vet402 unproven | ||||
| 09-10 01:012026-09-10 01:01 UTC | settle_failed | 402 | — | 851 ms |
| 1000 units (≈ $0.001 USDC) · L2 not_checkedWhose side: not sorted: vet402 unproven | ||||
| 09-02 12:082026-09-02 12:08 UTC | settle_failed | 402 | — | 762 ms |
| 1000 units (≈ $0.001 USDC) · L2 not_checkedWhose side: not sorted: vet402 unproven | ||||
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.