api.exa.ai

Solana, Tempo and Base

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

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

vet402 bought this seller again on 10 UTC days since 2026-09-29 (Tempo 10), 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 92 of 111 on this page.

11 / 11
came back, of counted (100%)
0.74 to 1.00
95% interval
2026-10-08
last bought · 11 days counted
00.51

Came back, of counted, per chain: Tempo 11/11. 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

0vet402 or facilitator side not counted
0can't tell not counted

Counted against this seller

0seller side counted in the grade

None.

How each failure is assigned

Recent purchases

Each tx links to a public explorer.

  1. 2026-10-08 02:42 UTC · Tempo · came back with an answer 0xc57847…ec15f4
    https://api.exa.ai/search
  2. 2026-10-07 02:46 UTC · Tempo · came back with an answer 0xbd1d6d…0272b1
    https://api.exa.ai/search
  3. 2026-10-06 01:29 UTC · Tempo · came back with an answer 0xe24539…c9655e
    https://api.exa.ai/search
  4. 2026-10-05 06:02 UTC · Tempo · came back with an answer 0x2b9018…a09db5
    https://api.exa.ai/search
  5. 2026-10-04 01:37 UTC · Tempo · came back with an answer 0xa3b457…b052d3
    https://api.exa.ai/search
  6. 2026-10-03 01:38 UTC · Tempo · came back with an answer 0xc8a7bc…f2c775
    https://api.exa.ai/search
  7. 2026-10-02 01:36 UTC · Tempo · came back with an answer 0x5892f9…06f3a3
    https://api.exa.ai/search
  8. 2026-10-01 01:33 UTC · Tempo · came back with an answer 0x846db8…e534f3
    https://api.exa.ai/search
  9. 2026-09-30 02:29 UTC · Tempo · came back with an answer 0x140176…67e630
    https://api.exa.ai/search
  10. 2026-09-29 08:27 UTC · Tempo · came back with an answer 0xee895e…9833bc
    https://api.exa.ai/search

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_000090
  2. 2026-09-29 · Tempo · obs_2026-09-29_000283
  3. 2026-09-30 · Tempo · obs_2026-09-30_000498
  4. 2026-10-01 · Tempo · obs_2026-10-01_000708
  5. 2026-10-02 · Tempo · obs_2026-10-02_000898
  6. 2026-10-03 · Tempo · obs_2026-10-03_001096
  7. 2026-10-04 · Tempo · obs_2026-10-04_001296
  8. 2026-10-05 · Tempo · obs_2026-10-05_001498
  9. 2026-10-06 · Tempo · obs_2026-10-06_001615

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