api.apex-db.org

Solana, Tempo and Base

Graded from Solana, Tempo and Base purchases only. Listed on the Sellers page.

vet402 paid this seller 10 times with its own money (Tempo 10), most recently on 2026-10-07 (UTC). 10 settled on chain; 10 came back with an answer.

vet402 bought this seller again on 9 UTC days since 2026-09-29 (Tempo 9), to the same payTo and at no more than the earlier price. It costs the seller nothing, and there is nothing to sign up for.

C grade C: comes back with an answer 50%+ of the time · Rank 79 of 101 on this page.

Came back, of counted, per chain: Tempo 10/10. Came back with an answer = vet402's payment settled, then the seller answered 2xx with a non-empty body. vet402 did not check that the answer is what the listing promised; whether its keys matched what the seller declared is a separate column.

Separate column, not in the grade. Answer matched what the seller declared: not checked.

Not counted

Counted against this seller

None.

How each failure is assigned

Recent purchases

Each tx links to a public explorer.

1. 2026-10-07 02:40 UTC · Tempo · came back with an answer 0x8cfdca…033695
   https://api.apex-db.org/v1/apex
2. 2026-10-06 01:23 UTC · Tempo · came back with an answer 0xe54046…15e6da
   https://api.apex-db.org/v1/apex
3. 2026-10-05 05:58 UTC · Tempo · came back with an answer 0x01248b…524db3
   https://api.apex-db.org/v1/apex
4. 2026-10-04 01:34 UTC · Tempo · came back with an answer 0x0d6025…c90d9c
   https://api.apex-db.org/v1/apex
5. 2026-10-03 01:35 UTC · Tempo · came back with an answer 0xdcb843…73e939
   https://api.apex-db.org/v1/apex
6. 2026-10-02 01:33 UTC · Tempo · came back with an answer 0x432ec0…949c49
   https://api.apex-db.org/v1/apex
7. 2026-10-01 01:31 UTC · Tempo · came back with an answer 0xcf84ab…3a9d70
   https://api.apex-db.org/v1/apex
8. 2026-09-30 02:27 UTC · Tempo · came back with an answer 0xf0c5b9…d30e1f
   https://api.apex-db.org/v1/apex
9. 2026-09-29 08:25 UTC · Tempo · came back with an answer 0xe5df06…7869c5
   https://api.apex-db.org/v1/apex
10. 2026-09-28 07:55 UTC · Tempo · came back with an answer 0xa9ff5b…d2c9fd
    https://api.apex-db.org/v1/apex

Signed delivery records

One page per purchase that came back with an answer, signed by vet402 and included in a daily Merkle root. Each page shows how to check it without trusting vet402.

1. 2026-09-28 · Tempo · obs_2026-09-28_000061
2. 2026-09-29 · Tempo · obs_2026-09-29_000267
3. 2026-09-30 · Tempo · obs_2026-09-30_000482
4. 2026-10-01 · Tempo · obs_2026-10-01_000697
5. 2026-10-02 · Tempo · obs_2026-10-02_000887
6. 2026-10-03 · Tempo · obs_2026-10-03_001085
7. 2026-10-04 · Tempo · obs_2026-10-04_001285
8. 2026-10-05 · Tempo · obs_2026-10-05_001487
9. 2026-10-06 · Tempo · obs_2026-10-06_001604

Are you the seller?

Is a row wrong? A seller who thinks a row is wrong opens a GitHub issue with the URL or tx. vet402 checks it against the chain and the raw result; a wrong row is fixed and the fix is noted in the change log.

Tell vet402 a row is wrong (GitHub issue, prefilled)

Signed records of failed purchases are published only after the seller is told. More for sellers