api.robinx.io/social/follows
1.Catalog declaration
| Resource URL | https://api.robinx.io/social/follows |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0xa13d363aecccf878ec64f6eb687eb4a771fb0599 |
| Declared price (base units) | 20000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-10-02 01:04 UTC |
| Catalog-reported calls / payers (30d) | 3 / 3 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-01 22:40 UTC | GET | pass | 402 | 166 ms | — |
| 2026-10-01 04:40 UTC | GET | pass | 402 | 283 ms | — |
| 2026-09-30 13:40 UTC | GET | pass | 402 | 203 ms | — |
| 2026-09-29 16:40 UTC | GET | pass | 402 | 547 ms | — |
| 2026-09-28 22:40 UTC | GET | pass | 402 | 83 ms | — |
| 2026-09-28 04:40 UTC | GET | pass | 402 | 193 ms | — |
| 2026-09-27 13:40 UTC | GET | pass | 402 | 113 ms | — |
| 2026-09-26 16:40 UTC | GET | pass | 402 | 143 ms | — |
| 2026-09-25 22:40 UTC | GET | pass | 402 | 171 ms | — |
| 2026-09-25 04:40 UTC | GET | pass | 402 | 206 ms | — |
| 2026-09-24 16:40 UTC | GET | pass | 402 | 204 ms | — |
| 2026-09-23 22:40 UTC | GET | pass | 402 | 151 ms | — |
| 2026-09-23 04:40 UTC | GET | pass | 402 | 353 ms | — |
| 2026-09-22 13:40 UTC | GET | pass | 402 | 266 ms | — |
| 2026-09-21 16:40 UTC | GET | pass | 402 | 164 ms | — |
| 2026-09-20 22:40 UTC | GET | pass | 402 | 341 ms | — |
| 2026-09-20 04:40 UTC | GET | pass | 402 | 185 ms | — |
| 2026-09-19 13:40 UTC | GET | pass | 402 | 2062 ms | — |
| 2026-09-18 16:40 UTC | GET | pass | 402 | 115 ms | — |
| 2026-09-18 04:40 UTC | GET | pass | 402 | 322 ms | — |
| 2026-09-17 13:40 UTC | GET | pass | 402 | 318 ms | — |
| 2026-09-16 16:40 UTC | GET | pass | 402 | 70 ms | — |
| 2026-09-15 22:40 UTC | GET | pass | 402 | 60 ms | — |
| 2026-09-15 04:40 UTC | GET | pass | 402 | 24 ms | — |
| 2026-09-14 16:40 UTC | GET | pass | 402 | 609 ms | — |
| 2026-09-13 22:40 UTC | GET | pass | 402 | 275 ms | — |
| 2026-09-13 13:40 UTC | GET | pass | 402 | 244 ms | — |
| 2026-09-12 16:40 UTC | GET | pass | 402 | 32 ms | — |
| 2026-09-12 04:40 UTC | GET | pass | 402 | 104 ms | — |
| 2026-09-11 13:40 UTC | GET | pass | 402 | 376 ms | — |
3.L1 — real purchases
4 of 4 paid attempts settled on-chain, and 4 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 no_declaration- the listing declares no output schema to check the response against.
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-10 19:022026-09-10 19:02 UTC | settled (nonce-bound) | 200 | 0x5179bfe8…947a | 1811 ms |
| 20000 units (≈ $0.02 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 08-30 12:082026-08-30 12:08 UTC | settled (amount + payee) | 200 | 0x811706a2…9b55 | 1393 ms |
| 20000 units (≈ $0.02 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 08-23 12:422026-08-23 12:42 UTC | settled (amount + payee) | 200 | 0xcaf2ef3c…1135 | 1505 ms |
| 20000 units (≈ $0.02 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 08-16 12:482026-08-16 12:48 UTC | settled (amount + payee) | 200 | 0x94a7f6bc…2462 | 1594 ms |
| 20000 units (≈ $0.02 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
Embed this record
Run this endpoint? Show the settle-through record vet402 measured — the badge reads 4/4 settled · 4 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/8587e02d-c930-4351-92ec-c75ec85a7367)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.