hirescrape.com/api/tools/tiktok
1.Catalog declaration
| Resource URL | https://hirescrape.com/api/tools/tiktok |
| Source | cdp_bazaar |
| Declared method | POST |
| Network | eip155:8453 |
| Receiving address | 0xb5194a98dbdbb7028b585db26b972e7f0f3f826a |
| Declared price (base units) | 2250 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-10-01 01:03 UTC |
| Catalog-reported calls / payers (30d) | 3 / 2 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-01 04:40 UTC | POST | pass | 402 | 370 ms | — |
| 2026-09-30 13:40 UTC | POST | pass | 402 | 264 ms | — |
| 2026-09-29 16:40 UTC | POST | pass | 402 | 340 ms | — |
| 2026-09-28 22:40 UTC | POST | pass | 402 | 73 ms | — |
| 2026-09-28 04:40 UTC | POST | pass | 402 | 1881 ms | — |
| 2026-09-27 13:40 UTC | POST | pass | 402 | 153 ms | — |
| 2026-09-26 16:40 UTC | POST | pass | 402 | 210 ms | — |
| 2026-09-25 22:40 UTC | POST | pass | 402 | 148 ms | — |
| 2026-09-25 13:40 UTC | POST | pass | 402 | 242 ms | — |
| 2026-09-24 16:40 UTC | POST | pass | 402 | 282 ms | — |
| 2026-09-23 22:40 UTC | POST | pass | 402 | 340 ms | — |
| 2026-09-23 04:40 UTC | POST | pass | 402 | 322 ms | — |
| 2026-09-22 13:40 UTC | POST | pass | 402 | 159 ms | — |
| 2026-09-21 16:40 UTC | POST | pass | 402 | 2055 ms | — |
| 2026-09-20 22:40 UTC | POST | pass | 402 | 2183 ms | — |
| 2026-09-20 04:40 UTC | POST | pass | 402 | 237 ms | — |
| 2026-09-19 13:40 UTC | POST | pass | 402 | 2033 ms | — |
| 2026-09-18 16:40 UTC | POST | pass | 402 | 143 ms | — |
| 2026-09-18 04:40 UTC | POST | pass | 402 | 319 ms | — |
| 2026-09-17 13:40 UTC | POST | pass | 402 | 209 ms | — |
| 2026-09-16 16:40 UTC | POST | pass | 402 | 135 ms | — |
| 2026-09-15 22:40 UTC | POST | pass | 402 | 99 ms | — |
| 2026-09-15 04:40 UTC | POST | pass | 402 | 40 ms | — |
| 2026-09-14 16:40 UTC | POST | pass | 402 | 514 ms | — |
| 2026-09-13 22:40 UTC | POST | pass | 402 | 249 ms | — |
| 2026-09-13 13:40 UTC | POST | pass | 402 | 189 ms | — |
| 2026-09-12 16:40 UTC | POST | pass | 402 | 82 ms | — |
| 2026-09-12 04:40 UTC | POST | pass | 402 | 145 ms | — |
| 2026-09-11 13:40 UTC | POST | pass | 402 | 384 ms | — |
| 2026-09-10 23:40 UTC | POST | pass | 402 | 85 ms | — |
3.L1 — real purchases
2 of 2 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.
2 of those paid attempts are held as inconclusive rather than counted against this seller (2 settled and answered 4xx, 0 answered 4xx with no settlement receipt, 0 answered 402 or 5xx while our own payer wallet was out of USDC, 2026-09-13 00:00 to 2026-09-15 23:49 UTC). A 4xx says the request was not one the server would accept, and we cannot rule out that the request was ours to get wrong: vet402 buys with no API key of the seller's, and sends a POST body only when the seller declares one. This is the same principle the methodology already applied to path_template URLs, applied to the body and the authentication header as well. The rows are not deleted and not hidden — they are below, with their status and HTTP code, and they are out of the denominator for delivered (corrections).
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_4xx- held_reason in the export: the payment settled, then the paid request got a 4xx.
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-11 12:092026-09-11 12:09 UTC | settled (nonce-bound) | 401 | 0xadcfae0f…784d | 988 ms |
| 2250 units (≈ $0.0022 USDC) · L2 not_checkedWhose side: not sorted (held) | ||||
| 09-05 01:002026-09-05 01:00 UTC | settled (nonce-bound) | 401 | 0xdeaa3669…f40b | 1168 ms |
| 2250 units (≈ $0.0022 USDC) · L2 not_checkedWhose side: not sorted (held) | ||||
Embed this record
Run this endpoint? Show the settle-through record vet402 measured — the badge reads 2/2 settled · 0 delivered · 2 inconclusive 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/6a6de86b-3f30-49c0-8dbb-683a6428a6f4)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.