api.aidress.ai/pay/agent_voidfeed_ai
1.Catalog declaration
| Resource URL | https://api.aidress.ai/pay/agent_voidfeed_ai |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0x71033ab6ed376a0b53d1826ea632ddfec96b3661 |
| Declared price (base units) | 50000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-10-01 01:03 UTC |
| Catalog-reported calls / payers (30d) | 2 / 2 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-01 04:40 UTC | GET | pass | 402 | 1585 ms | — |
| 2026-09-30 13:40 UTC | GET | pass | 402 | 2196 ms | — |
| 2026-09-29 16:40 UTC | GET | pass | 402 | 1730 ms | — |
| 2026-09-28 22:40 UTC | GET | unverified | 429 | 1129 ms | rate_limitedThe endpoint answered 429; a rate limit is not a verdict on the payment wall. |
| 2026-09-28 04:40 UTC | GET | pass | 402 | 1193 ms | — |
| 2026-09-27 13:40 UTC | GET | pass | 402 | 1452 ms | — |
| 2026-09-26 16:40 UTC | GET | pass | 402 | 1544 ms | — |
| 2026-09-25 22:40 UTC | GET | pass | 402 | 1230 ms | — |
| 2026-09-25 04:40 UTC | GET | pass | 402 | 1059 ms | — |
| 2026-09-24 13:40 UTC | GET | pass | 402 | 1030 ms | — |
| 2026-09-23 16:40 UTC | GET | pass | 402 | 1140 ms | — |
| 2026-09-22 22:40 UTC | GET | pass | 402 | 1009 ms | — |
| 2026-09-22 04:40 UTC | GET | pass | 402 | 953 ms | — |
| 2026-09-21 13:40 UTC | GET | pass | 402 | 1636 ms | — |
| 2026-09-20 16:40 UTC | GET | pass | 402 | 1426 ms | — |
| 2026-09-19 22:40 UTC | GET | pass | 402 | 1383 ms | — |
| 2026-09-19 04:40 UTC | GET | pass | 402 | 790 ms | — |
| 2026-09-18 13:40 UTC | GET | pass | 402 | 1183 ms | — |
| 2026-09-17 22:40 UTC | GET | pass | 402 | 1284 ms | — |
| 2026-09-17 04:40 UTC | GET | pass | 402 | 1111 ms | — |
| 2026-09-16 13:40 UTC | GET | pass | 402 | 979 ms | — |
| 2026-09-15 16:40 UTC | GET | pass | 402 | 2382 ms | — |
| 2026-09-14 22:40 UTC | GET | pass | 402 | 2026 ms | — |
| 2026-09-14 04:40 UTC | GET | pass | 402 | 1818 ms | — |
| 2026-09-13 16:40 UTC | GET | pass | 402 | 1863 ms | — |
| 2026-09-12 22:40 UTC | GET | pass | 402 | 1001 ms | — |
| 2026-09-12 13:40 UTC | GET | pass | 402 | 1061 ms | — |
| 2026-09-11 16:40 UTC | GET | pass | 402 | 4723 ms | — |
| 2026-09-11 04:40 UTC | GET | pass | 402 | 1270 ms | — |
| 2026-09-10 14:40 UTC | GET | pass | 402 | 961 ms | — |
3.L1 — real purchases
1 of 1 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.
A row marked tx from our index came back with no settlement receipt from the seller. Our own index of on-chain settlements found the transfer afterwards — our payer, this endpoint's payee, the exact amount, inside the time window — and the row goes through the same on-chain re-read as any other before it reads settled. The seller did not name that transaction; we did (methodology).
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 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-03 19:012026-09-03 19:01 UTC | settled (amount + payee)tx from our index | 500 | 0x39196fed…fa04 | 3438 ms |
| 50000 units (≈ $0.05 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 1/1 settled · 0 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/f8f92500-d54f-45f7-a613-e5188bfda31e)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.