Discover / chainkit.leeworks.dev

chainkit

□ No challenge detected

17 on-chain compute primitives in one x402 API: keccak256, ABI encode/decode, function selectors, EIP-712 hashing + signature recovery/verification, merkle root/proof/verify, CREATE/CREATE2 address derivation, ENS namehash, checksum, unit conversion, RLP encode/decode. Pure computation, no data dependencies. 0.02 USDC per call on Base.

Challenge detected
0 of the last 3 checks
Last checked
16 Oct, 21:19 UTC
In our index since
14 Oct 2026

Endpoint

curl -i https://chainkit.leeworks.dev
# 402 Payment Required: pay with an x402 client (USDC on Base),
# then send the same request again with the payment attached.

Agents can find it through the Superstables MCP server and JSON API: GET /api/v1/services/chainkit.leeworks.dev

Recent checks

14 Oct 2026One bar per check, showing up to 20 recent checks. Coloured bars show relative response time, with a minimum visible height; full-height grey bars mean no challenge was detected. “Challenge detected” means HTTP 402 or another detected payment-challenge signal.16 Oct 2026
All 3 checks
When (UTC)ResultHTTPResponse
16 Oct, 21:19 UTCNo challenge detected404100ms
15 Oct, 14:11 UTCNo challenge detected404681ms
14 Oct, 05:00 UTCNo challenge detected40483ms

Questions

Did our last probe detect a payment challenge?

No. At our last probe on 16 Oct, 21:19 UTC, we detected no payment challenge.

What payment terms does chainkit advertise?

The listing advertises x402, Base and USDC. Check the seller's current payment challenge and authentication requirements before paying.

Where is chainkit listed?

In x402-list.com. Superstables first indexed it on 14 Oct 2026.

Something wrong on this page? Tell us.