tensorfeed.ai/api/premium/research/milestones
1.Catalog declaration
| Resource URL | https://tensorfeed.ai/api/premium/research/milestones |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0x549c82e6bfc54bdae9a2073744cbc2af5d1fc6d1 |
| Declared price (base units) | 20000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-10-01 01:03 UTC |
| Catalog-reported calls / payers (30d) | 4 / 3 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-30 13:40 UTC | GET | pass | 402 | 421 ms | — |
| 2026-09-29 13:40 UTC | GET | pass | 402 | 361 ms | — |
| 2026-09-28 16:40 UTC | GET | pass | 402 | 533 ms | — |
| 2026-09-27 22:40 UTC | GET | pass | 402 | 2222 ms | — |
| 2026-09-27 13:40 UTC | GET | pass | 402 | 356 ms | — |
| 2026-09-26 16:40 UTC | GET | pass | 402 | 272 ms | — |
| 2026-09-25 22:40 UTC | GET | pass | 402 | 400 ms | — |
| 2026-09-25 04:40 UTC | GET | pass | 402 | 586 ms | — |
| 2026-09-24 13:40 UTC | GET | pass | 402 | 427 ms | — |
| 2026-09-23 16:40 UTC | GET | pass | 402 | 1316 ms | — |
| 2026-09-22 22:40 UTC | GET | pass | 402 | 624 ms | — |
| 2026-09-22 04:40 UTC | GET | pass | 402 | 556 ms | — |
| 2026-09-21 13:40 UTC | GET | pass | 402 | 199 ms | — |
| 2026-09-20 16:40 UTC | GET | pass | 402 | 589 ms | — |
| 2026-09-19 22:40 UTC | GET | pass | 402 | 362 ms | — |
| 2026-09-19 04:40 UTC | GET | pass | 402 | 391 ms | — |
| 2026-09-18 16:40 UTC | GET | pass | 402 | 426 ms | — |
| 2026-09-17 22:40 UTC | GET | pass | 402 | 360 ms | — |
| 2026-09-17 04:40 UTC | GET | pass | 402 | 384 ms | — |
| 2026-09-16 16:40 UTC | GET | pass | 402 | 822 ms | — |
| 2026-09-15 16:40 UTC | GET | pass | 402 | 406 ms | — |
| 2026-09-14 22:40 UTC | GET | pass | 402 | 654 ms | — |
| 2026-09-14 13:40 UTC | GET | pass | 402 | 630 ms | — |
| 2026-09-13 16:40 UTC | GET | pass | 402 | 455 ms | — |
| 2026-09-13 04:40 UTC | GET | pass | 402 | 383 ms | — |
| 2026-09-12 13:40 UTC | GET | pass | 402 | 2051 ms | — |
| 2026-09-11 22:40 UTC | GET | pass | 402 | 521 ms | — |
| 2026-09-11 13:40 UTC | GET | pass | 402 | 420 ms | — |
| 2026-09-10 17:40 UTC | GET | pass | 402 | 503 ms | — |
| 2026-09-10 05:40 UTC | GET | pass | 402 | 441 ms | — |
3.L1 — real purchases
2 of 2 paid attempts settled on-chain, and 2 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.
L2 no_declaration- the listing declares no output schema to check the response against.
L2 mismatch- the response lacked 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-30 21:322026-09-30 21:32 UTC | settled (nonce-bound) | 200 | 0xfbcfecae…1bc3 | 3083 ms |
| 20000 units (≈ $0.02 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 09-07 19:012026-09-07 19:01 UTC | settled (nonce-bound) | 200 | 0x5a26d97d…77d5 | 4591 ms |
| 20000 units (≈ $0.02 USDC) · L2 mismatchWhose side: no failure (delivered) | ||||
Embed this record
Run this endpoint? Show the settle-through record vet402 measured — the badge reads 2/2 settled · 2 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/ea620d40-e7ee-4d2c-9c12-09674c1d39ab)4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-09-09 | relisted | {"status":"delisted"} | {"status":"active"} |
| 2026-09-08 | delisted | {"status":"active"} | {"status":"delisted"} |
| 2026-09-02 | relisted | {"status":"delisted"} | {"status":"active"} |
| 2026-08-31 | 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.