api.glianalabs.com/x402/tools/exchange-rate
1.Catalog declaration
| Resource URL | https://api.glianalabs.com/x402/tools/exchange-rate |
| Source | cdp_bazaar |
| Declared method | POST |
| Network | eip155:8453 |
| Receiving address | 0x7662e00f8ab4c362166e1ff649ff6c2a638c80ad |
| Declared price (base units) | 2000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:52 UTC / 2026-10-03 01:04 UTC |
| Catalog-reported calls / payers (30d) | 2 / 2 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-04 13:40 UTC | POST | pass | 402 | 486 ms | — |
| 2026-10-03 16:40 UTC | POST | pass | 402 | 565 ms | — |
| 2026-10-02 16:40 UTC | POST | pass | 402 | 2291 ms | — |
| 2026-10-01 22:40 UTC | POST | pass | 402 | 2491 ms | — |
| 2026-10-01 04:40 UTC | POST | pass | 402 | 446 ms | — |
| 2026-09-30 13:40 UTC | POST | pass | 402 | 539 ms | — |
| 2026-09-29 16:40 UTC | POST | pass | 402 | 167 ms | — |
| 2026-09-28 22:40 UTC | POST | pass | 402 | 523 ms | — |
| 2026-09-28 04:40 UTC | POST | pass | 402 | 527 ms | — |
| 2026-09-27 13:40 UTC | POST | pass | 402 | 578 ms | — |
| 2026-09-26 16:40 UTC | POST | pass | 402 | 127 ms | — |
| 2026-09-25 22:40 UTC | POST | pass | 402 | 2034 ms | — |
| 2026-09-25 04:40 UTC | POST | pass | 402 | 384 ms | — |
| 2026-09-24 13:40 UTC | POST | pass | 402 | 255 ms | — |
| 2026-09-23 16:40 UTC | POST | pass | 402 | 412 ms | — |
| 2026-09-22 22:40 UTC | POST | pass | 402 | 408 ms | — |
| 2026-09-22 04:40 UTC | POST | pass | 402 | 310 ms | — |
| 2026-09-21 13:40 UTC | POST | pass | 402 | 348 ms | — |
| 2026-09-20 16:40 UTC | POST | pass | 402 | 22 ms | — |
| 2026-09-19 22:40 UTC | POST | pass | 402 | 432 ms | — |
| 2026-09-19 13:40 UTC | POST | pass | 402 | 550 ms | — |
| 2026-09-18 16:40 UTC | POST | pass | 402 | 236 ms | — |
| 2026-09-17 22:40 UTC | POST | pass | 402 | 91 ms | — |
| 2026-09-17 04:40 UTC | POST | pass | 402 | 397 ms | — |
| 2026-09-16 16:40 UTC | POST | pass | 402 | 401 ms | — |
| 2026-09-15 16:40 UTC | POST | pass | 402 | 206 ms | — |
| 2026-09-15 04:40 UTC | POST | pass | 402 | 173 ms | — |
| 2026-09-14 13:40 UTC | POST | pass | 402 | 260 ms | — |
| 2026-09-13 16:40 UTC | POST | fail | — | 10001 ms | timeoutNo response headers arrived within 10 seconds. |
| 2026-09-13 04:40 UTC | POST | fail | — | 10000 ms | timeoutNo response headers arrived within 10 seconds. |
3.L1 — real purchases
1 of 1 paid attempts settled on-chain, and 1 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 (amount + payee)- vet402 confirmed the USDC transfer on-chain; the on-chain re-read matched amount, payee, asset and chain; no nonce was on record (rows before 2026-09-04).
L2 no_declaration- the listing declares no output schema to check the response against.
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-04 09:252026-09-04 09:25 UTC | settled (amount + payee) | 200 | 0x8ef3d838…3a33 | 2895 ms |
| 2000 units (≈ $0.002 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
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 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/92a52f2d-e09c-4705-acca-033327f7d283)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.