Endpoint

B

api.agentstools.dev/crypto/hash

crypto-hash · score 77/100 · recomputed 21m ago

Compute keccak256/sha256, a 4-byte function selector, an event topic0, or an ENS namehash/labelhash from a string or hex input.

NEW_UNKNOWN
First seen
5d ago
Probes stored
3

Score

B
77 of 100
recomputed 21m 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
7h ago 402 40 ms exact
eip155:8453
0xF22e…f493 0.001000 clean
4d ago 402 264 ms exact
eip155:8453
0xF22e…f493 0.001000 clean
4d ago 402 260 ms exact
eip155:8453
0xF22e…f493 0.001000 clean

Reference

URLhttps://api.agentstools.dev/crypto/hash
Sourcesbazaar well-known
Recipient per catalogue0xF22e558a00D91Ee12A1F50C52186FecB8dDFf493
Price per catalogue0.001000
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.