OpenAPI and downloads
Validated OpenAPI 3.1 documents, JSON Schemas, and every machine readable artefact this site publishes.
Universe implementation Verified 2026-08-31
Describes what a Bitcoin Universe service actually does today. It is not a statement about the protocol in general.
- Page ID
-
reference/openapi - Normative authority
- Universe implementation documentation
- Networks
- mainnet
- Documentation version
- 2026.08
- Audience
- developer, integrator
- Owner
- bitcoin-universe-docs
- Sources
-
- Universe ARC-20 index and Marketplace v1 authority
at
670030e50071private repository - Universe Atomicals NFT, Realm, and Subrealm index
at
1d9109c68d95private repository
- Universe ARC-20 index and Marketplace v1 authority
at
- Known limitations
-
- No production host is published in any document. Set the server variable to the origin your deployment exposes.
このコンテンツはまだ日本語訳がありません。
Every document here is validated in CI. A route present in a document but absent from its source inventory fails the build, and so does the reverse.
Documents
Section titled “Documents”| Document | Operations | Source revision | Download |
|---|---|---|---|
| Universe ARC-20 index and feed API Verified ticker resolution, token details, holders, and confirmed activity for ARC-20. | 5 | 670030e50071 | JSON |
| Universe Atomicals NFT, Realm, and Subrealm API Read model for plain NFTs, Realms, and Subrealms projected from Atomicals ElectrumX. | 36 | 1d9109c68d95 | JSON |
| Atomicals Marketplace v1 authority Four isolated protocol authorities for ARC-20, plain NFTs, Realms, and Subrealms. | 35 | 670030e50071 | JSON |
|
Shared schema library
One component library every document draws from | 1 | 1.0.0 | JSON |
|
Source manifest
Every consumed source and its revision | 1 | 1.0.0 | JSON |
|
Conformance vectors
Executed ARC-20 allocation cases | 1 | 1.0.0 | JSON |
|
CLI inventory
Commands parsed from the pinned CLI source | 1 | 1.0.0 | JSON |
|
AIP registry
Proposals with implementation evidence, never assumed | 1 | 1.0.0 | JSON |
|
AVM opcode inventory
Generated from the beta interpreter source | 1 | 1.0.0 | JSON |
|
Ecosystem registry
Records with evidence and last-verified dates | 1 | 1.0.0 | JSON |
|
Page manifest
Every page with its stable ID, status, sources, and content hash | 1 | 1.0.0 | JSON |
What CI checks
Section titled “What CI checks”| Check | Effect when it fails |
|---|---|
| OpenAPI 3.1 structure | Build fails |
| Operation identifier uniqueness within and across documents | Build fails |
| Every operation has a summary, a declared tag, and responses | Build fails |
| Route inventory equals the documented paths, in both directions | Build fails |
| Every response example validates against its own schema | Build fails |
| Every deprecated route names a replacement | Build fails |
| No production host or routable address appears | Build fails |
Amount encoding
Section titled “Amount encoding”Every satoshi and protocol quantity is a decimal string in these contracts. JSON numbers are rejected, so no precision is lost in transit and no client silently converts a large integer into a float.
Using the documents
Section titled “Using the documents”- Download the document for the surface you integrate with.
- Generate a client rather than hand writing calls. See TypeScript client.
- Run the conformance vectors against your build.
- Pin the document version alongside your service revision.
- Regenerate on every upgrade and diff the generated types.