HCS-1 · Immutable files
Store a file on Hedera Consensus Service and retrieve it through its content address. Best for permanent media, metadata, and public artifacts.
Create an HCS-1 fileKiloScribe documentation
Build with durable Hedera content.
A local, maintained guide to HCS-1 files, HCS-5 Hashinals, HCS-3 references, and the inscription API. It also includes a ready-to- use kit for AI agents.
Protocol map
Use the standard that matches the artifact.
Keep protocol names explicit so your team and your users always know what a topic represents.
HCS-5 · Hashinal metadata
Pair a primary file with JSON metadata so wallets, indexers, and marketplaces can understand the Hashinal without a private database.
Create a HashinalHCS-3 · Portable links
Use Hedera-backed references as durable links between applications. The same topic can power a site, an API response, or an indexed collection.
See protocol examplesInscription API
Keep the request lifecycle visible.
Generate transaction bytes, sign with the wallet that owns the account, then poll the returned reference until the topic is ready.
POST /api/inscriptions/generate
→ sign transactionBytes with your wallet
→ submit to Hedera
→ GET /api/inscriptions/{tx_id}