Skip to main content
For agents and developers: the exact rules bundles follow. For what a bundle is and why to deploy one, read 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:
rip deploy <dir> and rip bundle deploy <dir> are the same command. Its flags:
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

The web app has no bundles page: deploy and manage bundles from the CLI or through your agent. A deleted bundle shows on the web app’s Trash page, where you can restore it.

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; each names the bundle id: its id, your slug for it, its live URL or its page URL. 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).