Endpoint

B

vibesprings.net/api/infra/health-check

Vibe Springs · score 77/100 · recomputed 44m ago

API endpoint health checker and x402 compatibility scanner. Provide target url to fetch and check if it correctly implements the HTTP 402 payment flow, and extract its pricing requirements.

NEW_UNKNOWN
First seen
5d ago
Probes stored
3

Score

B
77 of 100
recomputed 44m ago

The score is built from observations we collect ourselves: how the endpoint responds, what the envelope contains, how stable the price and the recipient are, who pays and how often. It is deterministic — the same input always produces the same result.

We do not publish the exact methodology yet. If you own this endpoint, write to us and we will show you, item by item, what drags the score down.

Recent probes

WhenCodeLatencyScheme and network RecipientPriceFindings
6h ago 402 101 ms exact
eip155:8453
0x38C0…44C8 0.003000 clean
4d ago 402 127 ms exact
eip155:8453
0x38C0…44C8 0.003000 clean
4d ago 402 132 ms exact
eip155:8453
0x38C0…44C8 0.003000 clean

Reference

URLhttps://vibesprings.net/api/infra/health-check
Sourcesbazaar
Recipient per catalogue0x38C063312719220c676E988f0DEE14B4ec0e44C8
Price per catalogue0.003000
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.