Independent MeasurementSeller: purchase results on BaseRead from the database 2026-09-29 16:18 UTC · reused for up to 5 min

vet402Sellers · What to fix firstMethodology

api.losbeto.xyz: x402 purchase results on Base, latest attempt 2026-09-29

86 Base listings. Latest result about the seller at each listing: 13 delivered · 0 failed on the seller's side · 0 with no such result among the attempts shown · 73 not tried yet. This counts, for each listing, the newest purchase that delivered or the newest failure on the seller's side. Attempts on vet402's side, not bought, not sorted, or awaiting on-chain verification are skipped.

By the latest attempt at each listing, whatever it was: 13 delivered · 0 failed on the seller's side · 0 on vet402's side · 73 not tried yet.

Latest attempt: 2026-09-29 12:02 UTC. This page read the ledger at 2026-09-29 16:18 UTC and reuses that read for up to 5 min.

1.Your listings

api.losbeto.xyz/br-bizdaysGET
Latest attempt
2026-09-29 12:02 UTC
Result
delivered
Whose side
no failure (delivered)
Decision API now: asking… · the full answer
Latest L0 check (the 402 to an unpaid request): pass at 2026-09-29 04:40 UTC. Probes run oldest first, so there is no booked time; the next one usually comes by 2026-10-04 04:40 UTC (within 120 hours of the last).
What we saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.The 402 terms vet402 paid: exact · 0.004 USDC · payTo 0xd5ba…fe7d. Input sent: body none, query declared. The listing's maxTimeoutSeconds is 300; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.004 USDC · payTo 0xd5ba…fe7d · nonce 0x92fc…5da1 · validBefore not recorded.Answer to the paid request: HTTP 200 · Content-Type application/json · PAYMENT-RESPONSE: success true, names a transaction.Recorded (L1 paid purchase): settled (vet402 confirmed the USDC transfer on-chain) · HTTP 200 · tx 0x7641cc83…0687In export.csv?days=2: the row with attempted_at 2026-09-29T12:02:39Z and resource_key api.losbeto.xyz/br-bizdays.
After a fixNext purchase by vet402: Not before 2026-10-05 12:02 UTC (a listing is bought at most once every 6 days). After that it depends on the daily budget and the order of demand, so this is the earliest date, not a booking.Email me when this result changes Dispute this purchase
api.losbeto.xyz/fetchGET
Latest attempt
2026-09-29 00:02 UTC
Result
delivered
Whose side
no failure (delivered)
Decision API now: asking… · the full answer
Latest L0 check (the 402 to an unpaid request): pass at 2026-09-29 13:40 UTC. Probes run oldest first, so there is no booked time; the next one usually comes by 2026-10-04 13:40 UTC (within 120 hours of the last).
What we saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.The 402 terms vet402 paid: exact · 0.01 USDC · payTo 0xd5ba…fe7d. Input sent: body none, query declared. The listing's maxTimeoutSeconds is 300; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.01 USDC · payTo 0xd5ba…fe7d · nonce 0x5753…763b · validBefore not recorded.Answer to the paid request: HTTP 200 · Content-Type application/json · PAYMENT-RESPONSE: success true, names a transaction.Recorded (L1 paid purchase): settled (vet402 confirmed the USDC transfer on-chain) · HTTP 200 · tx 0x5674a24f…21edIn export.csv?days=2: the row with attempted_at 2026-09-29T00:02:10Z and resource_key api.losbeto.xyz/fetch.
After a fixNext purchase by vet402: Not before 2026-10-05 00:02 UTC (a listing is bought at most once every 6 days). After that it depends on the daily budget and the order of demand, so this is the earliest date, not a booking.Email me when this result changes Dispute this purchase
api.losbeto.xyz/swarm-voteGET
Latest attempt
2026-09-28 21:32 UTC
Result
delivered
Whose side
no failure (delivered)
Decision API now: · the full answer
Latest L0 check (the 402 to an unpaid request): pass at 2026-09-29 13:40 UTC. Probes run oldest first, so there is no booked time; the next one usually comes by 2026-10-04 13:40 UTC (within 120 hours of the last).
What we saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.The 402 terms vet402 paid: exact · 0.025 USDC · payTo 0xd5ba…fe7d. Input sent: body none, query declared. The listing's maxTimeoutSeconds is 300; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.025 USDC · payTo 0xd5ba…fe7d · nonce 0x1c36…60f7 · validBefore not recorded.Answer to the paid request: HTTP 200 · Content-Type application/json · PAYMENT-RESPONSE: success true, names a transaction.Recorded (L1 paid purchase): settled (vet402 confirmed the USDC transfer on-chain) · HTTP 200 · tx 0x404fc3d9…53b9In export.csv?days=2: the row with attempted_at 2026-09-28T21:32:15Z and resource_key api.losbeto.xyz/swarm-vote.
After a fixNext purchase by vet402: Not before 2026-10-04 21:32 UTC (a listing is bought at most once every 6 days). After that it depends on the daily budget and the order of demand, so this is the earliest date, not a booking.Email me when this result changes Dispute this purchase
api.losbeto.xyz/commodity-priceGET
Latest attempt
2026-09-28 21:32 UTC
Result
delivered
Whose side
no failure (delivered)
Decision API now: · the full answer
Latest L0 check (the 402 to an unpaid request): pass at 2026-09-29 13:40 UTC. Probes run oldest first, so there is no booked time; the next one usually comes by 2026-10-04 13:40 UTC (within 120 hours of the last).
What we saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.The 402 terms vet402 paid: exact · 0.012 USDC · payTo 0xd5ba…fe7d. Input sent: body none, query declared. The listing's maxTimeoutSeconds is 300; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.012 USDC · payTo 0xd5ba…fe7d · nonce 0x0411…ed69 · validBefore not recorded.Answer to the paid request: HTTP 200 · Content-Type application/json · PAYMENT-RESPONSE: success true, names a transaction.Recorded (L1 paid purchase): settled (vet402 confirmed the USDC transfer on-chain) · HTTP 200 · tx 0x3e7b1417…e1a9In export.csv?days=2: the row with attempted_at 2026-09-28T21:32:12Z and resource_key api.losbeto.xyz/commodity-price.
After a fixNext purchase by vet402: Not before 2026-10-04 21:32 UTC (a listing is bought at most once every 6 days). After that it depends on the daily budget and the order of demand, so this is the earliest date, not a booking.Email me when this result changes Dispute this purchase
api.losbeto.xyz/win-rate-verifiedGET
Latest attempt
2026-09-28 21:32 UTC
Result
delivered
Whose side
no failure (delivered)
Decision API now: · the full answer
Latest L0 check (the 402 to an unpaid request): pass at 2026-09-29 13:40 UTC. Probes run oldest first, so there is no booked time; the next one usually comes by 2026-10-04 13:40 UTC (within 120 hours of the last).
What we saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.The 402 terms vet402 paid: exact · 0.04 USDC · payTo 0xd5ba…fe7d. Input sent: body none, query declared. The listing's maxTimeoutSeconds is 300; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.04 USDC · payTo 0xd5ba…fe7d · nonce 0x0672…a0d4 · validBefore not recorded.Answer to the paid request: HTTP 200 · Content-Type application/json · PAYMENT-RESPONSE: success true, names a transaction.Recorded (L1 paid purchase): settled (vet402 confirmed the USDC transfer on-chain) · HTTP 200 · tx 0x4144b18a…1e85In export.csv?days=2: the row with attempted_at 2026-09-28T21:32:10Z and resource_key api.losbeto.xyz/win-rate-verified.
After a fixNext purchase by vet402: Not before 2026-10-04 21:32 UTC (a listing is bought at most once every 6 days). After that it depends on the daily budget and the order of demand, so this is the earliest date, not a booking.Email me when this result changes Dispute this purchase
api.losbeto.xyz/stock-quoteGET
Latest attempt
2026-09-28 21:32 UTC
Result
delivered
Whose side
no failure (delivered)
Decision API now: · the full answer
Latest L0 check (the 402 to an unpaid request): pass at 2026-09-29 13:40 UTC. Probes run oldest first, so there is no booked time; the next one usually comes by 2026-10-04 13:40 UTC (within 120 hours of the last).
What we saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.The 402 terms vet402 paid: exact · 0.015 USDC · payTo 0xd5ba…fe7d. Input sent: body none, query declared. The listing's maxTimeoutSeconds is 300; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.015 USDC · payTo 0xd5ba…fe7d · nonce 0x6518…5a5f · validBefore not recorded.Answer to the paid request: HTTP 200 · Content-Type application/json · PAYMENT-RESPONSE: success true, names a transaction.Recorded (L1 paid purchase): settled (vet402 confirmed the USDC transfer on-chain) · HTTP 200 · tx 0xc72978d1…f953In export.csv?days=2: the row with attempted_at 2026-09-28T21:32:08Z and resource_key api.losbeto.xyz/stock-quote.
After a fixNext purchase by vet402: Not before 2026-10-04 21:32 UTC (a listing is bought at most once every 6 days). After that it depends on the daily budget and the order of demand, so this is the earliest date, not a booking.Email me when this result changes Dispute this purchase
api.losbeto.xyz/multi-chain-arbitrageGET
Latest attempt
2026-09-28 18:36 UTC
Result
delivered
Whose side
no failure (delivered)
Decision API now: · the full answer
Latest L0 check (the 402 to an unpaid request): pass at 2026-09-29 13:40 UTC. Probes run oldest first, so there is no booked time; the next one usually comes by 2026-10-04 13:40 UTC (within 120 hours of the last).
What we saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.The 402 terms vet402 paid: exact · 0.06 USDC · payTo 0xd5ba…fe7d. Input sent: body none, query declared. The listing's maxTimeoutSeconds is 300; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.06 USDC · payTo 0xd5ba…fe7d · nonce 0xa7f1…e70c · validBefore not recorded.Answer to the paid request: HTTP 200 · Content-Type application/json · PAYMENT-RESPONSE: success true, names a transaction.Recorded (L1 paid purchase): settled (vet402 confirmed the USDC transfer on-chain) · HTTP 200 · tx 0x2ffe2643…9917In export.csv?days=2: the row with attempted_at 2026-09-28T18:36:15Z and resource_key api.losbeto.xyz/multi-chain-arbitrage.
After a fixNext purchase by vet402: Not before 2026-10-04 18:36 UTC (a listing is bought at most once every 6 days). After that it depends on the daily budget and the order of demand, so this is the earliest date, not a booking.Email me when this result changes Dispute this purchase
api.losbeto.xyz/macro-calendarGET
Latest attempt
2026-09-28 18:36 UTC
Result
delivered
Whose side
no failure (delivered)
Decision API now: · the full answer
Latest L0 check (the 402 to an unpaid request): pass at 2026-09-29 13:40 UTC. Probes run oldest first, so there is no booked time; the next one usually comes by 2026-10-04 13:40 UTC (within 120 hours of the last).
What we saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.The 402 terms vet402 paid: exact · 0.07 USDC · payTo 0xd5ba…fe7d. Input sent: body none, query declared. The listing's maxTimeoutSeconds is 300; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.07 USDC · payTo 0xd5ba…fe7d · nonce 0x7a1d…0909 · validBefore not recorded.Answer to the paid request: HTTP 200 · Content-Type application/json · PAYMENT-RESPONSE: success true, names a transaction.Recorded (L1 paid purchase): settled (vet402 confirmed the USDC transfer on-chain) · HTTP 200 · tx 0x305d9eaa…b864In export.csv?days=2: the row with attempted_at 2026-09-28T18:36:13Z and resource_key api.losbeto.xyz/macro-calendar.
After a fixNext purchase by vet402: Not before 2026-10-04 18:36 UTC (a listing is bought at most once every 6 days). After that it depends on the daily budget and the order of demand, so this is the earliest date, not a booking.Email me when this result changes Dispute this purchase
api.losbeto.xyz/launch-riskGET
Latest attempt
2026-09-28 18:36 UTC
Result
delivered
Whose side
no failure (delivered)
Decision API now: · the full answer
Latest L0 check (the 402 to an unpaid request): pass at 2026-09-29 13:40 UTC. Probes run oldest first, so there is no booked time; the next one usually comes by 2026-10-04 13:40 UTC (within 120 hours of the last).
What we saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.The 402 terms vet402 paid: exact · 0.1 USDC · payTo 0xd5ba…fe7d. Input sent: body none, query declared. The listing's maxTimeoutSeconds is 300; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.1 USDC · payTo 0xd5ba…fe7d · nonce 0xc195…4906 · validBefore not recorded.Answer to the paid request: HTTP 200 · Content-Type application/json · PAYMENT-RESPONSE: success true, names a transaction.Recorded (L1 paid purchase): settled (vet402 confirmed the USDC transfer on-chain) · HTTP 200 · tx 0xeafaf320…408eIn export.csv?days=2: the row with attempted_at 2026-09-28T18:36:10Z and resource_key api.losbeto.xyz/launch-risk.
After a fixNext purchase by vet402: Not before 2026-10-04 18:36 UTC (a listing is bought at most once every 6 days). After that it depends on the daily budget and the order of demand, so this is the earliest date, not a booking.Email me when this result changes Dispute this purchase
api.losbeto.xyz/br-docGET
Latest attempt
2026-09-28 18:36 UTC
Result
delivered
Whose side
no failure (delivered)
Decision API now: · the full answer
Latest L0 check (the 402 to an unpaid request): pass at 2026-09-29 13:40 UTC. Probes run oldest first, so there is no booked time; the next one usually comes by 2026-10-04 13:40 UTC (within 120 hours of the last).
What we saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.The 402 terms vet402 paid: exact · 0.004 USDC · payTo 0xd5ba…fe7d. Input sent: body none, query declared. The listing's maxTimeoutSeconds is 300; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.004 USDC · payTo 0xd5ba…fe7d · nonce 0x0f6b…d51f · validBefore not recorded.Answer to the paid request: HTTP 200 · Content-Type application/json · PAYMENT-RESPONSE: success true, names a transaction.Recorded (L1 paid purchase): settled (vet402 confirmed the USDC transfer on-chain) · HTTP 200 · tx 0xc0948bce…899cIn export.csv?days=2: the row with attempted_at 2026-09-28T18:36:08Z and resource_key api.losbeto.xyz/br-doc.
After a fixNext purchase by vet402: Not before 2026-10-04 18:36 UTC (a listing is bought at most once every 6 days). After that it depends on the daily budget and the order of demand, so this is the earliest date, not a booking.Email me when this result changes Dispute this purchase
api.losbeto.xyz/agent-marketGET
Latest attempt
2026-09-28 18:36 UTC
Result
delivered
Whose side
no failure (delivered)
Decision API now: · the full answer
Latest L0 check (the 402 to an unpaid request): pass at 2026-09-29 13:40 UTC. Probes run oldest first, so there is no booked time; the next one usually comes by 2026-10-04 13:40 UTC (within 120 hours of the last).
What we saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.The 402 terms vet402 paid: exact · 0.005 USDC · payTo 0xd5ba…fe7d. Input sent: body none, query declared. The listing's maxTimeoutSeconds is 300; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.005 USDC · payTo 0xd5ba…fe7d · nonce 0xb774…8f59 · validBefore not recorded.Answer to the paid request: HTTP 200 · Content-Type application/json · PAYMENT-RESPONSE: success true, names a transaction.Recorded (L1 paid purchase): settled (vet402 confirmed the USDC transfer on-chain) · HTTP 200 · tx 0x187e2f66…1575In export.csv?days=2: the row with attempted_at 2026-09-28T18:36:05Z and resource_key api.losbeto.xyz/agent-market.
After a fixNext purchase by vet402: Not before 2026-10-04 18:36 UTC (a listing is bought at most once every 6 days). After that it depends on the daily budget and the order of demand, so this is the earliest date, not a booking.Email me when this result changes Dispute this purchase
api.losbeto.xyz/trust-hashGET
Latest attempt
2026-09-28 06:02 UTC
Result
delivered
Whose side
no failure (delivered)
Decision API now: · the full answer
Latest L0 check (the 402 to an unpaid request): pass at 2026-09-29 13:40 UTC. Probes run oldest first, so there is no booked time; the next one usually comes by 2026-10-04 13:40 UTC (within 120 hours of the last).
What we saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.The 402 terms vet402 paid: exact · 0.003 USDC · payTo 0xd5ba…fe7d. Input sent: body none, query declared. The listing's maxTimeoutSeconds is 300; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.003 USDC · payTo 0xd5ba…fe7d · nonce 0xb3c8…9592 · validBefore not recorded.Answer to the paid request: HTTP 200 · Content-Type application/json · PAYMENT-RESPONSE: success true, names a transaction.Recorded (L1 paid purchase): settled (vet402 confirmed the USDC transfer on-chain) · HTTP 200 · tx 0x77df3edf…0c2bIn export.csv?days=3: the row with attempted_at 2026-09-28T06:02:35Z and resource_key api.losbeto.xyz/trust-hash.
After a fixNext purchase by vet402: Not before 2026-10-04 06:02 UTC (a listing is bought at most once every 6 days). After that it depends on the daily budget and the order of demand, so this is the earliest date, not a booking.Email me when this result changes Dispute this purchase
api.losbeto.xyz/ai-newsGET
Latest attempt
2026-09-28 06:01 UTC
Result
delivered
Whose side
no failure (delivered)
Decision API now: · the full answer
Latest L0 check (the 402 to an unpaid request): pass at 2026-09-29 13:40 UTC. Probes run oldest first, so there is no booked time; the next one usually comes by 2026-10-04 13:40 UTC (within 120 hours of the last).
What we saw: Paid; vet402 confirmed the transfer on-chain and the paid request answered HTTP 200.The 402 terms vet402 paid: exact · 0.008 USDC · payTo 0xd5ba…fe7d. Input sent: body none, query declared. The listing's maxTimeoutSeconds is 300; vet402 waits 20 seconds for the paid answer.Signed payment: scheme exact · 0.008 USDC · payTo 0xd5ba…fe7d · nonce 0x292a…add1 · validBefore not recorded.Answer to the paid request: HTTP 200 · Content-Type application/json · PAYMENT-RESPONSE: success true, names a transaction.Recorded (L1 paid purchase): settled (vet402 confirmed the USDC transfer on-chain) · HTTP 200 · tx 0x54749b09…31ccIn export.csv?days=3: the row with attempted_at 2026-09-28T06:01:58Z and resource_key api.losbeto.xyz/ai-news.
After a fixNext purchase by vet402: Not before 2026-10-04 06:01 UTC (a listing is bought at most once every 6 days). After that it depends on the daily budget and the order of demand, so this is the earliest date, not a booking.Email me when this result changes Dispute this purchase
api.losbeto.xyz/agent-callGET
Latest attempt
not tried yet
Result
—
Whose side
—
Decision API now: · the full answer
Latest L0 check (the 402 to an unpaid request): pass at 2026-09-28 10:30 UTC. Probes run oldest first, so there is no booked time; the next one usually comes by 2026-10-03 10:30 UTC (within 120 hours of the last).
vet402 has not tried to buy this listing yet.
After a fixEmail me when this result changes Dispute this record
api.losbeto.xyz/agent-composableGET
Latest attempt
not tried yet
Result
—
Whose side
—
Decision API now: · the full answer
Latest L0 check (the 402 to an unpaid request): pass at 2026-09-28 10:30 UTC. Probes run oldest first, so there is no booked time; the next one usually comes by 2026-10-03 10:30 UTC (within 120 hours of the last).
vet402 has not tried to buy this listing yet.
After a fixEmail me when this result changes Dispute this record
api.losbeto.xyz/alpha-signalGET
Latest attempt
not tried yet
Result
—
Whose side
—
Decision API now: · the full answer
Latest L0 check (the 402 to an unpaid request): pass at 2026-09-28 10:30 UTC. Probes run oldest first, so there is no booked time; the next one usually comes by 2026-10-03 10:30 UTC (within 120 hours of the last).
vet402 has not tried to buy this listing yet.
After a fixEmail me when this result changes Dispute this record
api.losbeto.xyz/analiseGET
Latest attempt
not tried yet
Result
—
Whose side
—
Decision API now: · the full answer
Latest L0 check (the 402 to an unpaid request): pass at 2026-09-28 10:30 UTC. Probes run oldest first, so there is no booked time; the next one usually comes by 2026-10-03 10:30 UTC (within 120 hours of the last).
vet402 has not tried to buy this listing yet.
After a fixEmail me when this result changes Dispute this record
api.losbeto.xyz/anomaliasGET
Latest attempt
not tried yet
Result
—
Whose side
—
Decision API now: · the full answer
Latest L0 check (the 402 to an unpaid request): pass at 2026-09-28 10:30 UTC. Probes run oldest first, so there is no booked time; the next one usually comes by 2026-10-03 10:30 UTC (within 120 hours of the last).
vet402 has not tried to buy this listing yet.
After a fixEmail me when this result changes Dispute this record
api.losbeto.xyz/arbitrageGET
Latest attempt
not tried yet
Result
—
Whose side
—
Decision API now: · the full answer
Latest L0 check (the 402 to an unpaid request): pass at 2026-09-28 10:30 UTC. Probes run oldest first, so there is no booked time; the next one usually comes by 2026-10-03 10:30 UTC (within 120 hours of the last).
vet402 has not tried to buy this listing yet.
After a fixEmail me when this result changes Dispute this record
api.losbeto.xyz/backtestGET
Latest attempt
not tried yet
Result
—
Whose side
—
Decision API now: · the full answer
Latest L0 check (the 402 to an unpaid request): pass at 2026-09-28 10:30 UTC. Probes run oldest first, so there is no booked time; the next one usually comes by 2026-10-03 10:30 UTC (within 120 hours of the last).
vet402 has not tried to buy this listing yet.
After a fixEmail me when this result changes Dispute this record
api.losbeto.xyz/br-agroGET
Latest attempt
not tried yet
Result
—
Whose side
—
Decision API now: · the full answer
Latest L0 check (the 402 to an unpaid request): pass at 2026-09-29 04:40 UTC. Probes run oldest first, so there is no booked time; the next one usually comes by 2026-10-04 04:40 UTC (within 120 hours of the last).
vet402 has not tried to buy this listing yet.
After a fixEmail me when this result changes Dispute this record
api.losbeto.xyz/br-archiveGET
Latest attempt
not tried yet
Result
—
Whose side
—
Decision API now: · the full answer
Latest L0 check (the 402 to an unpaid request): pass at 2026-09-29 13:40 UTC. Probes run oldest first, so there is no booked time; the next one usually comes by 2026-10-04 13:40 UTC (within 120 hours of the last).
vet402 has not tried to buy this listing yet.
After a fixEmail me when this result changes Dispute this record
api.losbeto.xyz/br-asofGET
Latest attempt
not tried yet
Result
—
Whose side
—
Decision API now: · the full answer
Latest L0 check (the 402 to an unpaid request): pass at 2026-09-29 13:40 UTC. Probes run oldest first, so there is no booked time; the next one usually comes by 2026-10-04 13:40 UTC (within 120 hours of the last).
vet402 has not tried to buy this listing yet.
After a fixEmail me when this result changes Dispute this record
api.losbeto.xyz/br-briefGET
Latest attempt
not tried yet
Result
—
Whose side
—
Decision API now: · the full answer
Latest L0 check (the 402 to an unpaid request): pass at 2026-09-29 13:40 UTC. Probes run oldest first, so there is no booked time; the next one usually comes by 2026-10-04 13:40 UTC (within 120 hours of the last).
vet402 has not tried to buy this listing yet.
After a fixEmail me when this result changes Dispute this record
api.losbeto.xyz/br-curveGET
Latest attempt
not tried yet
Result
—
Whose side
—
Decision API now: · the full answer
Latest L0 check (the 402 to an unpaid request): pass at 2026-09-29 04:40 UTC. Probes run oldest first, so there is no booked time; the next one usually comes by 2026-10-04 04:40 UTC (within 120 hours of the last).
vet402 has not tried to buy this listing yet.
After a fixEmail me when this result changes Dispute this record
api.losbeto.xyz/br-equityGET
Latest attempt
not tried yet
Result
—
Whose side
—
Decision API now: · the full answer
Latest L0 check (the 402 to an unpaid request): pass at 2026-09-29 13:40 UTC. Probes run oldest first, so there is no booked time; the next one usually comes by 2026-10-04 13:40 UTC (within 120 hours of the last).
vet402 has not tried to buy this listing yet.
After a fixEmail me when this result changes Dispute this record
api.losbeto.xyz/br-macroGET
Latest attempt
not tried yet
Result
—
Whose side
—
Decision API now: · the full answer
Latest L0 check (the 402 to an unpaid request): pass at 2026-09-28 10:30 UTC. Probes run oldest first, so there is no booked time; the next one usually comes by 2026-10-03 10:30 UTC (within 120 hours of the last).
vet402 has not tried to buy this listing yet.
After a fixEmail me when this result changes Dispute this record
api.losbeto.xyz/br-macro-snapshotGET
Latest attempt
not tried yet
Result
—
Whose side
—
Decision API now: · the full answer
Latest L0 check (the 402 to an unpaid request): pass at 2026-09-28 10:30 UTC. Probes run oldest first, so there is no booked time; the next one usually comes by 2026-10-03 10:30 UTC (within 120 hours of the last).
vet402 has not tried to buy this listing yet.
After a fixEmail me when this result changes Dispute this record
api.losbeto.xyz/br-pix-codeGET
Latest attempt
not tried yet
Result
—
Whose side
—
Decision API now: · the full answer
Latest L0 check (the 402 to an unpaid request): pass at 2026-09-28 10:30 UTC. Probes run oldest first, so there is no booked time; the next one usually comes by 2026-10-03 10:30 UTC (within 120 hours of the last).
vet402 has not tried to buy this listing yet.
After a fixEmail me when this result changes Dispute this record
api.losbeto.xyz/br-pix-parseGET
Latest attempt
not tried yet
Result
—
Whose side
—
Decision API now: · the full answer
Latest L0 check (the 402 to an unpaid request): pass at 2026-09-28 10:30 UTC. Probes run oldest first, so there is no booked time; the next one usually comes by 2026-10-03 10:30 UTC (within 120 hours of the last).
vet402 has not tried to buy this listing yet.
After a fixEmail me when this result changes Dispute this record
api.losbeto.xyz/br-revisionsGET
Latest attempt
not tried yet
Result
—
Whose side
—
Decision API now: · the full answer
Latest L0 check (the 402 to an unpaid request): pass at 2026-09-29 13:40 UTC. Probes run oldest first, so there is no booked time; the next one usually comes by 2026-10-04 13:40 UTC (within 120 hours of the last).
vet402 has not tried to buy this listing yet.
After a fixEmail me when this result changes Dispute this record
api.losbeto.xyz/buy-credits-microGET
Latest attempt
not tried yet
Result
—
Whose side
—
Decision API now: · the full answer
Latest L0 check (the 402 to an unpaid request): pass at 2026-09-28 10:30 UTC. Probes run oldest first, so there is no booked time; the next one usually comes by 2026-10-03 10:30 UTC (within 120 hours of the last).
vet402 has not tried to buy this listing yet.
After a fixEmail me when this result changes Dispute this record
api.losbeto.xyz/copytradeGET
Latest attempt
not tried yet
Result
—
Whose side
—
Decision API now: · the full answer
Latest L0 check (the 402 to an unpaid request): pass at 2026-09-29 04:40 UTC. Probes run oldest first, so there is no booked time; the next one usually comes by 2026-10-04 04:40 UTC (within 120 hours of the last).
vet402 has not tried to buy this listing yet.
After a fixEmail me when this result changes Dispute this record
api.losbeto.xyz/correlation-matrixGET
Latest attempt
not tried yet
Result
—
Whose side
—
Decision API now: · the full answer
Latest L0 check (the 402 to an unpaid request): pass at 2026-09-29 13:40 UTC. Probes run oldest first, so there is no booked time; the next one usually comes by 2026-10-04 13:40 UTC (within 120 hours of the last).
vet402 has not tried to buy this listing yet.
After a fixEmail me when this result changes Dispute this record
api.losbeto.xyz/councilGET
Latest attempt
not tried yet
Result
—
Whose side
—
Decision API now: · the full answer
Latest L0 check (the 402 to an unpaid request): pass at 2026-09-28 10:30 UTC. Probes run oldest first, so there is no booked time; the next one usually comes by 2026-10-03 10:30 UTC (within 120 hours of the last).
vet402 has not tried to buy this listing yet.
After a fixEmail me when this result changes Dispute this record
api.losbeto.xyz/council-deepGET
Latest attempt
not tried yet
Result
—
Whose side
—
Decision API now: · the full answer
Latest L0 check (the 402 to an unpaid request): pass at 2026-09-29 13:40 UTC. Probes run oldest first, so there is no booked time; the next one usually comes by 2026-10-04 13:40 UTC (within 120 hours of the last).
vet402 has not tried to buy this listing yet.
After a fixEmail me when this result changes Dispute this record
api.losbeto.xyz/cross-chainGET
Latest attempt
not tried yet
Result
—
Whose side
—
Decision API now: · the full answer
Latest L0 check (the 402 to an unpaid request): pass at 2026-09-28 10:30 UTC. Probes run oldest first, so there is no booked time; the next one usually comes by 2026-10-03 10:30 UTC (within 120 hours of the last).
vet402 has not tried to buy this listing yet.
After a fixEmail me when this result changes Dispute this record
api.losbeto.xyz/deep-thinkGET
Latest attempt
not tried yet
Result
—
Whose side
—
Decision API now: · the full answer
Latest L0 check (the 402 to an unpaid request): pass at 2026-09-28 10:30 UTC. Probes run oldest first, so there is no booked time; the next one usually comes by 2026-10-03 10:30 UTC (within 120 hours of the last).
vet402 has not tried to buy this listing yet.
After a fixEmail me when this result changes Dispute this record
api.losbeto.xyz/defi-yieldGET
Latest attempt
not tried yet
Result
—
Whose side
—
Decision API now: · the full answer
Latest L0 check (the 402 to an unpaid request): pass at 2026-09-28 10:30 UTC. Probes run oldest first, so there is no booked time; the next one usually comes by 2026-10-03 10:30 UTC (within 120 hours of the last).
vet402 has not tried to buy this listing yet.
After a fixEmail me when this result changes Dispute this record
api.losbeto.xyz/dex-screenGET
Latest attempt
not tried yet
Result
—
Whose side
—
Decision API now: · the full answer
Latest L0 check (the 402 to an unpaid request): pass at 2026-09-28 10:30 UTC. Probes run oldest first, so there is no booked time; the next one usually comes by 2026-10-03 10:30 UTC (within 120 hours of the last).
vet402 has not tried to buy this listing yet.
After a fixEmail me when this result changes Dispute this record
api.losbeto.xyz/earnings-whisperGET
Latest attempt
not tried yet
Result
—
Whose side
—
Decision API now: · the full answer
Latest L0 check (the 402 to an unpaid request): pass at 2026-09-28 10:30 UTC. Probes run oldest first, so there is no booked time; the next one usually comes by 2026-10-03 10:30 UTC (within 120 hours of the last).
vet402 has not tried to buy this listing yet.
After a fixEmail me when this result changes Dispute this record
api.losbeto.xyz/equity-dossierGET
Latest attempt
not tried yet
Result
—
Whose side
—
Decision API now: · the full answer
Latest L0 check (the 402 to an unpaid request): pass at 2026-09-28 10:30 UTC. Probes run oldest first, so there is no booked time; the next one usually comes by 2026-10-03 10:30 UTC (within 120 hours of the last).
vet402 has not tried to buy this listing yet.
After a fixEmail me when this result changes Dispute this record
api.losbeto.xyz/event-playbookGET
Latest attempt
not tried yet
Result
—
Whose side
—
Decision API now: · the full answer
Latest L0 check (the 402 to an unpaid request): pass at 2026-09-29 13:40 UTC. Probes run oldest first, so there is no booked time; the next one usually comes by 2026-10-04 13:40 UTC (within 120 hours of the last).
vet402 has not tried to buy this listing yet.
After a fixEmail me when this result changes Dispute this record
api.losbeto.xyz/extractPOST
Latest attempt
not tried yet
Result
—
Whose side
—
Decision API now: · the full answer
Latest L0 check (the 402 to an unpaid request): pass at 2026-09-29 10:30 UTC. Probes run oldest first, so there is no booked time; the next one usually comes by 2026-10-04 10:30 UTC (within 120 hours of the last).
vet402 has not tried to buy this listing yet.
After a fixEmail me when this result changes Dispute this record
api.losbeto.xyz/fear-greedGET
Latest attempt
not tried yet
Result
—
Whose side
—
Decision API now: · the full answer
Latest L0 check (the 402 to an unpaid request): pass at 2026-09-28 10:30 UTC. Probes run oldest first, so there is no booked time; the next one usually comes by 2026-10-03 10:30 UTC (within 120 hours of the last).
vet402 has not tried to buy this listing yet.
After a fixEmail me when this result changes Dispute this record
api.losbeto.xyz/forex-arbitrageGET
Latest attempt
not tried yet
Result
—
Whose side
—
Decision API now: · the full answer
Latest L0 check (the 402 to an unpaid request): pass at 2026-09-29 13:40 UTC. Probes run oldest first, so there is no booked time; the next one usually comes by 2026-10-04 13:40 UTC (within 120 hours of the last).
vet402 has not tried to buy this listing yet.
After a fixEmail me when this result changes Dispute this record
api.losbeto.xyz/forex-rateGET
Latest attempt
not tried yet
Result
—
Whose side
—
Decision API now: · the full answer
Latest L0 check (the 402 to an unpaid request): pass at 2026-09-28 10:30 UTC. Probes run oldest first, so there is no booked time; the next one usually comes by 2026-10-03 10:30 UTC (within 120 hours of the last).
vet402 has not tried to buy this listing yet.
After a fixEmail me when this result changes Dispute this record
api.losbeto.xyz/geo-alphaGET
Latest attempt
not tried yet
Result
—
Whose side
—
Decision API now: · the full answer
Latest L0 check (the 402 to an unpaid request): pass at 2026-09-28 10:30 UTC. Probes run oldest first, so there is no booked time; the next one usually comes by 2026-10-03 10:30 UTC (within 120 hours of the last).
vet402 has not tried to buy this listing yet.
After a fixEmail me when this result changes Dispute this record
api.losbeto.xyz/global-morning-briefGET
Latest attempt
not tried yet
Result
—
Whose side
—
Decision API now: · the full answer
Latest L0 check (the 402 to an unpaid request): pass at 2026-09-29 04:40 UTC. Probes run oldest first, so there is no booked time; the next one usually comes by 2026-10-04 04:40 UTC (within 120 hours of the last).
vet402 has not tried to buy this listing yet.
After a fixEmail me when this result changes Dispute this record
api.losbeto.xyz/holder-concentrationGET
Latest attempt
not tried yet
Result
—
Whose side
—
Decision API now: · the full answer
Latest L0 check (the 402 to an unpaid request): pass at 2026-09-28 10:30 UTC. Probes run oldest first, so there is no booked time; the next one usually comes by 2026-10-03 10:30 UTC (within 120 hours of the last).
vet402 has not tried to buy this listing yet.
After a fixEmail me when this result changes Dispute this record

2.How to read this

Each listing shows its latest attempt on Base and up to four earlier ones. A row where vet402 signed a payment and sent the paid request is an L1 result: “Recorded (L1 paid purchase)” when the payment settled on-chain, and “signed, not settled on-chain” when it did not. A row where vet402 did not sign is marked “not bought” and is not an L1 result. The listing's record page also shows the L0 state (“Published state”), which checks that an unpaid request gets a valid 402, so a listing can pass L0 and still fail here. Whose side puts a failure on the seller's side when the row shows vet402 was not at fault: it signed on the listing's terms, its wallet held the price, it sent the declared input, and the seller answered explicitly or had its declared time. Even then, one such failure is “not sorted: one failure so far”: a failure goes on the seller's side only when the same listing has one on two different days (UTC), and those rows are marked “under re-check” while we re-check them. A row that cannot show all of that is “not sorted”, and so is a held row (held_reason in the export), a failure where no payment was taken (“no charge”), and a payment that settled before the seller refused an input vet402 had not sent. “Signed payment” and “Answer to the paid request” show what the row recorded, and nothing else: the answer's body and header values are not published. The maxTimeoutSeconds on a row is the listing's value today; a declared price or address on a not-bought row is the value recorded at the time of the attempt. The transaction link opens the settlement on Basescan. “Decision API now” is what the decision API (GET /api/v1/resources/{id}/decision?role=payer, no key) answers for the listing when you open this page; your browser asks it for the first 2 listings, and for the others when you ask. It reads the same sorting as this page: a failure counts against the seller only when this page puts it on the seller's side. A paid attempt that took payment and did not deliver is a WARN, and two or more of them on the seller's side since the last delivery are the only way a failed purchase makes it a BLOCK; a listing whose failures this page leaves not sorted gets at most a WARN from them. An L0 check that is unverified (not probed yet, or not measurable) is a WARN, not a BLOCK. The codes that decided the answer come first, each with the meaning from the reason-code table (reason codes). “After a fix” gives the earliest date vet402's regular sweep can buy the listing again, where the rules let it be worked out, and the links to be told of a change or to dispute a row. Listings removed from the Bazaar, and listings whose catalog network is not Base, are not on this page. The fix-first page groups the same results across sellers (methodology).

3.Think a row is wrong?

Use “Dispute this purchase” on the row: it opens Dispute this record on the listing's record page with the purchase time filled in. Say what you saw instead. The row is not deleted on dispute; a correction is published with the same weight.