Tachyon Now Supports Nanopayments via x402

Tachyon is now accessible through Nanopayments powered by Circle Gateway.

Until now, using Tachyon required a Rath account and an API key issued by our team. With this integration, users with a funded Circle Gateway balance can call Tachyon's x402-protected API, pay the relay cost in USDC, and submit a gasless blockchain transaction.

No Rath account. No API key. Just pay and use.

Read the complete Tachyon and Nanopayments guide

Fast, gasless transaction execution

Tachyon is Rath's blazing-fast transaction relayer for gasless execution across multiple chains. It is built for latency-sensitive systems and is already used by MEV searchers, liquidation bots, keepers, wallets, and applications that need transactions to land quickly and reliably.

Tachyon abstracts the operational complexity behind blockchain execution, including destination-chain gas, nonce management, retries, RPC reliability, and transaction status. Developers send a transaction through one interface, while Tachyon handles the execution lifecycle. The experience remains the same with Nanopayments. The difference is how access and relay costs are handled: instead of receiving an account and API key from Rath, the caller pays programmatically with USDC.

What is Nanopayments?

Circle Gateway gives users a unified USDC balance that can be used across supported blockchain networks. After depositing USDC into the Gateway Wallet contract, applications can query that balance and authorize payments through the Gateway SDK.

Nanopayments powered by Circle Gateway make very small, high-frequency USDC payments practical. Each payment is authorized with an offchain signature, while Nanopayments combines many authorizations into fewer onchain settlement transactions.

This means a bot, application, or AI agent does not need to broadcast a separate USDC transaction for every Tachyon API request.

The initial Gateway deposit is an onchain transaction and requires gas. After that deposit, individual payment authorizations are gasless for the buyer.

How x402 payments work with Tachyon

x402 is an open payment protocol built around the HTTP 402 Payment Required status code. It allows software to pay for an API at the moment it is used, without an account, subscription, checkout page, or manually provisioned API key.

The Tachyon payment flow is simple:

1. Fund a Circle Gateway balance with USDC.
2. Call Tachyon's x402-protected transaction relay endpoint.
3. Tachyon returns the payment requirements for the relay.
4. The Circle Gateway client signs a USDC payment authorization offchain.
5. The client retries the request with the payment proof.
6. Tachyon pays the destination-chain gas and submits the transaction.
7. Circle Gateway settles accumulated payment authorizations in batches.

The Gateway payment authorization is gasless for the buyer, but the destination blockchain transaction still consumes gas. Tachyon pays for that execution and charges the corresponding relay cost through x402.

Using the batch settlement, payment negotiation and submission happen in one call:

const result = await client.pay<SubmitTxResponse>(
  "https://tachyon.rath.fi/api/submit-tx",
  {
    method: "POST",
    body: tx,
  }
);

GatewayClient.pay() handles the 402 Payment Required response, signs the payment authorization, retries the request, and returns the Tachyon API response.

For dependencies, Gateway funding, transaction construction, and a complete TypeScript walkthrough, follow the Tachyon Nano payments and x402 documentation.

You can also use the runnable nano-payment.ts example on GitHub.

Infrastructure that software can consume directly

Accounts and API keys were designed for infrastructure purchased and operated by people. They add onboarding, credential provisioning, secret management, and billing systems before a developer can make the first useful request.

x402 replaces that process with a payment-native interface. If software can authorize the required payment, it can consume the service.

For Tachyon users, that unlocks:

• Instant access: start using the transaction relay without waiting for account approval or API key provisioning.
• USDC payments: pay relay costs from a Circle Gateway balance instead of managing a separate billing relationship.
• Gasless requests: authorize each post-deposit payment offchain without sending a payment transaction for every API call.
• Usage-based pricing: pay when the API is used rather than committing to a subscription.
• Machine-to-machine execution: let bots and agents purchase blockchain execution programmatically.

Infrastructure should be consumed, not requested.

Built for bots, applications, and AI agents

Tachyon already powers workloads where speed and reliability matter: MEV strategies, liquidations, market making, keeper networks, wallets, and high-frequency applications.

Nanopayments open the same execution infrastructure to any program capable of making an x402 payment. A liquidation bot can pay for execution as an opportunity appears. A keeper can fund its own relay requests. An AI agent can purchase transaction execution without a human creating an account or entering payment details.

This is a small step toward a larger shift:

Agents paying for execution.

Bots paying for infrastructure.

Software consuming services directly.

The machine economy will not run on dashboards and manually issued API keys. It will run on programmable payments.

Start using Tachyon with x402

To submit a Tachyon transaction with Nanopayments, you need an EVM wallet, USDC and native gas for the initial Gateway deposit, and the x402 batching client.

• Read the Tachyon Nanopayments guide
• Run the TypeScript Nanopayments example
• Explore the Tachyon transaction relay API
• Learn about Circle Gateway

Rath x Nanopayments is live.