SUBTC Protocol — The Philosophy of curl-first Financial Sovereignty

permalink SUBTC
#aiagent#btc#golang#sovereignty

​The Core Philosophy
In an era dominated by heavy SDKs, bloated dashboards, and restrictive third-party platforms, SUBTC Protocol emerges as a return to the fundamentals of the web. Our philosophy is simple: Financial infrastructure should be as accessible and transparent as a raw HTTP request.
​By adopting a curl-first approach, we eliminate the "black box" of traditional payment gateways. Whether you are a human developer in a terminal or an AI Agent navigating a headless server, the interface remains identical. Raw, stateless, and predictable.
​Why curl?
​Zero Dependencies: No libraries to install, no version conflicts to manage. If your environment has curl, you have a global payment gateway.
​AI Agent Native: Autonomous agents don’t need UI/UX; they need precise API contracts. SUBTC provides the perfect "instruction set" for agents to manage wallets and execute on-chain transactions autonomously.
​Auditability: Every transaction logic is visible in the command line. You see exactly what you send, from headers to JSON payloads.
​The SUBTC Implementation
The protocol, built entirely in Go for maximum performance and 100/100 Lighthouse efficiency, treats Bitcoin not just as an asset, but as a programmable transport layer.
​Example: The Atomic Workflow
Creating a wallet and checking its status is a matter of two simple commands:

# Create a sovereign wallet
RESP=$(curl -sS -X POST "https://api.subtc.net/v1/btc?mode=wallet_create" \
  -H "X-SUBTC-KEY: $KEY" \
  -H "Content-Type: application/json" \
  -d '{"net":"main"}')
WID=$(echo "$RESP" | sed -n 's/.*"wallet_id":"\([^"]*\)".*/\1/p')
echo "WID=$WID"
# Verify balance in Satoshis (SAT)
curl -sS -X POST "https://api.subtc.net/v1/btc?mode=wallet_balance" \
  -H "X-SUBTC-KEY: $KEY" \
  -H "Content-Type: application/json" \
  -d "{\"wallet_id\":\"$WID\"}"

Beyond Human Interfaces
SUBTC is built for the Sovereign AI era. By removing the friction of traditional banking and the overhead of complex virtualization, we provide a "Financial OS" that fits into a single binary.
​The goal isn't just to process payments—it's to ensure that the code you write today remains functional, sovereign, and independent of any third-party gatekeeper.