Start building
Build, prepare, and publish with KEEL.
The shortest path from local source to a verified release, with the same planning rules in Studio, the SDK, and MCP.
The publication workflow
Studio can guide this sequence. With an agent, connect the KEEL MCP and ask it to prepare a work from your actual files.
Start from the source graph
Give each HTML entry, stylesheet, script, reusable module, and asset a stable identity and explicit dependencies. Preserve the creator's originals. A single public tokenURI call can still assemble a modular project.
- Inspect the target README and architecture before choosing modules.
- Discover compatible modules on the selected chain; resolve their actual receipts and bytes.
- Reuse unchanged object IDs. Upload changed resources and the necessary bindings only.
Prepare before the wallet opens
Measure original bytes, stored bytes, decoded bytes, complete tokenURI bytes, and read gas separately. Render the exact prepared result locally, then build a reviewable publication plan. Wallet approval authorizes the concrete transactions, not an unmeasured substitute.
Read back after publication
Check receipts, storage identity, ordered bindings, complete returned bytes, and decoded integrity on the selected public chain. Open that exact return in a browser. A build or local preview alone is not a completed onchain release.
Independent choices
These settings solve different problems; changing one must not silently change another.
Storage
Compact is the default: use beneficial supported lossless compression and store one representation. Raw preserves supplied bytes and deliberate encoding without automatic compression.
Viewer
The registered verification shell is the default. An explicit viewer=none preserves a supported creator-owned self-contained HTML artifact without claiming canonical protection. Reusable custom shells use their declared registration and compatibility path.
Delivery
At or below 2,000,000 complete prepared tokenURI bytes, full Inline is the automatic delivery default: one public collection call carries the work's modules and assets. Internal storage reads still consume gas. Preserve explicit delivery choices and verify the actual RPC ceiling.
Ask an agent to prepare a work
Use a concrete request that supplies creative intent while leaving technical discovery to the tools.
Example request
Review the plan and measured costs before approving the wallet. The agent must report missing registrations or incompatible readers instead of inventing a fallback.
Prepare this project for KEEL on my selected chain.
Keep the HTML, scripts, styles, and assets as logical resources.
Reuse any unchanged published objects.
Use Compact storage and the registered verification shell.
Use full Inline when the complete tokenURI fits the supported limit.
Show the exact preview, returned byte count, read gas, and upload quote.
Do not publish until I review the plan.