x402 List Submit a serviceSubmit
Menu

chainkit

offline

payment-ready 2026-10-08, probe currently failing

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.

Part of the Leeworks operator hub

chainkit.leeworks.dev ↗

Call it x402 v1

x402 v1

Base URL
https://chainkit.leeworks.dev
Payment
x402 v1, body (v1 style)
$ curl -i -X POST 'https://chainkit.leeworks.dev/v1/crypto'

An unpaid request returns HTTP 402 with the payment terms. Sign a payment authorization, then retry with the X-PAYMENT header.

Endpoints 1 paid route on chainkit.leeworks.dev

POST/v1/cryptoBase$0.02since 07-25

Prices as captured in the 402 response: $0.02.

Example 402 response

Endpoints and prices

Current paid endpoints; minimum quoted prices in USD where available; first capture dates in UTC
MethodPathDescriptionPriceNetworkAsset402 channelCaptured
POST/v1/cryptoOn-chain compute: keccak256, ABI encode/decode, fn/event selectors, EIP-712 hashing, EIP-191/712 recovery, Merkle proofs, CREATE/CREATE2, ENS namehash, checksum, unit convert, RLP$0.02BaseUSDCbodysince 07-25

Payment evidence

402 payload captured at . Check evidence JSON · Measurement methodology.

1 payload captured by the monitor for POST /v1/crypto.

144 lines, scroll inside

{
  "error": "payment required",
  "accepts": [
    {
      "asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
      "extra": {
        "name": "USD Coin",
        "input": {
          "method": "POST",
          "schema": {
            "type": "object",
            "required": [
              "op"
            ],
            "properties": {
              "op": {
                "enum": [
                  "keccak256",
                  "abi_encode",
                  "abi_decode",
                  "selector",
                  "eip712_hash",
                  "recover",
                  "verify_712",
                  "merkle_root",
                  "merkle_proof",
                  "verify_merkle",
                  "create2",
                  "create_address",
                  "namehash",
                  "checksum",
                  "unit_convert",
                  "rlp_encode",
                  "rlp_decode"
                ],
                "type": "string",
                "description": "Operation to run; remaining fields depend on op"
              },
              "args": {
                "type": "array",
                "description": "abi_encode: arguments for the given signature"
              },
              "data": {
                "type": "string",
                "description": "keccak256: hex(0x…) hashed as bytes else UTF-8. abi_decode: calldata. rlp_*: hex or nested array"
              },
              "from": {
                "type": "string",
                "description": "create_address: deployer address"
              },
              "leaf": {
                "description": "merkle_proof/verify_merkle: target leaf"
              },
              "name": {
                "type": "string",
                "description": "namehash: ENS name e.g. vitalik.eth"
              },
              "salt": {
                "type": "string",
                "description": "create2: 32-byte hex salt"
              },
              "nonce": {
                "type": "integer",
                "description": "create_address: deployer nonce"
              },
              "proof": {
                "type": "array",
                "description": "verify_merkle: hex proof"
              },
              "types": {
                "type": "array",
                "description": "abi_encode/abi_decode: raw ABI type list e.g. [\"address\",\"uint256\"]"
              },
              "value": {
                "type": "object",
                "description": "verify_712/eip712_hash: typed-data value"
              },
              "domain": {
                "type": "object",
                "description": "verify_712/eip712_hash: EIP-712 domain"
              },
              "leaves": {
                "type": "array",
                "description": "merkle_*: leaf values (keccak256, sorted pairs)"
              },
              "values": {
                "type": "array",
                "description": "abi_encode: values matching types"
              },
              "address": {
                "type": "string",
                "description": "checksum: address to checksum/validate"
              },
              "message": {
                "type": "string",
                "description": "recover: the personal_sign message"
              },
              "deployer": {
                "type": "string",
                "description": "create2: deployer address"
              },
              "initCode": {
                "type": "string",
                "description": "create2: init code (hashed) — or pass initCodeHash"
              },
              "signature": {
                "type": "string",
                "description": "recover/verify_712: 0x sig. abi_encode/abi_decode/selector: a fn/event sig e.g. transfer(address,uint256)"
              },
              "value_num": {
                "description": "unit_convert: amount (use field 'value')"
              }
            }
          },
          "example": {
            "op": "selector",
            "signature": "transfer(address,uint256)"
          },
          "contentType": "application/json"
        },
        "output": {
          "example": {
            "ok": true,
            "op": "selector",
            "topic0": "0xa9059cbb2ab09eb219583f4a59a5d0623ade346d962bcd4e46b11da047c9049b",
            "selector": "0xa9059cbb"
          },
          "contentType": "application/json",
          "description": "Always {ok, op}; other fields depend on op (hash | data | values | selector/topic0 | digest | signer | root/proof | address | checksum | wei/result | rlp/decoded)"
        },
        "version": "2"
      },
      "payTo": "0xa8B061d96F69426f11bcC807BfA00f0AF79541a7",
      "scheme": "exact",
      "network": "base",
      "mimeType": "application/json",
      "resource": "https://chainkit.leeworks.dev/v1/crypto",
      "description": "On-chain compute: keccak256, ABI encode/decode, fn/event selectors, EIP-712 hashing, EIP-191/712 recovery, Merkle proofs, CREATE/CREATE2, ENS namehash, checksum, unit convert, RLP",
      "maxAmountRequired": "20000",
      "maxTimeoutSeconds": 120
    }
  ],
  "x402Version": 1
}

Can I trust it score from our own monitoring

score from our own monitoring

71/100 Mixed

#71 of 75 in Blockchain. Bands: strong 93+, solid 75+, mixed 55+, weak below 55.

Reliability
94.6% uptime 30d
Compliance
A 13/14 checks pass, failing: declares the current x402 version (2), stale (probe failing)
Price
$0.02 p75 in Blockchain
Risk
clean no risk flag
Traction
---
13/14 compliance checks
  • 402 payload captured
  • accepts[] array present
  • payTo address recoverable
  • payTo at accepts[0].payTo (conformant shape)
  • payTo is a valid on-chain address
  • atomic price declared
  • atomic price in a sane range
  • asset (token) address declared
  • network resolves to CAIP-2
  • payment scheme declared
  • served over HTTPS
  • declares the current x402 version (2)
  • EIP-712 domain parameters present on every EVM entry
  • x402 v2 envelope delivered in the payment-required header

402 terms unchanged since 2026-07-25. Last up 2026-10-08.

── Site signals

  • homepage reachable
  • openapi doc
  • pricing page
  • llms.txt
  • robots.txt
  • terms page
How the score works

What the score read on this service: status offline, 94.6% uptime 30d, 1997ms response p95, x402 compliance 13 of 14, $0.02 price against the category. Each of those is measured, and each is published in full below.

The score comes from our own monitoring, never from reviews, operator claims, or a language model: reliability, x402 compliance, price against the category, a deterministic risk flag, and a small on-chain traction term, weighted by ranking generation 3. It is not placement anyone can buy: the paid verify tier is reported beside it and is not one of its inputs. Every component below stays published and read-only.

Bands on the 0 to 100 measured score: strong at 93 and above, solid from 75, mixed from 55, weak below 55. Price and speed are scored against the whole category field, every listing in it that carries no danger flag, the scored service included, so the score places a service in its own field.

It is a score inside Blockchain, and only there: price and speed are scored against the whole category field, every listing in it that carries no danger flag, the scored service included, which here means 75 listings, this one among them: the same 75 the position above is counted against. When the two differ, the field is the wider one, because a listing we have measured too little of to rank still sits in the field the price and the speed are normalized over. The same service in a different field would read differently. The same engine answers GET /api/v1/best, and asked for a different pool (the whole directory, or another filter) it returns a different number for this service under this same ranking generation. Neither is more correct: they answer different questions, and the methodology states which is which.

All measured facts

What it does

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.

chainkit is a listed x402 Blockchain API. Captured payment terms name Base. Monitoring and settlement figures below describe the observations available to this directory; an unpaid HTTP 402 check does not prove that a paid call will deliver.

Assessment computed at . Latest service check observed at . Service data JSON · Measurement methodology.

Page rendered at . This response time is separate from the observation and computation times attached to each measurement.

Latest endpoint observation: . Latest price capture: . Prices are recorded quotes, not a promise of availability. Token assets and payment terms are listed separately. Endpoint data JSON · Price history JSON · Measurement methodology.

Assessment computed at . Uptime uses the stated daily-rollup window; response times are in milliseconds, compliance is passed/evaluated checks, and traction is a measured settlement floor. The comparison score is out of 100 within this category. Assessment JSON · Measurement methodology.

Observed daily coverage: 2026-09-25 to 2026-10-24 UTC. Daily monitoring and settlement rollups do not expose their computation time; a bucket date is not an update timestamp. Uptime and response JSON · Volume JSON · Buyers JSON · Measurement methodology.

Ranked from the measured category pool, refreshed at most once a minute. The comparison has no persisted computation timestamp; the assessment time above belongs to this service only. Ranking API documentation · Ranking methodology.

x402 List home · Services · Blockchain

uptime · latest daily rollup
-
uptime 7d
0%
uptime 30d
94.6%
uptime 90d
98.8%
response p95
1997ms
avg response
1203ms
total checks
1,473

Measured on the unpaid 402 handshake, not the paid call. A service can 402 correctly and still fail after payment.

price (min)
$0.02
category percentile (min)
p75 in Blockchain
endpoints / prices
1 / 1
model
flat
stability
100%

No deterministic risk flag. Risk fires only on an exact blocklist match, or a reserved-brand name with a mismatched verified payTo. Never from low uptime, a high price, or a model guess.

domain age
-
registrar
-
hosting
custom
domain created
---

Identity facts, not a risk score.

This service shares a payout address and its probe has been failing, so its on-chain volume is suppressed until it responds again. Settlements on a shared address while a member is down are not attributed to it.

member since
2026-07-25
Recent checks
Latest 18 unpaid HTTP checks, newest first; response times in milliseconds, observation times in UTC
Checked at (UTC)StatusHTTPResponseEndpoints
Offline4045279ms0
Offline4041826ms0
Offline4042030ms0
Offline4041624ms0
Offline4041751ms0
Offline4042989ms0
Offline4041933ms0
Offline4042746ms0
Offline4041180ms0
Offline4041660ms0
Offline4041461ms0
Offline4042003ms0
Offline4041415ms0
Offline4041461ms0
Offline4044493ms0
Offline4042697ms0
Offline4041986ms0
Offline4041803ms0

Changes0 in 30d

No changes recorded in the last 30 days.

all changes

Over time

On-chain volume

This service shares a payout address and its probe has been failing, so its on-chain volume is suppressed until it responds again. Settlements on a shared address while a member is down are not attributed to it.

Uptime 16 of 29 completed days below 100%
uptime below 100%, to scale uptime 0%
Uptime
16 of 29 completed days below 100%

This service shares a payout address and its probe has been failing, so its on-chain volume is suppressed until it responds again. Settlements on a shared address while a member is down are not attributed to it.

More charts
Response time daily average, ms min 769ms, avg 1210ms, max 1599ms

09-25 to 10-24* UTC

Scores over time

x402 compliance low 13/14, high 13/14

09-25 to 10-24* UTC

Price percentile in Blockchain own low to high; exact values below

09-25 to 10-24* UTC

Site signals present (of 6) own low to high; exact values below

09-25 to 10-24* UTC

Scores: one day per column, 09-25 to 10-24*, on the columns of Response time. Uptime held below 100% on some days in this window, including any partial day. Daily readings remain in the Uptime strip and Values. The checklist grew from 11 to 14 checks on 2026-07-28, before this window. Pillar lines use their own low and high. Exact dated readings are available in each readout and in Values.

Each series spans only the dates it has data for. Every series is also served as JSON at /api/v1/services/chainkit/price, /scores, /volume and /buyers.

Values

* today so far, partial (UTC).

The uptime summary counts completed UTC days only. The strip, readouts and table retain today's partial reading.

Assessment history last recorded at . Each UTC day uses its last recorded run; missing readings stay unmeasured. Assessment history JSON · Measurement methodology.

Daily values, 2026-09-25 to 2026-10-24: uptime percent, average response milliseconds, compliance passed/total, price percentile 0-100, site signals out of 6; UTC dates
DayUptimeResponseCompliancePrice percentileSite signals
2026-09-25100%1399.79ms13/14p663/6
2026-09-26100%1599.24ms13/14p653/6
2026-09-27100%1597.17ms13/14p653/6
2026-09-28100%1434.08ms13/14p653/6
2026-09-29100%1285.27ms13/14p693/6
2026-09-30100%1344.21ms13/14p693/6
2026-10-01100%1037.72ms13/14p693/6
2026-10-02100%1031.76ms13/14p693/6
2026-10-03100%1235.61ms13/14p693/6
2026-10-04100%1149.07ms13/14p693/6
2026-10-05100%872.34ms13/14p703/6
2026-10-06100%1107.48ms13/14p703/6
2026-10-07100%1070.51ms13/14p713/6
2026-10-0886.84%768.77ms13/14p743/6
2026-10-090%no data13/14p741/6
2026-10-100%no data13/14p741/6
2026-10-110%no data13/14p741/6
2026-10-120%no data13/14p741/6
2026-10-130%no data13/14p741/6
2026-10-140%no data13/14p761/6
2026-10-150%no data13/14p761/6
2026-10-160%no data13/14p761/6
2026-10-170%no data13/14p750/6
2026-10-180%no data13/14p750/6
2026-10-190%no data13/14p751/6
2026-10-200%no data13/14p751/6
2026-10-210%no data13/14p751/6
2026-10-220%no data13/14p751/6
2026-10-230%no data13/14p751/6
2026-10-24*no datano data13/14p751/6

Alternatives in Blockchain

keyring-agent strong 97/100 99.9% up 30d $1.5k 30d
OneSource strong 96/100 100% up 30d $74.27 30d
Loyal Spark strong 96/100 100% up 30d $84.41 30d
SolEnrich strong 93/100 100% up 30d $88.06 30d
Chainlink for Agents solid 90/100 100% up 30d $283.92 30d

5 of 74 other ranked services in Blockchain, ordered by the same measured score.

see the whole category

Own this service?

Keep this listing accurate. Ownership is proven with a domain check and every change is reviewed by hand.

Update this listing

Earn the verified tier: x402list pays a real call to this endpoint and, if it delivers, the service is delivery-verified. The fee covers the cost of the probe, not the badge; there is no refund if the call does not deliver. Agent and API only, no in-browser signing. See /api.

Verify this service ($0.25)
Embed a badge

HTML

<a href="https://x402-list.com/services/chainkit?utm_source=badge&utm_medium=referral&utm_campaign=embed">
  <img src="https://x402-list.com/badge/chainkit.svg" alt="chainkit listed on x402-list" height="28">
</a>

Markdown

[![chainkit on x402-list](https://x402-list.com/badge/chainkit.svg)](https://x402-list.com/services/chainkit?utm_source=badge&utm_medium=referral&utm_campaign=embed)

HTML, live uptime variant

<a href="https://x402-list.com/services/chainkit?utm_source=badge&utm_medium=referral&utm_campaign=embed">
  <img src="https://x402-list.com/badge/chainkit.svg?data=uptime" alt="chainkit uptime on x402-list" height="28">
</a>
Delisting

To request delisting, email info@x402-list.com with the service name, slug, or URL. Removal is free and does not require proof of ownership. Contact.