trust-agent.io/v1/registry/agents
1.Catalog declaration
| Resource URL | https://trust-agent.io/v1/registry/agents |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0x6121654d3fd4c8b42a90d30472e4d40927c3e6bb |
| Declared price (base units) | 10000 |
| Catalog status | active |
| First seen / last seen | 2026-08-17 01:06 UTC / 2026-09-05 01:03 UTC |
| Catalog-reported calls / payers (30d) | 3 / 3 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-04 23:40 UTC | GET | pass | 402 | 115 ms | — |
| 2026-09-04 14:40 UTC | GET | pass | 402 | 186 ms | — |
| 2026-09-01 23:14 UTC | GET | pass | 402 | 220 ms | — |
3.L1 — real purchases
1 of 1 paid attempts settled with a receipt, and 1 of those also returned a 2xx response (delivered). Each settled row carries its on-chain transaction hash — the receipt is the evidence. 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 4xx or 5xx counts as settled and not as delivered — definitions.
| Attempted at | Result | HTTP | Receipt (tx) | Latency |
|---|---|---|---|---|
| 09-04 12:092026-09-04 12:09 UTC | settled (nonce-bound) | 200 | 0x6513c492…475c | 1079 ms |
| 10000 units (≈ $0.01 USDC) · L2 mismatch | ||||
Embed this record
Run this endpoint? Show the settle-through record vet402 measured — the badge reads 1/1 settled · 1 delivered and updates as the record grows. It states a measurement, not a rating.
[](https://vet402.com/observatory/e/ca9187ac-459a-43f6-9f6c-fc2e0bdeef64)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.