agents.allium.so/api/v1/developer/wallet/pnl
Withdrawn from the catalog. This route is absent from a complete fetch of the public discovery catalog, so it is left out of the public L0 fail count.
1.Catalog declaration
| Resource URL | https://agents.allium.so/api/v1/developer/wallet/pnl |
| Source | circle_discovery |
| Declared method | POST |
| Catalog network | eip155:8453 |
| Receiving address | 0x050d803e21c834806871f0ae1d54232c22599606 |
| Declared price (base units) | 10000 |
| Catalog status | delisted (since 2026-11-01 01:30 UTC) |
| First seen / last seen | 2026-10-26 01:30 UTC / 2026-10-31 01:30 UTC |
| Catalog-reported calls / payers (30d) | — / — |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-31 10:30 UTC | POST | fail | 404 | 77 ms | no_402HTTP 404 instead of 402 to an unpaid POST. |
| 2026-10-30 10:30 UTC | POST | fail | 402 | 657 ms | metadata_mismatchDeclared payTo 0x549f…47d2 on eip155:8453; the 402 offered 0xc6e7…ee78 on eip155:8453, wGwFBo…nJDQ on solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp, 0xF5B5…68CA on eip155:137. |
| 2026-10-29 10:30 UTC | POST | fail | 402 | 619 ms | metadata_mismatchDeclared payTo 0x9373…d71c on eip155:8453; the 402 offered 0xed75…27ac on eip155:8453, GQHY2u…YVdc on solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp, 0xF5B5…68CA on eip155:137. |
| 2026-10-28 10:31 UTC | POST | fail | 402 | 945 ms | metadata_mismatchDeclared payTo 0xd1a5…26d8 on eip155:8453; the 402 offered 0x8aef…6b19 on eip155:8453, 7VbSqk…XAGg on solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp, 0x61Fd…Cada on eip155:196, 0xF5B5…68CA on eip155:137. |
| 2026-10-27 10:30 UTC | POST | fail | 402 | 742 ms | metadata_mismatchDeclared payTo 0x662c…07f1 on eip155:8453; the 402 offered 0x011b…b81a on eip155:8453, 9pFo8H…yVMa on solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp, 0x61Fd…Cada on eip155:196, 0xF5B5…68CA on eip155:137. |
3.L1 — real purchases
No paid purchases recorded for this endpoint yet.
4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-11-01 | 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
A dispute does not start a purchase. The signed dispute route runs one fresh L0 check, an unpaid request.
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. This listing is not active in the catalog, so a dispute filed on the record form does not put it on the re-probe list. The record stays on this page. The scheduled L0 run is at 10:30 UTC. This listing is not on that run. Send the dispute to support@vet402.com. Published corrections are listed at /corrections. Operators who control the receiving address can also sign a dispute via POST /api/v1/observatory/disputes (API reference). That route runs one fresh L0 check under the normal publication gate. A later purchase comes from the regular schedule.