Skip to main content
Independent MeasurementEndpoint record (L0 · L1)Published state: withdrawnLast probed: 2026-10-25 · 28 days ago

api.erb-llm.com/v1/long

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

Catalog declaration for this endpoint
Resource URLhttps://api.erb-llm.com/v1/long
Sourcecdp_bazaar
Declared methodPOST
Catalog networkeip155:8453
Receiving address0x23976fb6af8f7fe8756730f0473fb7ffac531ee8
Declared price (base units)10000
Catalog statusdelisted (since 2026-10-26 13:05 UTC)
First seen / last seen2026-08-24 02:00 UTC / 2026-10-23 13:02 UTC
Catalog-reported calls / payers (30d)11 / 5

2.Probe history

2026-09-092026-10-25
Figure 1. Probe timeline, last 21 probes for this endpoint (UTC). Filled = pass, crossed = fail, dashed = unverified. Same-day probes overlap. Marks closer than one mark width are stepped down one lane.
L0 probe history, newest first
Probed atMethodVerdictHTTPLatencyReason
2026-10-25 18:40 UTCPOSTfail530162 msno_402HTTP 530 instead of 402 to an unpaid POST.
2026-10-23 16:40 UTCPOSTfail530363 msno_402HTTP 530 instead of 402 to an unpaid POST.
2026-10-22 04:40 UTCPOSTpass402546 ms—
2026-10-20 16:40 UTCPOSTpass402546 ms—
2026-10-19 13:40 UTCPOSTpass402348 ms—
2026-10-17 16:40 UTCPOSTpass402276 ms—
2026-10-16 12:40 UTCPOSTpass402339 ms—
2026-10-14 21:40 UTCPOSTpass4022312 ms—
2026-10-13 15:40 UTCPOSTpass4021869 ms—
2026-10-12 12:40 UTCPOSTpass4021663 ms—
2026-10-11 12:40 UTCPOSTpass402364 ms—
2026-10-10 12:40 UTCPOSTpass402333 ms—
2026-10-09 12:40 UTCPOSTpass402400 ms—
2026-10-07 22:40 UTCPOSTpass402453 ms—
2026-10-07 04:40 UTCPOSTpass4021011 ms—
2026-10-06 04:41 UTCPOSTpass402660 ms—
2026-10-04 16:40 UTCPOSTpass402197 ms—
2026-10-03 22:40 UTCPOSTpass402431 ms—
2026-10-03 04:40 UTCPOSTpass402576 ms—
2026-10-02 10:30 UTCPOSTpass402289 ms—
2026-09-09 11:24 UTCPOSTfail530145 msno_402HTTP 530 instead of 402 to an unpaid POST.

3.L1 — real purchases

2 of 2 paid attempts settled on-chain, and 0 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 vet402's 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.

A row marked tx from vet402's 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. vet402 did (methodology).

Terms in this table

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.
Stage settled
vet402 re-read the payment on the chain. The paid request answered 202 Accepted, or HTTP 2xx with a body vet402 recorded as empty, or vet402 has no HTTP status on record, so vet402 does not call it delivered or not_delivered.
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).
2/2
Figure 2. Settle-through: one cell per paid attempt. Filled = settled on-chain, crossed = signed, and not settled on-chain.
L1 purchase history, newest first
Attempted atResultHTTPOn-chain txPayment chainLatency
10-12 23:01settled (nonce-bound)tx from vet402's index—0x2431e70f…ebe5Base20402 ms
10000 units (≈ $0.01 USDC) · L2 not_checkedWhose side: not sorted: vet402 stopped waitingStage: settled
10-04 00:02settled (nonce-bound)tx from vet402's index—0xfd86fba9…4143Base20307 ms
50000 units (≈ $0.05 USDC) · L2 not_checkedWhose side: not sorted: vet402 stopped waitingStage: settled

Add this badge to your docs

Run this endpoint? Show the settle-through record vet402 measured — the badge reads 2/2 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.

vet402: 2 of 2 paid attempts settled with an on-chain receipt, and 0 of those also returned a deliverable HTTP 2xx response. settled is the confirmed transfer; delivered is a 2xx other than 202 with a non-empty body. A measurement of what happened when vet402 paid this endpoint, not a recommendation. (api.erb-llm.com · measured 2026-10-12)

[![vet402 receipt](https://vet402.com/api/badge/endpoint/fb9840c7-cbbd-4953-8f35-f6d4b10144e2.svg)](https://vet402.com/observatory/e/fb9840c7-cbbd-4953-8f35-f6d4b10144e2)

Get one email when this record's verdict changes. No digest, no marketing — one message per change, and only for this endpoint. We first send one confirmation email; nothing else goes out until you confirm.

4.Catalog listing events

Catalog listing events, newest first
Detected onEventBeforeAfter
2026-10-26delisted{"status":"active"}{"status":"delisted"}
2026-10-02relisted{"status":"delisted"}{"status":"active"}
2026-09-10delisted{"status":"active"}{"status":"delisted"}
2026-09-09relisted{"status":"delisted"}{"status":"active"}
2026-08-26delisted{"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.

20–2,000 characters · 0 so far