SmartPDF (Document Creation Node)
<div class="post-category"><span class="cat-badge cat-nodes">Nodes</span></div>
<p class="lead"><strong>SmartPDF produces AI-interactive, blockchain-certified documents. Unlike static PDFs, a SmartPDF carries an embedded chat agent, a verifiable integrity seal, and fine-grained access controls.</strong></p>
<h2>Overview</h2>
<p>Hosted at https://smartpdf.1bz.biz, SmartPDF takes source content (markdown, HTML, or an IPVault asset), wraps it with an on-document assistant, and anchors the final hash on Polygon for tamper detection.</p>
<h2>Key components</h2>
<ul><li>Interactive assistant embedded in the PDF viewer</li><li>CopyGuard-style integrity seal</li><li>Access tokens bound to DZID identities</li><li>Delivery via Fax, email, or direct download</li><li>Consumes DZIT credits per generation</li></ul>
<h2>Related</h2>
<ul><li>[IPVault Node](/post.php?slug=ipvault-node)</li><li>[CopyGuard Node](/post.php?slug=copyguard-node)</li><li>[DZID — Virtual Identity](/post.php?slug=dzid-virtual-identity)</li></ul>
Powered by BizNode™
Related Posts
Add a Command to Your Bot in 10 Lines of YAML
Adding a new bot feature used to mean editing Python, wiring a `CommandHandler`, and redeploying. With the Feature Manifest Framework it is four steps and about ten lines of YAML — and you get a slash command and a paid network handle from
How 1BZ Bots Define Features via Manifest
1BZ bots used to hand-wire every capability as a Python `CommandHandler`. That put even a trivial command one code change and a redeploy away from production. The Feature Manifest Framework replaces that with a declarative YAML file at `bot
Slash Command vs Handle — what each is for
Slash commands and handles are related but not identical. A slash command is the owner-facing UI inside a single bot; a handle is a network-facing service endpoint that any other bot, workflow, or API on the 1BZ network can call. The same u