use.bsv.tools

A builder entry point for internet-native value.

Build apps where users bring identity, money, private data, and proof.

BSV tools are worth learning when they let a developer ship something the normal web makes awkward: charge for useful work at the moment of use, keep user data portable, and prove who created or approved an action.

Run the starter Tell us what blocks you
Wallet as account Pay per API call User-owned memory Signed proof
Developer workbench showing BSV payment, private memory, and proof modules connected to an AI coding surface.

Why BSV

Make value a feature, not a billing project.

Most developer platforms start with accounts, dashboards, API keys, invoices, and a pile of user data the app has to custody. BSV flips the starting point: the wallet can carry identity, permissions, payment ability, private records, and signatures into the app.

01

Charge for work as it happens

Paid API calls, AI runs, file unlocks, and premium actions can settle at tiny values without forcing a subscription gate before the user gets value.

02

Let users own the state

Encrypted records and wallet-mediated permissions let a useful app remember things without turning every profile into another app-owned silo.

03

Prove creation and consent

Signatures and durable hashes make authorship, licensing, approval, audit trails, and AI artifact provenance visible outside one vendor database.

04

Compose with agents

In 2026, the fastest developer path is an agent starting from a tested slice. This site gives the agent a working base and a narrow BSV payoff to preserve.

Start here

Run one maintained starter before touching the deeper docs.

git clone https://github.com/p2ppsr/use.bsv.tools.git && cd use.bsv.tools/starter && npm install && npm test && npm run preflight && npm run dev

Verified path

What the starter proves on a clean machine.

It gives a working no-spend milestone and runs a real BRC-100 wallet readiness loop. A new builder should see product value first, then know exactly whether their local wallet is ready for a live mainnet flow.

Wallet preflightPorts, Origin headers, app ownership, auth, network, and conflict guidance.
Real wallet loopDerived key, encrypt/decrypt, sign/verify, and identity-key readiness.
Paid APIHTTP 402 challenge, mock payment retry, server receipt.
Private MemoryCreate, list, decrypt, and delete encrypted records.
Creation ProofHash metadata, sign proof, verify signature.
CI loopback gateStrict BRC-100 loopback wallet powered by @bsv/sdk ProtoWallet.

After the starter

Pick the payoff you want a new developer to feel.

The first project should not be a toy counter. It should prove that BSV can make software earn, remember, or verify something useful with less platform ceremony.

01 10 min target

Paid AI API

Upgrade the starter's HTTP 402 mock into real AuthFetch/payment middleware once wallet preflight is clean.

  • Wallet auth instead of signup
  • Payment before expensive work
  • Visible revenue in the flow
02 12 min target

Private AI Memory

Move from the starter's local encryption into wallet-owned records with create/list/read/delete states intact.

  • Encrypted app records
  • Portable user identity
  • No app-owned profile silo
03 15 min target

Creation Proof

Replace the starter's browser proof with wallet-backed signature, storage, and a shareable proof page.

  • Signed provenance
  • Shareable proof page
  • License or unlock payment

AI-native

Copy a prompt that starts from the runnable starter.

New developers should not spend their first hour reconciling ports, package warnings, and unfinished snippets. Start from the tested starter, then ask an agent to upgrade one path while preserving the BSV value proposition.

Paid AI API prompt 

        

      


      

        

          
Use the tools

          
The minimum kit a builder should touch first.

        

        

          
            01
            Run starter
            Clone, preflight, dev server, first visible win.
          
          
            02
            Wallet auth
            Reference docs after local wallet preflight passes.
          
          
            03
            Payments
            Upgrade from mock receipt to low-value mainnet flow.
          
          
            04
            Private data
            Keep the starter's visible states while swapping APIs.