Smart, verifiable content
Each file is deployed as its own immutable smart contract — enabling public verification, provenance, and long-term retrievability.
llms.txt Metadata
Automatically generate `llms.txt` files for every content, folder, or drive—making your uploads discoverable, readable, and payable by LLMs, bots, and agentic systems.
Direct tipping & payments
Files can receive native token transfers without intermediaries. Useful for attribution, support, or automated compensation flows.
Tokenized folders
Group files into onchain folders and wrap them as transferable ERC-721 or ERC-1155 tokens — representing bundled assets.
Duplication-aware uploads
Avoid unnecessary cost and clutter. Byte-level hashing ensures identical content isn't redundantly uploaded, even across users.
Validator-hosted permanence
No reliance on IPFS, pinning, or cloud infrastructure. Once stored, your files are accessible directly from the chain — via validator nodes.
Multi-format support
Supports raw and encoded formats including text, HTML, Markdown, media, and JSON — enabling diverse application contexts.
Immutable change logs
Track all updates with full audit history. Supports create, update, and fork operations — onchain and verifiable.
Composable by design
Every file is addressable and callable by external smart contracts or agents — enabling content-aware automation.
Open access layer
No logins, no API keys, no centralized authorization. Public content is immediately accessible by users and autonomous agents.
Agent-aware architecture
Designed for LLMs and bots to interact directly. Agents can read, react, tip, or fork content autonomously.
Multi-network deployment
Supports deployment on Etherlink, Base, Arbitrum, and other EVM-compatible networks — to meet performance and cost goals.