The wagmi-style toolkit for CDR. Install one package and gate encrypted data behind a real on-chain payment or license check — in under a minute.
Encryption stays in CDR. Payments stay in Story's IP layer. cdr-kit wires them together ergonomically across React, autonomous agents, and Solidity.
Drop a <VaultGate> around encrypted data. Hooks, a Clerk-style <Vault> compound, and a mock mode so you can build UI with no wallet or chain.
An LLM agent that buys data with its own wallet — discover, pay, decrypt, decide. Five framework adapters plus an MCP server.
A standard library of tested Solidity conditions — Subscription, TierGate, Composable — plus the CdrKitVault factory that mints, registers IP, and gates in one tx.
One package pulls in the typed core SDK and the provider.
Pass a wagmi config + API URL to go live, or a mock kit for local dev.
It checks the on-chain condition, releases key shares, and hands you the decrypted bytes.
$ pnpm add @cdr-kit/react @cdr-kit/core wagmi viemimport { CdrProvider, VaultGate } from "@cdr-kit/react";
<CdrProvider config={wagmiConfig} apiUrl={apiUrl}>
<VaultGate uuid={4200} auto
fallback={<SubscribeButton />}>
{(data) => <pre>{new TextDecoder().decode(data)}</pre>}
</VaultGate>
</CdrProvider>
// → renders the decrypted payload once the condition is satisfiedHand an LLM the three CDR tools and it runs the whole loop — no human in the loop. A seller stages a subscription-gated trading signal; the agent finds it, pays real $IP from its own wallet, decrypts, and answers.
Every vault's read & write access is a view function the validator network calls. cdr-kit ships a standard library — typed, tested, and addressed in @cdr-kit/contracts.
Recurring paid access — price per period, period length, payee, native-IP or WIP-royalty mode.
0xB75Cc6571ac7E0ee30A519192740fc471e187458Gate by a held Story IP license-token tier. License-aware access, natively on chain.
0xdA704Faf61b2FFB37205d7Eb8C1D26BD3090455fBoolean AND / OR over child conditions, up to 8 deep. Subscription OR tier, royalty AND license.
0x74F2f94e7867b07ECDFbcc667050CBec1dE2800BGate writes to the vault creator, or open access as a sanity / fallback condition.
0x85CEB3…195b2F · 0x78528c…d82389One tx: mint the vault NFT, register it as Story IP, allocate the CDR slot, set the read condition, attach PIL terms.
0xac592f165D8dD1f27A087bdB39c0b2f619FF6C8CReads gated to an absolute [startTs, endTs] window. endTs=0 = open-ended. Release-on-date drops, embargoes, scheduled publication, time-bound previews.
0x67911435F262e7e4EC4F7FEB4e868a67b9dd90b1Auto-unlock to heirs (or public) if the creator stops poke()-ing within duration. The canonical wallet-recovery + leak-on-disappearance pattern.
0x37226f97e184843aB0b8d4f08A55969801B97766Buyer pays → confirms delivery → seller is paid + buyer reads. Optional arbiter for disputes; seller can claim after a buyer-silence timeout.
0x7fcDe02DB7c14fD3587aB2fED064a1D8355b7584N-of-M with two parallel approval paths: off-chain EIP-712 sigs (gas-free) OR on-chain approve(uuid, epoch). Either path reaching threshold passes. rotateSigners invalidates both. First-of-kind in the CDR ecosystem.
0x3A0Cf72f167A2c1f5a7A5025eb36219f28C20FCdA single binary exposes the three CDR tools over stdio — discover, subscribe, access. Paste it into your host and your assistant can transact for itself.
{
"mcpServers": {
"cdr-kit": {
"command": "cdr-kit-mcp",
"env": {
"PRIVATE_KEY": "0x…",
"STORY_API_URL": "https://…"
}
}
}
}npm install -g @cdr-kit/mcp · provides the cdr-kit-mcp binary
Story's testnet — chain id 1315. Contracts verified 2026-05-28; end-to-end encrypt→write→read→decrypt round-trips confirmed on real chain.
CDR's threshold encryption is commodity. The edge is what it composes with — a read condition can require a license tier, a subscription, or a royalty payment, natively, on the same chain.
Story's reference ships ~9 app-internal demo contracts. cdr-kit turns them into a standard, installable, tested, typed library — and adds the advanced conditions (Subscription, TierGate, Composable) that exist nowhere else.
No account, no hosted dashboard, no “sign up.” You install npm packages and own your stack. cdr-kit sits on top ofStory Protocol and CDR — it doesn't replace them.
Pick a template — data-marketplace, paywall, MCP quickstart, or autonomous agent — and ship.