BSVKey's Inference MCP Lands in the Official Registry
The window's real news is BSVKey's pay-per-call inference listing going live in the standard MCP directory, alongside a run of small but concrete app updates from Janus, Zoide, Sovereign Receiver, and others.
-
01
BSVKey's inference MCP was added to the official Model Context Protocol registry, exposing pay-per-call Claude and Grok inference settled in BSV to any MCP-aware AI agent.
-
02
Janus launched a wallet-neutral cross-chain swap in beta, moving BSV to and from SOL, HYPE, BELLS and others in seconds without account signup.
One-time unlock for this issue, paid directly from your BRC-100 wallet.
Prefer to pay by address or QR?
For developers
X Read settles through ChainTap's BRC-100 micropayment flow (BRC-29 key derivation, per session). The "Unlock with Wallet" button above does this for you via @bsv/sdk's WalletClient. Testing a different BRC-100 wallet by hand? Here's the raw endpoint:
{ "beefHex": "0100beef...", "identityKey": "02...", "readerTag": "02..." }
identityKey is your wallet's getPublicKey({ identityKey: true }) result — required for genuine BRC-29 derivation (it's the counterparty used to derive the payment address). It's used once, in memory, to verify this one payment, then discarded — we don't store it. readerTag (optional) is a separate, ChainTap-scoped key — getPublicKey({ protocolID: [1, 'chaintap reader id'], keyID: '1', counterparty: <our identity key> }) — and that's what's stamped into the delivered report as a watermark and kept on file, so a leaked copy traces back to your wallet without also revealing your real identity key or which other BRC-100 apps you use. Omit it and you still get access, just without watermark privacy.
Already paid?
If you already paid but lost your access link, enter the transaction ID from your wallet.
X Read is synthesized by AI (Claude) from real X/Twitter posts, sourced via John Calhoun's x-research, using a research and editing process I designed and run every three days. I write the prompts and review the output; the pipeline itself is automated. Ask me about it — @hbgnostic on X, or bridget@doranconsultingllc.com.