# Inscribe documentation

Bitcoin creation learning environment for Inscribe. Source commit 77304a4e97002b372ef983e97350cabe8a2618b0. Generated 2026-09-06T11:50:08.197Z.
The final in-app quote is always authoritative; this site teaches, the app decides.

## Pages

- [That page is not here](https://bitcoinuniverseio.github.io/docs-inscribe/404) [markdown](/docs-inscribe/md/404.md): The page you asked for does not exist on this documentation site. Here is where to go instead.
- [Changelog](https://bitcoinuniverseio.github.io/docs-inscribe/about/changelog) [markdown](/docs-inscribe/md/about/changelog.md): What changed in this documentation, and where to find the changelog for the Inscribe product itself.
- [Where pages moved](https://bitcoinuniverseio.github.io/docs-inscribe/about/migration) [markdown](/docs-inscribe/md/about/migration.md): Every file from the previous flat structure and where its content now lives, plus the redirects that keep old links working.
- [Asset safety and UTXO classification](https://bitcoinuniverseio.github.io/docs-inscribe/concepts/asset-safety) [markdown](/docs-inscribe/md/concepts/asset-safety.md): How Inscribe decides which outputs it may spend on your behalf, the three classification states, why unknown is never treated as safe, and the one surface that deliberately lets you spend an asset.
- [The life of an order](https://bitcoinuniverseio.github.io/docs-inscribe/concepts/order-lifecycle) [markdown](/docs-inscribe/md/concepts/order-lifecycle.md): How an Inscribe order goes from a quote to an asset in your wallet, what you sign and when, how payment is detected, and what happens when the hour runs out.
- [Where the data comes from](https://bitcoinuniverseio.github.io/docs-inscribe/concepts/source-freshness) [markdown](/docs-inscribe/md/concepts/source-freshness.md): The six states a data source can be in, how Inscribe reports a source that is down or catching up, why an empty result is never shown as an answer, and what stays working.
- [Wallets and the two addresses](https://bitcoinuniverseio.github.io/docs-inscribe/concepts/wallets-and-addresses) [markdown](/docs-inscribe/md/concepts/wallets-and-addresses.md): Why an Ordinals wallet keeps a payment address and an Ordinals address, what each one is for, how Inscribe keeps them apart, and which wallets it connects to.
- [What a transaction costs](https://bitcoinuniverseio.github.io/docs-inscribe/concepts/what-it-costs) [markdown](/docs-inscribe/md/concepts/what-it-costs.md): The three amounts in an Inscribe quote, what each satoshi buys, how a fee rate is chosen, and why only two of the three lines are fees.
- [Inscribe in a batch](https://bitcoinuniverseio.github.io/docs-inscribe/create/batch) [markdown](/docs-inscribe/md/create/batch.md): Inscribe up to 1,000 items in one job, how the payment is fanned out, why bigger batches wait for confirmations, and what the service fee does across a batch.
- [Create a collection](https://bitcoinuniverseio.github.io/docs-inscribe/create/collections) [markdown](/docs-inscribe/md/create/collections.md): The three ways Inscribe groups inscriptions into a collection, gallery, parent and child, and delegate, with the limits on each and when to use which.
- [Deploy a token](https://bitcoinuniverseio.github.io/docs-inscribe/create/deploy-a-token) [markdown](/docs-inscribe/md/create/deploy-a-token.md): Create a new token on Bitcoin. Which protocols support a deploy, what each one does differently, the shared workflow, and what a deploy does not give you.
- [Etch a rune](https://bitcoinuniverseio.github.io/docs-inscribe/create/etch-a-rune) [markdown](/docs-inscribe/md/create/etch-a-rune.md): Create a new rune with Runes or Mezcal, mint an open rune, and split a rune balance across outputs. What etching commits to permanently and how the two protocols differ.
- [Your first inscription](https://bitcoinuniverseio.github.io/docs-inscribe/create/first-inscription) [markdown](/docs-inscribe/md/create/first-inscription.md): From an empty wallet to a confirmed inscription, with every check in between.
- [Inscribe a file](https://bitcoinuniverseio.github.io/docs-inscribe/create/inscribe-a-file) [markdown](/docs-inscribe/md/create/inscribe-a-file.md): Put an image, audio, video, HTML or JSON file on Bitcoin, with the accepted types, the size limits per destination, what it costs and how to verify the result.
- [Inscribe text](https://bitcoinuniverseio.github.io/docs-inscribe/create/inscribe-text) [markdown](/docs-inscribe/md/create/inscribe-text.md): Write text onto Bitcoin as an Ordinals inscription, an OP_RETURN record or a Drop, with the size limits, the cost and how to find it again afterwards.
- [Mint a token](https://bitcoinuniverseio.github.io/docs-inscribe/create/mint-a-token) [markdown](/docs-inscribe/md/create/mint-a-token.md): Claim an amount of an existing token or rune, which protocols support minting, the shared workflow, and why a confirmed mint can still be refused by a protocol index.
- [Transfer an asset](https://bitcoinuniverseio.github.io/docs-inscribe/create/transfer-an-asset) [markdown](/docs-inscribe/md/create/transfer-an-asset.md): Move an inscription, rune or token balance you already hold, which address signs, why TAP transfers take two steps, and how fees are funded without touching your assets.
- [What a transaction costs](https://bitcoinuniverseio.github.io/docs-inscribe/create/what-it-costs) [markdown](/docs-inscribe/md/create/what-it-costs.md): Network fee, service fee, and the output value that stays yours, piece by piece.
- [Workspace map](https://bitcoinuniverseio.github.io/docs-inscribe/create/workspaces) [markdown](/docs-inscribe/md/create/workspaces.md): Every Inscribe workspace, what it does, and which ones have in-app guides.
- [Advanced transaction tools](https://bitcoinuniverseio.github.io/docs-inscribe/manage/advanced-transactions) [markdown](/docs-inscribe/md/manage/advanced-transactions.md): Four tools for when a normal flow will not do what you need, what each is for, and which one deliberately lets you spend an asset.
- [Orders you started](https://bitcoinuniverseio.github.io/docs-inscribe/manage/pending-orders) [markdown](/docs-inscribe/md/manage/pending-orders.md): How Inscribe gets you back to an order after a closed tab or a reload, what the browser remembers, what it deliberately does not, and why the list shows no status.
- [Portfolio](https://bitcoinuniverseio.github.io/docs-inscribe/manage/portfolio) [markdown](/docs-inscribe/md/manage/portfolio.md): What Portfolio shows, why the bitcoin balance and the asset balance are never added together, what Partial means, and how to see any address without a wallet.
- [Recovery routes](https://bitcoinuniverseio.github.io/docs-inscribe/manage/recovery) [markdown](/docs-inscribe/md/manage/recovery.md): Every route back from an unpaid, underpaid, stuck or interrupted order, the two dedicated repair tools, and the one situation with no recovery at all.
- [Accessibility](https://bitcoinuniverseio.github.io/docs-inscribe/reference/accessibility) [markdown](/docs-inscribe/md/reference/accessibility.md): The release gates every page and screen must pass, in both themes.
- [Admin Control Center](https://bitcoinuniverseio.github.io/docs-inscribe/reference/admin-control-center) [markdown](/docs-inscribe/md/reference/admin-control-center.md): The private operations surface: health, orders, indexers, and audit.
- [For agents and LLMs](https://bitcoinuniverseio.github.io/docs-inscribe/reference/agent-surfaces) [markdown](/docs-inscribe/md/reference/agent-surfaces.md): Machine-readable surfaces: full-text corpus, JSONL, skill guidance, MCP tools, and how to cite provenance.
- [Fee tiers](https://bitcoinuniverseio.github.io/docs-inscribe/reference/fee-tiers) [markdown](/docs-inscribe/md/reference/fee-tiers.md): The tiers Inscribe offers, the accepted rate range, where the rates come from, how often they refresh, and every case where two tiers legitimately show the same number.
- [Glossary](https://bitcoinuniverseio.github.io/docs-inscribe/reference/glossary) [markdown](/docs-inscribe/md/reference/glossary.md): The terms used across this documentation and in the Inscribe interface, defined in the sense Inscribe uses them.
- [Order states](https://bitcoinuniverseio.github.io/docs-inscribe/reference/order-states) [markdown](/docs-inscribe/md/reference/order-states.md): The four states an Inscribe order shows you, what each one covers, why there is no cancelled or expired state, and what confirmations are required at each batch size.
- [Performance and media](https://bitcoinuniverseio.github.io/docs-inscribe/reference/performance-and-media) [markdown](/docs-inscribe/md/reference/performance-and-media.md): Load order, caching windows, and where media is served from.
- [Live protocol data status](https://bitcoinuniverseio.github.io/docs-inscribe/reference/protocol-data-status) [markdown](/docs-inscribe/md/reference/protocol-data-status.md): Where live data comes from, what health means, and how order recovery works.
- [Release evidence](https://bitcoinuniverseio.github.io/docs-inscribe/reference/release-evidence) [markdown](/docs-inscribe/md/reference/release-evidence.md): Immutable images, verified revisions, and browser route validation.
- [Social previews](https://bitcoinuniverseio.github.io/docs-inscribe/reference/social-previews) [markdown](/docs-inscribe/md/reference/social-previews.md): Route-aware preview images and the noindex rules for private surfaces.
- [Wallet matrix](https://bitcoinuniverseio.github.io/docs-inscribe/reference/wallets) [markdown](/docs-inscribe/md/reference/wallets.md): The five wallets Inscribe connects to, what each supports, their known limitations, and the rule about which address is used for what.
- [Asset and UTXO safety](https://bitcoinuniverseio.github.io/docs-inscribe/safety/asset-safety) [markdown](/docs-inscribe/md/safety/asset-safety.md): How Inscribe protects asset-bearing outputs, and the checks to run before every signature.
- [Order recovery](https://bitcoinuniverseio.github.io/docs-inscribe/safety/order-recovery) [markdown](/docs-inscribe/md/safety/order-recovery.md): What can interrupt an order, what each state means, and the exact next action for every one of them.
- [Before you spend anything](https://bitcoinuniverseio.github.io/docs-inscribe/start/before-you-spend) [markdown](/docs-inscribe/md/start/before-you-spend.md): The four ways people lose Bitcoin-native assets, what Inscribe does about each, and the two minutes of reading that prevent most of them.
- [Your first inscription](https://bitcoinuniverseio.github.io/docs-inscribe/start/first-inscription) [markdown](/docs-inscribe/md/start/first-inscription.md): A complete walkthrough of inscribing a file or a line of text, from connecting a wallet to seeing the result, with the wallet screen to expect and how to verify what happened.
- [What Inscribe is](https://bitcoinuniverseio.github.io/docs-inscribe/start/what-inscribe-is) [markdown](/docs-inscribe/md/start/what-inscribe-is.md): What Universe Inscribe does, who it is for, how it relates to Core and the rest of Bitcoin Universe, and what it deliberately does not do.
- [What you can create](https://bitcoinuniverseio.github.io/docs-inscribe/start/what-you-can-create) [markdown](/docs-inscribe/md/start/what-you-can-create.md): Inscribe puts Bitcoin creation in one place. Start with a guided plan, practice without spending, then make the real thing.
- [Common problems](https://bitcoinuniverseio.github.io/docs-inscribe/troubleshooting/common-problems) [markdown](/docs-inscribe/md/troubleshooting/common-problems.md): The problems people actually hit in Inscribe, what each one means, and the shortest route to a fix. Ordered by how often they come up.
- [Failure states](https://bitcoinuniverseio.github.io/docs-inscribe/troubleshooting/failure-states) [markdown](/docs-inscribe/md/troubleshooting/failure-states.md): Every way Inscribe reports that something is wrong, what each state blocks, what keeps working, and how to tell a switched-off feature from a broken one.

## Structured data

- [Learning manifest](/docs-inscribe/learning-manifest.json): workflows, protocols, guides, recovery outcomes, source commits
- [JSONL corpus](/docs-inscribe/corpus.jsonl): one record per page with stable ids and provenance
- [Agent guidance](/docs-inscribe/skill.md): read-only tool guidance and safety boundaries