Endpoint

?

api.402rates.com/v1/tests/run

· not enough data yet · recomputed 13d ago
NOT_RESPONDING
First seen
50d ago
Probes stored
8
No score yet: there are not enough observations. We do not assign a low grade for missing data — a new endpoint would otherwise look dead. The prepay verdict in that case is warn: unknown is a risk, not a clean bill of health.

Recent probes

WhenCodeLatencyScheme and network RecipientPriceFindings
20d ago 405 9 ms — — — E_NO_402:405
44d ago 405 15 ms — — — E_NO_402:405
45d ago 405 56 ms — — — E_NO_402:405
45d ago 405 12 ms — — — E_NO_402:405
49d ago 405 837 ms — — — E_NO_402:405
50d ago 405 236 ms — — — E_NO_402:405
50d ago 405 240 ms — — — E_NO_402:405
50d ago 405 238 ms — — — E_NO_402:405

Reference

URLhttps://api.402rates.com/v1/tests/run
Sourcesbazaar
Machine access/v1/endpoint · /full · badge

Is this your endpoint?

The score is built only from public observations. If something we recorded is wrong — say our prober hit you during maintenance — write to us. We will recheck and publish your reply next to the score.

We do not delete accurate observations. The prober makes at most one request per second per host and only asks for the payment challenge — it never pays and never takes content.

Next

Market overview →

Payments, median ticket, who pays whom, who settles.

Wallets →

Payers, recipients and facilitators, listed separately.

Facilitators →

Who actually settles — including those in no public registry.

API →

Verdict before payment, seller and wallet scores, market aggregates.