Purpose
bolthub-sdk is the source code repository for bolthub's published SDK packages. bolthub is positioned as a payment layer for commercial transactions between agents and tools: developers can charge agents per call for their own MCP tools and APIs, with funds settled directly to the developer's own wallet via the Bitcoin Lightning Network (L402), and bolthub itself is not in the path of fund flow.
This repository is the open-source side of this payment system, containing the tool payment SDK, payment client, MCP server, command-line tool (CLI), and provenance verification middleware.
Main Capabilities and Package Structure
The repository covers all publicly released bolthub.ai packages: the npm @bolthub/* scope, and the PyPI bolthub / bolthub-verify packages.
- packages/shared is an internal package and is never published; it appears in this repository because @bolthub/mcp bundles it.
- Merge notes (2026-07): @bolthub/agent has been merged into @bolthub/pay (≥0.4.0); @bolthub/mcp-registry and @bolthub/mcp-bridge have been merged into @bolthub/mcp. The old names are deprecated on npm and point here.
Relationship with the bolthub Platform
The bolthub platform (gateway, API, web app) is located in a private monorepo. The above SDK packages are developed there and synchronized to this repository; this repository is the release source: releases are tagged here, built and published by CI, with npm provenance, so what is on npm is verifiably built from this public source code.
Usage
- Each TypeScript package is built under its directory via
bun run buildbuild; @bolthub/pay must be built before the packages that bundle it. - The published dist/ artifacts are built by Bun from this source, with source maps containing embedded source, so the tarball itself is readable.
- For the trust model (which parts touch wallet credentials and which do not) and how to report vulnerabilities, see SECURITY.md.
Applicable Scenarios
Suitable for developers who want to charge per call for MCP tools or APIs and receive payments directly to their wallet via the Lightning Network, as well as integration scenarios that require a payment client, MCP server, CLI, or provenance verification middleware.
Limitations and Notes
- This repository is a generated mirror: PRs will not be merged directly. Accepted changes are first applied to the monorepo (with contributor attribution), then synchronized out with the next release. Please read CONTRIBUTING.md before submitting a PR.
- The repository welcomes issues and PRs, but the merge process is as described above.
- Specific information such as fees, pricing, and the scope of platform support is not provided in the materials.