api.kakerapetit.dev/v1/text/similarity
1.Catalog declaration
| Resource URL | https://api.kakerapetit.dev/v1/text/similarity |
| Source | cdp_bazaar |
| Declared method | POST |
| Network | eip155:8453 |
| Receiving address | 0x3a43fdf92b1596b22ddf719d5b528c537da4237d |
| Declared price (base units) | 2000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-09-30 01:03 UTC |
| Catalog-reported calls / payers (30d) | 7 / 2 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-29 22:40 UTC | POST | pass | 402 | 264 ms | — |
| 2026-09-29 04:40 UTC | POST | pass | 402 | 424 ms | — |
| 2026-09-28 13:40 UTC | POST | pass | 402 | 368 ms | — |
| 2026-09-27 16:40 UTC | POST | pass | 402 | 538 ms | — |
| 2026-09-26 22:40 UTC | POST | pass | 402 | 483 ms | — |
| 2026-09-26 04:40 UTC | POST | pass | 402 | 582 ms | — |
| 2026-09-25 13:40 UTC | POST | pass | 402 | 903 ms | — |
| 2026-09-24 16:40 UTC | POST | pass | 402 | 496 ms | — |
| 2026-09-24 04:40 UTC | POST | pass | 402 | 497 ms | — |
| 2026-09-23 13:40 UTC | POST | pass | 402 | 579 ms | — |
| 2026-09-22 16:40 UTC | POST | pass | 402 | 274 ms | — |
| 2026-09-21 22:40 UTC | POST | pass | 402 | 744 ms | — |
| 2026-09-21 04:40 UTC | POST | pass | 402 | 408 ms | — |
| 2026-09-20 13:40 UTC | POST | pass | 402 | 2360 ms | — |
| 2026-09-19 16:40 UTC | POST | pass | 402 | 434 ms | — |
| 2026-09-18 22:40 UTC | POST | pass | 402 | 2434 ms | — |
| 2026-09-18 04:40 UTC | POST | pass | 402 | 203 ms | — |
| 2026-09-17 16:40 UTC | POST | pass | 402 | 468 ms | — |
| 2026-09-16 22:40 UTC | POST | pass | 402 | 657 ms | — |
| 2026-09-15 22:40 UTC | POST | pass | 402 | 576 ms | — |
| 2026-09-15 13:40 UTC | POST | pass | 402 | 428 ms | — |
| 2026-09-14 16:40 UTC | POST | pass | 402 | 612 ms | — |
| 2026-09-14 04:40 UTC | POST | pass | 402 | 340 ms | — |
| 2026-09-13 13:40 UTC | POST | pass | 402 | 61 ms | — |
| 2026-09-12 22:40 UTC | POST | pass | 402 | 299 ms | — |
| 2026-09-12 04:40 UTC | POST | pass | 402 | 327 ms | — |
| 2026-09-11 16:40 UTC | POST | pass | 402 | 451 ms | — |
| 2026-09-11 04:40 UTC | POST | pass | 402 | 401 ms | — |
| 2026-09-10 14:40 UTC | POST | pass | 402 | 127 ms | — |
| 2026-09-09 23:40 UTC | POST | pass | 402 | 85 ms | — |
3.L1 — real purchases
2 of 4 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.
settle_failed- vet402 signed a payment and got no settlement receipt back.
L2 no_declaration- the listing declares no output schema to check the response against.
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-27 00:012026-09-27 00:01 UTC | settled (nonce-bound) | 200 | 0xee61446b…55cf | 1289 ms |
| 2000 units (≈ $0.002 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 09-20 18:022026-09-20 18:02 UTC | settled (nonce-bound) | 200 | 0x84cf4c85…c778 | 1407 ms |
| 2000 units (≈ $0.002 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 09-12 06:012026-09-12 06:01 UTC | settle_failed | 500 | — | 546 ms |
| 2000 units (≈ $0.002 USDC) · L2 not_checkedWhose side: not sorted: vet402 unproven | ||||
| 09-02 19:022026-09-02 19:02 UTC | settle_failed | 500 | — | 550 ms |
| 2000 units (≈ $0.002 USDC) · L2 not_checkedWhose side: not sorted: vet402 unproven | ||||
Embed this record
Run this endpoint? Show the settle-through record vet402 measured — the badge reads 2/4 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/5fd70cac-591c-43a0-85d9-ec715d4c2136)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.