ckbccc.com valid

CCC Documentation (CKBers' Codebase)

CCC is a monorepo-based TypeScript SDK that abstracts CKB's UTXO-based cell model into developer-friendly APIs. The system enables developers to:

For agents: CCC: a TypeScript SDK for Nervos CKB that wraps the UTXO cell model in developer APIs, with docs covering install, packages, concepts and guides.

ckbtypescript sdkcell modelutxonervos network

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-24T02:29:09.179Z. Cached copy · Source on ckbccc.com

# CCC Documentation (CKBers' Codebase)

> CCC is a monorepo-based TypeScript SDK that abstracts CKB's UTXO-based cell model into developer-friendly APIs. The system enables developers to:
> - Compose transactions using high-level abstractions like `ccc.Transaction.from` and automatic input/fee completion
> - Integrate wallets from Ethereum (MetaMask), Bitcoin (UniSat, Xverse), Nostr, and native CKB wallets through a unified `Signer` interface
> - Interact with CKB nodes via WebSocket/HTTP JSON-RPC clients
> - Build UIs using React components (`@ckb-ccc/connector-react`) or Web Components (`@ckb-ccc/connector`)
> - Develop and test using the interactive playground at live.ckbccc.com

Notes for AI agents:

- All links below are absolute URLs. Append `.md` to any docs page URL to get its raw Markdown version (e.g. https://docs.ckbccc.com/en/docs/getting-started/introduction.md).
- The entire documentation concatenated into a single file: https://docs.ckbccc.com/llms-full.txt
- Agent skills index (product-specific operating guidance, split by topic): https://docs.ckbccc.com/skill.md
- Chinese versions of every page are available by replacing `/en/` with `/zh/` in the URL.
- API reference: https://api.ckbccc.com | Playground: https://live.ckbccc.com | Source: https://github.com/ckb-devrel/ccc

## Sections (index pages)

- [Get Started](https://docs.ckbccc.com/en/docs/getting-started): Install CCC, send your first transaction, and learn what CCC can do for you.
- [Core Concepts](https://docs.ckbccc.com/en/docs/concepts): The five primitives behind every CCC app — cells, transactions, signers, clients, and addresses.
- [Guides](https://docs.ckbccc.com/en/docs/guides): Step-by-step recipes for the most common CKB development tasks.
- [CCC Package Guide](https://docs.ckbccc.com/en/docs/packages): Overview of every NPM package; pick the right one for your runtime and features.
- [Core Packages](https://docs.ckbccc.com/en/docs/packages/core-packages): Core primitives, aggregated entry points, and wallet connectors.
- [Protocol Support Layer](https://docs.ckbccc.com/en/docs/packages/protocol-sdks): Protocol-level SDKs — Spore, UDT, SSRI, and Lumos patches.
- [Wallet Integrations](https://docs.ckbccc.com/en/docs/packages/wallet-integrations): Connect any wallet through one unified `Signer` interface.
- [AI Resources](https://docs.ckbccc.com/en/docs/ai-resources): How this documentation is built for AI agents, and how developers should configure and prompt their own AI tools to use it correctly.

## Common tasks (recommended reading paths)

Start here, then read the linked pages in order for the task at hand:

- New to CCC: [Introduction](https://docs.ckbccc.com/en/docs/getting-started/introduction) → [Installation](https://docs.ckbccc.com/en/docs/getting-started/installation) → [Quick Start](https://docs.ckbccc.com/en/docs/getting-started/quick-start)
- Connect a wallet: [Connect Wallets](https://docs.ckbccc.com/en/docs/guides/connect-wallets) → [Signer](http
…

Related sites

Find similar publishers by meaning →

Other listed sites in Developer tools. See the whole category →

Machine-readable: GET /v1/resolve?q=ckbccc.com · GET /v1/domain/ckbccc.com · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for ckbccc.com:
1. POST https://agentwebmap.com/v1/sites/ckbccc.com/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://ckbccc.com/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/ckbccc.com/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/ckbccc.com).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.