Blockmachine Integrates x402 To Automate Blockchain RPC Payments For AI Agents

Blockmachine (SN19) has added full x402 support to its RPC (Remote Procedure Call) infrastructure, letting AI agents self-provision access to blockchain endpoints by paying in $USDC, $TAO, or $SN19 directly on-chain.

The x402 protocol revives the long-forgotten HTTP (Hypertext Transfer Protocol) 402 “Payment Required” status code and turns it into a machine-native standard for on-chain payments, removing every step of the human-operated billing flow.

The payment loop completes autonomously in under a minute from a cold start, and the minimum purchase of $5 credits 500,000 Request Units against a single API key that works across all supported chains.

Bittensor RPC is live today with 215+ supported methods, Ethereum RPC ships with Helios-backed consensus-verified endpoints for trustless reads, and BNB Smart Chain (BSC) is landing next.

What x402 Changes For Agents

The protocol turns a dormant HTTP status code into a machine-native payment standard, which is exactly what agent-first infrastructure has been missing.

1. x402 revives HTTP 402 ‘Payment Required.’ An open payment protocol that turns the long-unused status code into a live path for on-chain payments.

2. No human-operated billing flows. Autonomous software agents (AI or otherwise) pay for services programmatically, with no intermediary sitting between the wallet and the endpoint.

3. Agents self-provision their own access. An agent that needs Ethereum RPC calls or Bittensor chain data can acquire that access itself, spending crypto it already holds in its wallet.

4. No signup, no email, no credit card. A Blockmachine API key becomes something an agent can buy itself in four lines of code.

How The Payment Loop Runs

The payment flow is designed to be completed autonomously in under a minute from a cold start. The full loop:

1. Agent requests a live-priced quote from the Blockmachine x402 endpoint.

2. Signs a brief authentication message with its Bittensor wallet to bind the key to its address.

3. Pays the quoted amount on-chain in $USDC, $TAO, or $SN19.

4. Submits the transaction hash as proof.

5. Blockmachine (SN19) verifies payment against the finalised chain and returns a live API key with the purchased Request Unit credit.

The three payment assets accepted:

1. $USDC: The most widely held stablecoin and the natural choice for agents operating across multiple chains.

2. $TAO: Bittensor’s native token, priced live from the current $TAO/$USD rate at the moment of the quote.

3. $SN19: For agents already participating in Bittensor’s dynamic TAO economy, $SN19 can be used to pay directly with no un-staking step required.

The $SN19 option closes a structural loop the ecosystem has needed for months. Blockmachine runs on SN19, node runners earn $SN19 for operating the infrastructure, and agents can now pay in $SN19 those runners are already earning. The infrastructure funds itself from within the ecosystem it serves.

What’s Live On The RPC Layer

Once an agent has its API key, it hits an RPC layer that has been expanding quickly across the past quarter.

1. Bittensor RPC is live. 215+ supported methods over HTTP and WebSocket, with standard Bittensor tooling working unmodified. Miners and validators can use Blockmachine as a drop-in replacement for their current endpoint.

2. Ethereum RPC is live. Full JSON-RPC support including a consensus-verified endpoint backed by Helios proofs, giving agents trustless reads without depending on a single trusted operator.

3. BNB Smart Chain (BSC) is next. Further networks follow after that, with the goal being a single API key that gives agents reliable metered access to every major chain under one RU (Request Unit) budget and one status endpoint.

4. One key across every chain. A single Blockmachine API key already authenticates across all currently supported chains and draws from one shared RU budget. Agents can check remaining credit through the key itself with no dashboard login required.

Human operators are not locked out either. The dashboard supports card and $USDC invoice payments with subscription plans starting at $9 per month for higher rate limits, so the same infrastructure serves both agent-native and traditional developer workflows.

The Loop That Funds Itself

The implication of the x402 launch is that Blockmachine has closed the last operational gap between an autonomous agent and the blockchain data it needs to function. Ethereum and Bittensor RPC are both live, BSC is next, and the payment loop resolves in under a minute from a wallet the agent already controls.

The $SN19 payment option makes this more than a distribution feature, since it means node runners get paid in the token agents earn and spend inside the same subnet. For a Bittensor subnet whose product is decentralized blockchain infrastructure, this is the moment the incentive layer stops being theoretical and starts being circular.

➛ Read More on Blockmachine’s x402 Payment Spec. Here