x402 List

x402 Protocol Service Directory

chainkit

Blockchain PAYMENT-READY

payment-ready until 2026-09-15

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.

Part of the Leeworks operator hub

Pay from $0.02 per request in USDC on Base, settled onchain via the x402 protocol, no signup, no API key needed.

BASE URL https://chainkit.leeworks.dev WEBSITE https://chainkit.leeworks.dev ENDPOINTS 1 NETWORK Base ASSET USDC MEMBER SINCE 2026-07-25 MONITORED SINCE 2026-07-25

VERDICT

ranking generation 3

solid 89/100 #5 of 41 in Blockchain by measured score

What the score read on this service: status online, 100% uptime 30d, 1621ms 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.

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 41 listings, this one among them. That set is wider than the 41 the position above is counted against, 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.

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.

ALTERNATIVES IN BLOCKCHAIN

Other Blockchain services in this directory, ordered by the same measured score. The figures are ours: 30-day uptime from our own probes, 30-day settlement volume read on-chain (a conservative undercount, and null where we cannot measure it, never a zero).

Ranked alternative x402 services in the same category, with band, measured score, 30-day uptime and 30-day on-chain settlement volume
SERVICE BAND SCORE UPTIME 30D VOL 30D
3Route strong 97 99.9% ---
Loyal Spark strong 96 99.9% $137.59
OneSource strong 96 100% $69.47
Testnet ETH Merchant solid 90 100% ---
true402 solid 89 96.1% $0.92
5 of 40 other ranked services in Blockchain · see the whole category

ASSESSMENT

updated 25m ago

The parts the verdict above is computed from, each with its proof. Click any chip. Measured values stay read-only; unknown is honest, and an unknown is never counted as a zero.

reliability 100%
uptime 24h
100%
uptime 7d
99.8%
uptime 30d
100%
uptime 90d
99.8%
response p95
1621ms
avg response
1360ms
total checks
2,758

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

compliance A (13/14): declares the current x402 version (2)

13 of 14 x402 conformance checks pass; failing: declares the current x402 version (2). Full checklist below.

jump to compliance checklist

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

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.

traction ---

This service settles on a network x402-list does not measure yet, so on-chain volume is not counted here. Shown as unmeasured, not zero.

WHAT IT DOES

ai-derived

No AI synthesis has been produced for this service yet.

ENDPOINTS

Service endpoints with HTTP method, path, description, pricing, and network
METHOD PATH DESCRIPTION PRICE NETWORK ASSET 402 CHANNEL
POST /v1/crypto 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 $0.02 Base USDC body (v1 style)
1 endpoints

REQUEST / RESPONSE EXAMPLE

An unpaid request to POST /v1/crypto returns HTTP 402 with the payment terms. Settle onchain via your facilitator, then retry with the X-Payment header.

// request
curl -i -X POST 'https://chainkit.leeworks.dev/v1/crypto'
// 402 response (captured by monitor) · 1 payload · click to expand
[
  {
    "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
  }
]

OVER TIME

All charts use the 30d selector; 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. On-chain volume and distinct buyers are measured over the service's settlement address and are a conservative undercount (only settlements that reach a measured facilitator are counted). The on-chain series roll up hourly, so the latest day can be up to about an hour behind; distinct buyers are counted per payout address, so a service that settles to more than one address is an upper bound.

UPTIME
08-10 · uptime 100.0% · 1730ms avg08-11 · uptime 100.0% · 1012ms avg08-12 · uptime 100.0% · 908ms avg08-13 · uptime 100.0% · 2380ms avg08-14 · uptime 100.0% · 872ms avg08-15 · uptime 100.0% · 1152ms avg08-16 · uptime 100.0% · 2923ms avg08-17 · uptime 100.0% · 2774ms avg08-18 · uptime 100.0% · 2986ms avg08-19 · uptime 100.0% · 1765ms avg08-20 · uptime 100.0% · 1073ms avg08-21 · uptime 100.0% · 850ms avg08-22 · uptime 100.0% · 973ms avg08-23 · uptime 100.0% · 829ms avg08-24 · uptime 100.0% · 997ms avg08-25 · uptime 100.0% · 1109ms avg08-26 · uptime 100.0% · 1096ms avg08-27 · uptime 100.0% · 1438ms avg08-28 · uptime 100.0% · 1120ms avg08-29 · uptime 100.0% · 1241ms avg08-30 · uptime 100.0% · 1536ms avg08-31 · uptime 100.0% · 1446ms avg09-01 · uptime 100.0% · 1216ms avg09-02 · uptime 100.0% · 878ms avg09-03 · uptime 100.0% · 1148ms avg09-04 · uptime 98.9% · 1642ms avg09-05 · uptime 100.0% · 994ms avg09-06 · uptime 100.0% · 809ms avg09-07 · uptime 100.0% · 797ms avg09-08 · uptime 100.0% · 1239ms avg08-1009-08
30d UPTIME 100%
RESPONSE TIME
08-10 · 1730ms avg08-10 · 1730ms avg08-11 · 1012ms avg08-11 · 1012ms avg08-12 · 908ms avg08-12 · 908ms avg08-13 · 2380ms avg08-13 · 2380ms avg08-14 · 872ms avg08-14 · 872ms avg08-15 · 1152ms avg08-15 · 1152ms avg08-16 · 2923ms avg08-16 · 2923ms avg08-17 · 2774ms avg08-17 · 2774ms avg08-18 · 2986ms avg08-18 · 2986ms avg08-19 · 1765ms avg08-19 · 1765ms avg08-20 · 1073ms avg08-20 · 1073ms avg08-21 · 850ms avg08-21 · 850ms avg08-22 · 973ms avg08-22 · 973ms avg08-23 · 829ms avg08-23 · 829ms avg08-24 · 997ms avg08-24 · 997ms avg08-25 · 1109ms avg08-25 · 1109ms avg08-26 · 1096ms avg08-26 · 1096ms avg08-27 · 1438ms avg08-27 · 1438ms avg08-28 · 1120ms avg08-28 · 1120ms avg08-29 · 1241ms avg08-29 · 1241ms avg08-30 · 1536ms avg08-30 · 1536ms avg08-31 · 1446ms avg08-31 · 1446ms avg09-01 · 1216ms avg09-01 · 1216ms avg09-02 · 878ms avg09-02 · 878ms avg09-03 · 1148ms avg09-03 · 1148ms avg09-04 · 1642ms avg09-04 · 1642ms avg09-05 · 994ms avg09-05 · 994ms avg09-06 · 809ms avg09-06 · 809ms avg09-07 · 797ms avg09-07 · 797ms avg09-08 · 1239ms avg09-08 · 1239ms avg08-1009-08
AVG RESP 1360ms
PRICE (captured 402, USD)
08-09 · $0.0209-08 · $0.02$0.0208-0909-08
SUB-SCORES (uptime + x402 compliance)
08-10 uptime: 99.5% compliance: 93% checks08-11 uptime: 99.5% compliance: 93% checks08-12 uptime: 99.6% compliance: 93% checks08-13 uptime: 99.6% compliance: 93% checks08-14 uptime: 99.6% compliance: 93% checks08-15 uptime: 99.6% compliance: 93% checks08-16 uptime: 99.7% compliance: 93% checks08-17 uptime: 99.7% compliance: 93% checks08-18 uptime: 99.7% compliance: 93% checks08-19 uptime: 99.7% compliance: 93% checks08-20 uptime: 99.7% compliance: 93% checks08-21 uptime: 99.7% compliance: 93% checks08-22 uptime: 99.7% compliance: 93% checks08-23 uptime: 99.7% compliance: 93% checks08-24 uptime: 99.7% compliance: 93% checks08-25 uptime: 99.7% compliance: 93% checks08-26 uptime: 99.7% compliance: 93% checks08-27 uptime: 99.9% compliance: 93% checks08-28 uptime: 99.9% compliance: 93% checks08-29 uptime: 99.9% compliance: 93% checks08-30 uptime: 99.9% compliance: 93% checks08-31 uptime: 99.9% compliance: 93% checks09-01 uptime: 99.9% compliance: 93% checks09-02 uptime: 99.9% compliance: 93% checks09-03 uptime: 99.9% compliance: 93% checks09-04 uptime: 99.8% compliance: 93% checks09-05 uptime: 100.0% compliance: 93% checks09-06 uptime: 100.0% compliance: 93% checks09-07 uptime: 100.0% compliance: 93% checks09-08 uptime: 100.0% compliance: 93% checksuptimecompliance08-1009-08

checklist grew 11->14 on 2026-07-28; a step here is a metric change, not a regression

PILLARS OVER TIME (measured)

Measured site and economics pillars from the assessment history, so the latest value shown elsewhere on this page reads as a point on a trend rather than a permanent state.

VOLUME (on-chain settlement, USD)
This service settles on a network x402-list does not measure yet, so on-chain volume is not counted here. Shown as unmeasured, not zero.
DISTINCT BUYERS
This service settles on a network x402-list does not measure yet, so distinct on-chain buyers are not counted here. Shown as unmeasured, not zero.

COMPLIANCE

13/14 checks pass · grade A · failing: declares the current x402 version (2)

last 402 captured 2026-07-25 · last up 2026-09-08

  • 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

SITE PILLARS

  • homepage reachable
  • openapi doc
  • pricing page
  • llms.txt
  • robots.txt
  • terms page
recent checks (18) live · click to expand
TIME STATUS RESP CAUSE
● OK 1006ms
● OK 1111ms
● OK 1097ms
● OK 1003ms
● OK 1217ms
● OK 1055ms
● OK 1079ms
● OK 1095ms
● OK 842ms
● OK 1265ms
● OK 1042ms
● OK 865ms
● OK 832ms
● OK 782ms
● OK 1263ms
● OK 725ms
● OK 718ms
● OK 1608ms

EMBED THIS BADGE

Show that chainkit is monitored on x402-list. Paste this on your site or README, it links back to this live listing.

chainkit listed on x402-list
status
chainkit uptime on x402-list
live uptime
// 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>

RUN THIS SERVICE?

Keep this listing accurate: propose changes to the name, description, website, category or add new endpoints to monitor. Ownership is verified with a domain proof and every change is reviewed manually; measured data stays read-only.

[ 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) ]

To request delisting, email info@x402-list.com or update your listing at /services/chainkit/update.