CKCloud Token + OpenClaw

1. Overview

CKCloud provides x402 paywall-based authentication for LLM access. Main endpoints:

• Management and query APIs: /v1/*
• Model invocation endpoint: /x402/v1/chat/completions

Core Flow

1. The client calls an x402-protected LLM endpoint.
2. If a valid payment signature is included and balance is sufficient, the backend validates and forwards to the upstream model API.
3. If payment is missing or balance is insufficient, the backend returns a paywall/payment requirement.
4. The client completes payment signing and retries the request.

2. OpenClaw Installation and Usage

2.1 Install

Run on the machine where OpenClaw will be installed:

curl -fsSL https://pkg.ckcloudai.com/update.sh | bash

After installation, a wallet address is generated (or reused from cache):

• Solana wallet: HjrbgMg*********************************2mqYha5
• Base wallet: 0x64eb7a0**********************0cc322F6

2.2 Start / Restart

openclaw gateway restart

2.3 Top Up

Transfer funds to the generated wallet address, then you can use OpenClaw directly.

2.4 Check Status and Wallet

/stats 
/wallet

/stats — Usage Statistics

/wallet — Wallet Info

2.5 Uninstall and Reinstall

Uninstall:

bash ~/.openclaw/extensions/ckcloud/scripts/uninstall.sh

Reinstall:

curl -fsSL https://pkg.ckcloudai.com/reinstall.sh | bash

3. x402 Authentication and Payment Flow

Endpoint: POST /x402/v1/chat/completions

3.1 Request Requirements

Headers:

• Content-Type: application/json
• PAYMENT-SIGNATURE (optional): Base64-encoded x402 PaymentPayload

Body (OpenAI-compatible):

{
  "model": "google/gemma-3n-E4B-it",
  "messages": [
    {"role": "user", "content": "Hello"}
  ]
}

3.2 Server Behavior

3.3 Key Response Headers

• PAYMENT-REQUIRED
• PAYMENT-RESPONSE

Clients should use these headers to complete payment and retry.

3.4 Recommended Request Flow

Step 1: First request (without signature)

curl "http://localhost:8080/x402/v1/chat/completions" \
  -H "Content-Type: application/json" \
  -d '{"model":"google/gemma-3n-E4B-it","messages":[{"role":"user","content":"Hello"}]}'

Step 2: Retry with signature after payment

curl "http://localhost:8080/x402/v1/chat/completions" \
  -H "Content-Type: application/json" \
  -H "PAYMENT-SIGNATURE: <base64-payment-payload>" \
  -d '{"model":"google/gemma-3n-E4B-it","messages":[{"role":"user","content":"Hello"}]}'

4. API Reference

Base URL depends on deployment: http://<host>:<port>. Responses are generally application/json.

curl -G "http://localhost:8080/v1/balance" \
  --data-urlencode "Pubkey=YourPublicKey"

{"balance": 12.345678}

curl -G "http://localhost:8080/v1/consume-history" \
  --data-urlencode "Pubkey=YourPublicKey" \
  --data-urlencode "Page=1" \
  --data-urlencode "Limit=20"

curl -G "http://localhost:8080/v1/payment-history" \
  --data-urlencode "Pubkey=YourPublicKey" \
  --data-urlencode "Chain=eip155:1"

curl "http://localhost:8080/v1/models"

// Response fields: model, displayName, provider, modelType,
// contextLength, inputPrice, outputPrice, supportFunction

curl "http://localhost:8080/x402/v1/chat/completions" \
  -H "Content-Type: application/json" \
  -H "PAYMENT-SIGNATURE: <base64-payment-payload>" \
  -d '{"model":"google/gemma-3n-E4B-it","messages":[{"role":"user","content":"Hello"}]}'

5. Error Codes and Troubleshooting

5.1 Common x402 Errors

5.2 Common /v1 Errors

5.3 Troubleshooting Checklist

1. Call /v1/models to confirm model availability.
2. Call /v1/balance to verify account balance.
3. If /x402/... returns paywall, verify client-side handling of PAYMENT-REQUIRED.
4. If signature request still fails, verify Base64 validity, chain type, and wallet/signature match.
5. Use /v1/consume-history and /v1/payment-history for detailed records.