api.erb-llm.com/v1/chat/completions
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://api.erb-llm.com/v1/chat/completions |
| Source | cdp_bazaar |
| Declared method | POST |
| Catalog network | eip155:8453 |
| Receiving address | 0x23976fb6af8f7fe8756730f0473fb7ffac531ee8 |
| Declared price (base units) | 1000 |
| Catalog status | delisted (since 2026-10-26 13:05 UTC) |
| First seen / last seen | 2026-08-23 01:18 UTC / 2026-10-23 13:02 UTC |
| Catalog-reported calls / payers (30d) | 23 / 5 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-25 06:40 UTC | POST | fail | 530 | 111 ms | no_402HTTP 530 instead of 402 to an unpaid POST. |
| 2026-10-23 04:40 UTC | POST | pass | 402 | 2396 ms | — |
| 2026-10-21 16:40 UTC | POST | pass | 402 | 463 ms | — |
| 2026-10-20 04:40 UTC | POST | pass | 402 | 333 ms | — |
| 2026-10-18 16:40 UTC | POST | pass | 402 | 276 ms | — |
| 2026-10-17 13:40 UTC | POST | pass | 402 | 547 ms | — |
| 2026-10-15 21:40 UTC | POST | pass | 402 | 901 ms | — |
| 2026-10-14 12:40 UTC | POST | pass | 402 | 331 ms | — |
| 2026-10-13 03:40 UTC | POST | pass | 402 | 346 ms | — |
| 2026-10-12 03:40 UTC | POST | pass | 402 | 767 ms | — |
| 2026-10-11 03:40 UTC | POST | pass | 402 | 404 ms | — |
| 2026-10-09 21:40 UTC | POST | pass | 402 | 1766 ms | — |
| 2026-10-08 16:40 UTC | POST | pass | 402 | 1257 ms | — |
| 2026-10-07 16:40 UTC | POST | pass | 402 | 343 ms | — |
| 2026-10-06 16:40 UTC | POST | pass | 402 | 439 ms | — |
| 2026-10-05 22:40 UTC | POST | fail | 402 | 587 ms | price_mismatchDeclared 5000 of 0x8335…2913; the 402 offered 1000 of 0x8335…2913. |
| 2026-10-04 13:40 UTC | POST | pass | 402 | 522 ms | — |
| 2026-10-03 16:40 UTC | POST | pass | 402 | 526 ms | — |
| 2026-10-02 22:40 UTC | POST | pass | 402 | 466 ms | — |
| 2026-10-02 04:40 UTC | POST | pass | 402 | 693 ms | — |
| 2026-09-09 11:24 UTC | POST | fail | 530 | 219 ms | no_402HTTP 530 instead of 402 to an unpaid POST. |
3.L1 — real purchases
1 of 2 paid attempts settled on-chain, and 1 of those also returned a deliverable 2xx response (delivered: other than 202 Accepted with a non-empty body). 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 matched the one-time value stored for that purchase, so the transaction is the one for this purchase. Stellar is not in this count. The Stellar re-read checks payer, payee, amount and asset. A row reads as amount + payee when the re-read matched payer, payee, amount and asset and did not bind a one-time value. That tier holds rows from before 2026-09-04 and Stellar rows. They keep the settled label rather than being demoted (methodology). settled is the transfer vet402 confirmed on-chain. delivered is a 2xx other than 202 with a non-empty body. A settled row whose paid request answered 5xx counts as settled and not as delivered. definitions.
Terms in this table
settle_failed- vet402 signed a payment and got no settlement receipt back.
settled (nonce-bound)- vet402 re-read the transfer on-chain in that chain's pinned settlement asset, and the on-chain re-read matched the one-time value stored for that purchase, so the transaction is the one for this purchase. Stellar is not in this count.
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.
L2 match- the response parsed as JSON and had each key the declaration marks as required.
Stage signed- vet402 signed a paid request. vet402 has not settled it on chain yet, or settlement failed, or the seller returned goods without a receipt.
Stage delivered- vet402 re-read the payment on the chain and the paid request returned HTTP 2xx other than 202 Accepted with a body vet402 did not record as empty.
Whose side- the same words as the seller page: seller's side only after failures on two different days (UTC), marked “attribution under review”; vet402's side; or not sorted (the rules).
| Attempted at | Result | HTTP | On-chain tx | Payment chain | Latency |
|---|---|---|---|---|---|
| 10-11 17:012026-10-11 17:01 UTC | settle_failed (withdrawn from the catalog) | — | — | Base | 20324 ms |
| 1000 units (≈ $0.001 USDC) · L2 not_checkedWhose side: not sorted: vet402 stopped waitingLeft out of the public L0 fail count.Stage: signed | |||||
| 10-02 06:012026-10-02 06:01 UTC | settled (nonce-bound) | 200 | 0xb634edbe…c91e | Base | 8311 ms |
| 5000 units (≈ $0.005 USDC) · L2 matchWhose side: no failure (delivered)Stage: delivered | |||||
Embed this record
Run this endpoint? Show the settle-through record vet402 measured — the badge reads 1/2 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/0b7d24f7-c2eb-4189-bf9d-c6f30ed48ee0)4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-10-26 | delisted | {"status":"active"} | {"status":"delisted"} |
| 2026-10-02 | relisted | {"status":"delisted"} | {"status":"active"} |
| 2026-09-10 | delisted | {"status":"active"} | {"status":"delisted"} |
| 2026-09-09 | relisted | {"status":"delisted"} | {"status":"active"} |
| 2026-08-26 | 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.