asset-canister

Host frontend assets on the Internet Computer with certified delivery.

Updated Dec 18, 2025
One-click install
npx skills add https://github.com/Looping-AI/looping-control-plane --skill asset-canister-looping-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: asset-canister
Source: https://github.com/Looping-AI/looping-control-plane/tree/main/.agents/skills/asset-canister
Command: npx skills add https://github.com/Looping-AI/looping-control-plane --skill asset-canister-looping-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Hosting frontend assets on the Internet Computer with certified delivery, SPA routing, and domain support to power on-chain web apps without external CDNs.

Core Features & Use Cases

  • Certified asset hosting directly on IC with content integrity guarantees.
  • SPA routing via index.html fallbacks and .ic-assets.json5 configuration.
  • Custom domains and per-environment deployment for local, test, and mainnet scenarios.

Quick Start

Upload your build output to the asset canister and deploy it to IC.

Frequently Asked Questions about asset-canister

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I host frontend assets on the Internet Computer with certified delivery?

Host frontend assets on the Internet Computer by deploying your build output to an asset canister, which provides certified delivery and content integrity guarantees without relying on external CDNs.

Can I configure SPA routing and custom domains for on-chain web apps?

Yes, you can configure SPA routing via index.html fallbacks and set up custom domains using the .ic-assets.json5 configuration file for your on-chain web apps across local and mainnet environments.

How do I programmatically upload static assets to ICP using the SDK?

Programmatically upload static assets to ICP using the icp SDK, which supports configuring cache headers, SPA fallback behavior, and per-environment deployments for local, test, and mainnet scenarios.

What is the best way to scale static hosting for an on-chain frontend without an external CDN?

Scaling static hosting for an on-chain frontend without an external CDN is best achieved by using an asset canister on the Internet Computer, ensuring content integrity and certified asset delivery directly on-chain.

Does the asset canister support per-environment deployment for local and mainnet scenarios?

Yes, the asset canister supports per-environment deployment, allowing you to manage custom-domain setup and .ic-assets.json5 configuration across local, test, and mainnet scenarios for your on-chain frontends.