Skip to main content

​
Bundles

A bundle is a versioned tree of files deployed as a single unit. Where an artifact is one file, a bundle is a whole directory — and its primary use is hosting a live static website. Deploy a folder of HTML/CSS/JS and get back a URL that serves it as a real site: relative links between pages work, assets load, and client-side JavaScript runs. It’s the right primitive for a multi-page course, a microsite, a generated report with assets, or any static dist/ directory.

​
Deploy a directory

The CLI zips the directory, uploads it, and prints two URLs:
  • Live site — https://bundles.tokenrip.com/<id>/ — the rendered website.
  • Page — https://tokenrip.com/b/<id> — a shareable page showing the file list, with links to the live site and a downloadable archive.
index.html at the root is the default entrypoint. Re-deploy a new version anytime:
Live sites are served from a dedicated, cookieless origin (bundles.tokenrip.com) — separate from the app — so your site’s JavaScript runs in full isolation. Your fonts and CDN scripts load normally.

​
Visibility

​
Managing bundles

Operators can also deploy and manage bundles from the Bundles tab in the dashboard (drag a .zip to deploy).

​
For agents

Every bundle is readable structurally without rendering: GET /v0/bundles/<id> returns metadata plus the full file manifest, and GET /v0/bundles/<id>/files/<path> streams any file. The MCP tools deploy_bundle, bundle_get, and bundle_get_file cover the same ground. The /b/<id> page embeds tokenrip:* meta tags and JSON-LD so an agent can discover the live site and file tree from the HTML alone.
Building the site from a folder is the CLI’s job (rip deploy ./dir). The dashboard accepts a pre-made .zip.

​
Runtime packages

Tokenrip also uses immutable bundle versions as an internal package format for the next Surface runtime. A runtime package contains a tokenrip.runtime.json manifest, an entrypoint such as index.html, and all code and assets needed by that revision. The manifest declares binding slots and only five broker actions: artifact.read, artifact.version.create, table.rows.read, table.row.patch, and table.rows.append. Targets and allowed actions are resolved when a Surface revision is configured; secrets never belong in the package. Runtime packages differ from ordinary live-site bundles. Ordinary bundles are served as websites from bundles.tokenrip.com. Runtime packages are intended for isolated, ticketed delivery tied to a Surface launch and live authorization.
The package store and policy infrastructure are present, but package-backed Surface validation and hosting remain fail-closed until H3/H5. Do not treat a runtime package as a supported public Surface deployment yet.