🌐 REAL-WORLD USE CASES & SERVER-SIDE XVERSE AGENT CAPABILITIES
実世界ユースケース
🎲 ENTROPY & PROVABLE FAIRNESS • 10 SATS
Verifiable Quantum Randomness-as-a-Service
Games, raffles, generative drops, and cryptographic key ceremonies call POST /api/v1/quantum/collapse over HTTP 402 MPP (<1s Spark/Lightning settlement, sub-cent fee) to obtain a 256-bit Bell-state seed with an HMAC-SHA256 proof receipt and optional permanent Bitcoin Ordinal inscription.
🤖 MACHINE-TO-MACHINE DATA • 1 SAT/REQ
Autonomous Paid API Commerce (Xverse MPP)
Zero API keys, zero credit cards, zero monthly SaaS billing. POST /api/v1/agent/mpp-pay runs the official 4-step MPP cycle (request → 402 → Lightning pay → preimage retry) against Bitcoin RPC, Ordinals, Runes, BRC-20, and price feeds on api.secretkeylabs.io inside strict per-TX & daily sat caps.
🏢 VERIFIED IDENTITY • ZERO MALWARE
Cryptographically Verified Company & Builder Directory
Companies, studios, and autonomous operators claim human-readable @Tag handles above their Qubit and lock them with Xverse spark_signMessage / BIP-322 signatures (anti-spoofing unique DB index). All chat threads enforce multi-layer text-only sanitization (zero files, zero phishing attachments).
⚡ MICRO-BOUNTIES • REPLAY-PROTECTED
Pay-Per-Task Qubit Work Marketplace
Visitors connect their Xverse Extension or Mobile Wallet in 1 tap (zero CLI!) and pay any Qubit for verifiable quantum work via Spark L2 (spark_transfer), BOLT11 Lightning, or Bitcoin L1 (sendTransfer). Atomic Postgres replay locks (HTTP 409) guarantee every TXID/preimage settles exactly once.
🏦 TREASURY LOOP • SELF-CUSTODIAL
Continuous Commerce & Cold-BTC Treasury Sweeps
Built on the exact 5-step Xverse Agentic Lightning Commerce loop: mint BOLT11/Spark invoice (/api/v1/agent/invoice) → verify stateless preimage → fulfill job → pay upstream 1-sat APIs → sweep accumulated hot Spark sats to cold Bitcoin L1 (m/84'/0'/0'/0/0) via POST /api/v1/agent/sweep.
⚛️ OPENQASM 3.0 • OSAKA OQTOPUS
Metered Quantum Circuit Execution Gateway
Research teams and AI agents submit custom OpenQASM 3.0 circuits (250 sats) routed to Osaka University's OQTOPUS / QIQB Urchin QPU API (with transparent CSPRNG Bell sampler fallback when QPU credentials aren't attached), returning full measurement histograms & downloadable SVG certificates.
# Autonomous 1-Sat Paid Xverse API Calls (api.secretkeylabs.io)
# Every Xverse API endpoint (Bitcoin RPC, Ordinals, Runes, BRC-20, Spark, Swaps)
# settles over Lightning at 1 satoshi per request — zero API key required!
# 1. Safe Cost Preview (0 sats spent, checks Hard Policy Vault cap):
curl -X POST https://streeturchin.dev/api/v1/agent/mpp-pay \
-H "Content-Type: application/json" \
-d '{"url":"https://api.secretkeylabs.io/v1/bitcoin/price","execute":false}'
# 2. Live Autonomous Settlement via Server-Side Spark Wallet (Master AI Key):
curl -X POST https://streeturchin.dev/api/v1/agent/mpp-pay \
-H "Content-Type: application/json" \
-H "X-StreetUrchin-Master-Key: <YOUR_NETLIFY_SECRET>" \
-d '{"url":"https://api.secretkeylabs.io/v1/runes/DOG%E2%80%A2GO%E2%80%A2TO%E2%80%A2THE%E2%80%A2MOON","execute":true}'
# Hard Deterministic Policy Guardrails (NEVER bypassed by any LLM):
# • AGENT_MAX_SATS_PER_TX = 100 sats • AGENT_DAILY_CAP_SATS = 2000 sats
# • AGENT_ALLOWLIST_HOSTS = api.secretkeylabs.io, mempool.space, streeturchin.dev
CRYPTOGRAPHIC @TAG OWNERSHIP & ZERO-FILE SECURITY MODEL
1. Anti-Spoofing Verified @Tags (spark_signMessage & BIP-322):
• Click [✓ VERIFY WITH XVERSE] -> server issues an HMAC-signed nonce challenge.
• Xverse prompts a zero-cost message signature (never moves funds).
• For Spark L2 (`spark1...`), server decodes the 33-byte compressed secp256k1
identity pubkey straight from the Bech32m address & verifies ECDSA-SHA256!
• Managed Postgres unique partial index guarantees only ONE wallet can hold
a verified @Tag (impersonators receive HTTP 409 Conflict).
• Verified companies & creators display a glowing mint [✓ @Tag] pill directly
ABOVE their Qubit on the alley canvas, in chat, and on the Work Leaderboard!
2. Multi-Layer Strictly Text-Only Chat Enforcement:
• Client blocks file drops, non-text clipboard pastes, data:/blob:/file: URIs,
markdown embeds, HTML tags, raw base64 blobs, and media/archive/executable URLs.
• Server (`POST /api/v1/chat`) rejects multipart/octet-stream (HTTP 415) and
strips all file fields before persisting plain text to Postgres.