API Source Map
SAT20 is still evolving quickly. Interface fields, error codes, and testnet-only capabilities change together with STP, indexers, SatoshiNet nodes, and wallet adapters. At this stage the API documentation is source-first: it identifies interface domains, authoritative source entries, stability levels, and integration boundaries. After the interfaces stabilize, OpenAPI, Swagger, and SDK documentation can be added.
The old ORDX indexer Swagger only covers part of early indexer APIs. It does not represent the full current SAT20 / SatoshiNet API system. This page links directly to GitHub source as the most reliable entry point.
Interface Domains
Bitcoin L1 Indexer API
Wallets, exchanges, explorers, STP clients, Agents
Gin routers, handlers, and wire models
SatoshiNet Node RPC
Node operators, miners, wallets, contract tools
JSON-RPC commands, handlers, and help registry
SatoshiNet L2 Indexer API
Wallets, exchanges, explorers, STP clients, Agents
L2 indexer routers, handlers, and models
SAT20 Wallet WASM / PWA Adapter API
Wallet UI, DApps, AI Agents, PWA adapters
WASM wrappers, PWA bridge, Agent adapter contract
STP Agent Adapter API
docs + sat20wallet + transcend
AI Agents and third-party STP clients
sat20-agent-wallet skill contract and adapters
Stability Levels
Public Stable
Externally stable API; field changes need compatibility
Suitable for production
Public Experimental
Usable for testnet and early integration; fields may change
Keep a compatibility layer
Internal
Internal module API with no external compatibility promise
Third parties should avoid direct dependency
Testnet Only
Available only on testnet; mainnet must reject it
For drills, validation, and fault injection only
Deprecated
Historical interface or outdated docs
Not a basis for new integrations
Bitcoin L1 Indexer API
The Bitcoin L1 indexer parses Bitcoin UTXOs, sat ranges, Ordinals, Runes, BRC20, ORDX, mempool, confirmations, and reorg state. It is the entry point for wallets, exchanges, STP, and AI Agents to judge L1 asset facts.
Service startup and RPC initialization
Gin root router and Swagger mount
ORDX / multi-asset APIs
Ordinals content APIs
Bitcoin node proxy APIs
Response models
Indexer manager and handling
ORDX protocol handling
Runes / BRC20 handling
SatoshiNet Node RPC
SatoshiNet node RPC inherits the btcd-style JSON-RPC model and extends it with SatoshiNet transactions, assets, contracts, mining, and network capabilities.
JSON-RPC server
RPC adapters
WebSocket RPC
RPC help / result registry
JSON-RPC command registration and parsing
Chain server commands and results
btcd extension commands and results
Wallet command models
Contract execution and results
POS mining
SatoshiNet L2 Indexer API
The SatoshiNet L2 indexer parses L2 UTXOs, ascend, descend, channels, contracts, Core Node state, and asset state. It is the entry point for verifying L2 asset facts after STP operations.
L2 indexer startup
L2 root router
SatoshiNet query APIs
Indexer query APIs and models
L2 indexer manager
L2 transaction handling
ascend / descend / STP parsing
Channel state indexing
Contract indexing
SAT20 Wallet WASM / PWA Adapter API
SAT20 Wallet protects private keys, mnemonic phrases, signatures, asset sends, user authorization, PWA wallet state, and STP adapter calls. AI Agents interact through a PWA adapter or another controlled adapter.
Go WASM entry
Wallet core management
Wallet base interfaces
Asset sending
PSBT / signing
Contract client interfaces
STP / channel wallet capabilities
PWA WASM wrappers
PWA Agent adapter
PWA DApp Connect types
PWA DApp bridge
Authorization UI and state
STP Agent Adapter API
The STP Agent Adapter is a language-agnostic JSON contract for AI Agents. It defines how an Agent requests wallet operations, reads safety evidence, and recovers from unknown network results.
The English explanation pages live under SAT20 Agent Wallet. The canonical installable skill and reference files live in sat20-labs/docs. docs-en links to that source and does not copy a separate skill tree.
Skill entrypoint
Adapter contract
Operation playbooks
PWA WASM adapter reference
Adapter forwarding script
Documentation Evolution
Current API documentation uses this source map. After stable public interfaces emerge, the docs can add:
Request and response examples for Public Stable APIs.
Standard error codes and state machines.
OpenAPI / Swagger only for stable public APIs.
Multi-language SDKs or client generators.
Explorer / indexer URL schemas that Agents can verify.
Last updated