Independent MeasurementEndpoint record (L0 · L1)Published state: passLast probed: 2026-10-18 · 2 days ago
stablesocial.dev/api/sc/bluesky/user/posts
1.Catalog declaration
| Resource URL | https://stablesocial.dev/api/sc/bluesky/user/posts |
| Source | cdp_bazaar |
| Declared method | POST |
| Network | eip155:8453 |
| Receiving address | 0xcfa26f13c6c18307033ece13bbb8f470da5b4dbe |
| Declared price (base units) | 60000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:52 UTC / 2026-10-20 01:01 UTC |
| Catalog-reported calls / payers (30d) | 4 / 1 |
2.Probe history
2026-08-302026-10-18
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-18 22:40 UTC | POST | pass | 402 | 137 ms | — |
| 2026-10-17 16:40 UTC | POST | pass | 402 | 289 ms | — |
| 2026-10-03 10:30 UTC | POST | pass | 402 | 200 ms | — |
| 2026-09-26 10:30 UTC | POST | pass | 402 | 161 ms | — |
| 2026-09-22 11:24 UTC | POST | pass | 402 | 47 ms | — |
| 2026-09-18 11:24 UTC | POST | pass | 402 | 467 ms | — |
| 2026-09-15 11:24 UTC | POST | pass | 402 | 47 ms | — |
| 2026-09-11 11:24 UTC | POST | pass | 402 | 32 ms | — |
| 2026-09-08 11:24 UTC | POST | pass | 402 | 32 ms | — |
| 2026-09-03 11:24 UTC | POST | pass | 402 | 39 ms | — |
| 2026-08-30 11:24 UTC | POST | fail | 402 | 166 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
No paid purchases recorded for this endpoint yet.
4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-10-03 | relisted | {"status":"delisted"} | {"status":"active"} |
| 2026-09-27 | 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
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.