Bots with bearer assets: an SDK for autonomous agent commerce

What it does

Sphere SDK is a TypeScript client for the Unicity network that equips autonomous agents with identities, wallets, and peer-to-peer commerce primitives. It lets an agent claim a human-readable @nametag, send and receive bearer tokens, request payments, issue invoices, swap assets atomically, and message counterparties over Nostr — all without relying on a global ledger update for every interaction. The same API runs in browsers, Node.js, and on the command line.

The interesting bit

Unicity treats assets as self-contained bearer objects that carry their own cryptographic history and validity proofs, so value moves directly between two parties rather than through a broadcast mempool. Sphere wraps that substrate into agent-level concerns like discovery, negotiation, and settlement — essentially giving bots the same financial autonomy a person has with cash and a phone.

Key highlights

• Identity module issues @nametag handles backed by secp256k1 keypairs, with HD multi-address support
• Payments, invoicing, and atomic swaps operate over bearer tokens that the project claims bypass gas auctions and mempool broadcasts
• Discovery and market intent posting let agents find counterparties without a central directory
• Communications layer uses Nostr relays for encrypted direct messages (NIP-04) and group chat (NIP-29)
• Token state can sync to IPFS/IPNS, and a Connect module supports browser-extension wallet integration

Caveats

• Browser builds may need Buffer/process polyfills, and Node.js requires the ws package explicitly
• Receiving payments via a @nametag requires an on-chain Unicity ID mint, which adds a separate setup step
• The SDK is purpose-built for the Unicity network and its ALPHA base-chain coin, so it will not translate directly to EVM chains

Verdict

Worth a look if you are building bots or dApps that need programmable identity, messaging, and settlement in one TypeScript API — provided you are comfortable betting on the Unicity stack. If you need EVM compatibility or a fully abstracted multi-chain toolkit, this is not your layer.