Agent Payments Watch / Applications
In Brief
BSVKey’s open-source Inference MCP has been listed in the official Model Context Protocol Registry, providing AI agents with access to Claude and Grok inference through a hosted gateway that meters usage and settles payment in BSV. The service supports both prepaid channels and a per-request HTTP 402 mode in which an agent can fund and sign its own BSV payment. The project is independent of the still-open proposal to add BSV support to the x402 Foundation’s upstream implementation. (MCP Registry)
News Report
A new Model Context Protocol service is giving AI agents a way to purchase model inference by usage while settling the corresponding payment in BSV.
BSVKey’s inference-mcp now appears in the official MCP Registry, where version 1.2.1 was listed as updated on September 7. The registry describes the service as providing pay-per-token Claude and Grok inference through the hosted inference.bsvkey.com gateway. (MCP Registry)
Model Context Protocol, or MCP, provides a common interface through which AI applications and agents can discover and invoke external tools and services.
BSVKey applies that model to something agents increasingly need directly: access to another AI model as a paid service.
Rather than requiring the user to manually open a model-provider interface for every task, an MCP-compatible agent can call the BSVKey service as a tool, request inference and account for the usage through a BSV-funded payment mechanism.
The open-source MCP server exposes five principal tools:
list_models, infer, channel_balance, open_channel, and x402_infer.
The software is described as a thin HTTP client. It does not run Claude or Grok itself and says it does not hold the user’s payment keys. Instead, inference requests pass through BSVKey’s hosted gateway, which provides access to the underlying models and meters the calls. (Luca’s Proxy)
This distinction matters.
The project is not an announcement of a partnership with Anthropic or xAI, nor does it represent a new model trained on BSV Blockchain. Its contribution is the payment and agent-access layer around existing model inference.
Two Payment Paths
BSVKey provides two different payment models.
The first uses a prepaid channel.
A user funds a channel through the BSVKey gateway, either using a BRC-100 wallet or by loading a key into the interface. The resulting channel credentials can then be supplied to the MCP server. As the agent makes inference calls, its usage is drawn down from that funded balance on a per-token basis. (Luca’s Proxy)
This avoids constructing a new blockchain payment for every individual token while still allowing the service to meter relatively small units of model usage.
The second option is more directly machine-to-machine.
Through the x402_infer tool, the agent can respond to an HTTP 402 Payment Required request by constructing a BSV payment for that particular call. No prepaid channel is required.
For this mode, the agent holds its own funded BSV private key and uses BSVKey’s x402-bsv-client together with the BSV SDK to create the payment. The project describes the sequence as requesting the resource, receiving a quoted price, signing the corresponding BSV transaction, resubmitting the request with the payment evidence and receiving the result after settlement. (Luca’s Proxy)
That creates a different interaction model from a conventional API subscription.
An autonomous process can encounter a paid service, learn its requested price, pay for one call and receive the result without first requiring a conventional recurring account relationship.
Designed for Existing Agent Environments
The package is published as @bsvkey/inference-mcp and can be connected to environments including Claude Code as well as other MCP-compatible hosts.
Its configuration can point either to BSVKey’s hosted gateway or to another deployment using the same interface. The repository also includes a portable SKILL.md alongside the MCP server implementation. (Luca’s Proxy)
This gives the project two layers.
At the user-facing level, the hosted gateway provides the actual inference service.
At the integration level, the MCP package gives agents a standardized way to discover and call that service.
The official MCP Registry listing is relevant because it places that integration inside the wider MCP discovery ecosystem rather than leaving it solely as a BSV-specific GitHub project. The registry currently identifies the service directly by its package namespace, io.github.BSVKey/inference-mcp, and describes its BSV-settled usage model. (MCP Registry)
The x402 Distinction
BSVKey’s use of the term x402 should not be confused with upstream acceptance of BSV into the x402 Foundation repository.
BSV Association has separately submitted Pull Request #2890 to add a BSV exact payment scheme to the x402 Foundation implementation. That proposal includes a TypeScript client, server and facilitator, BRC-29 payment handling, BRC-42-derived destinations and more than 100 reported tests.
As of the September 8 check, however, PR #2890 remains open and has not been merged into the foundation’s main branch. (GitHub)
BSVKey therefore provides its own BSV payment builder for the per-call path rather than depending on that upstream proposal having been accepted.
That distinction is useful because it demonstrates that experimentation around HTTP 402 machine payments can continue at the application layer while formal interoperability work proceeds separately.
BSV TIMES Read
The interesting part of this development is not simply that someone can pay for AI with BSV.
The more important shift is who can make the purchasing decision.
Traditional API access is built largely around human-created accounts, subscriptions, stored payment methods and billing relationships. An autonomous agent can use those APIs, but the commercial relationship was usually established beforehand by a person.
BSVKey is experimenting with a more direct model.
An agent can discover a service through a standard machine interface, request a unit of computation and pay for that particular use through a payment mechanism the software itself can execute.
The prepaid-channel model makes very small, repeated usage practical. The per-call HTTP 402 model goes further by allowing each request to become an independently priced interaction.
Neither mechanism proves that this will become the dominant way AI services are purchased, and the present implementation still relies on BSVKey’s hosted inference gateway. But it demonstrates something concrete: BSV payment can be placed inside an ordinary agent tool interface rather than requiring the agent’s user to leave the workflow and operate a separate payment application.
That is the infrastructure direction worth watching.
If AI agents increasingly consume models, datasets, APIs and other machine services on demand, payments become less useful when they require human interruption. A network capable of settling small transactions cheaply gives developers another way to make the payment itself part of the software interaction.
The official MCP Registry listing gives this experiment a useful external interface: an MCP host can encounter it as an agent service first, while BSV operates underneath as the settlement mechanism.
Source Links
Official MCP Registry — BSVKey Inference MCP
x402 Foundation — BSV Exact Scheme PR #2890
Posted on September 8, 2026
Leave a comment