Tempo RPC Endpoint

Flat-rate Tempo RPC provider and Tempo RPC node access: free tier, no KYC, HTTP & WebSocket. Tempo mainnet chain ID 4217.

Tempo is an EVM-compatible Layer 1 designed around stablecoin payments. It has no native volatile token — fees are paid in USD-denominated stablecoins, chosen per transaction or per account.

About Tempo

Tempo was announced in September 2025 by Stripe and Paradigm and reached mainnet in March 2026. It runs its own consensus rather than settling as an Ethereum layer 2, and targets merchant-scale payment workloads: a dedicated payment lane, memo fields on its TIP-20 token standard for invoice references, and sub-cent transfer costs.

Fee handling is the unusual part. A built-in fee AMM converts whichever supported stablecoin the sender holds into each validator's preferred stablecoin at a fixed rate, and if an account sets no preference, fees are simply taken in the same token being transferred. For RPC consumers the interface is standard eth_* against chain ID 4217.

Common Use Cases on Tempo

• Merchant payments
• Payouts and reconciliation
• Stablecoin transfers
• Programmable money movement

Tempo Mainnet RPC URL (HTTP)

Tempo WebSocket RPC URL

Quick Start: Connect to Tempo

cURL

curl -X POST https://rpc.swiftnodes.io/rpc/tempo?key=YOUR_API_KEY \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","method":"eth_blockNumber","params":[],"id":1}'

ethers.js

import { JsonRpcProvider } from "ethers";

const provider = new JsonRpcProvider(
  "https://rpc.swiftnodes.io/rpc/tempo?key=YOUR_API_KEY"
);

const blockNumber = await provider.getBlockNumber();
console.log("Tempo block:", blockNumber);

viem

import { createPublicClient, http } from "viem";

const client = createPublicClient({
  transport: http("https://rpc.swiftnodes.io/rpc/tempo?key=YOUR_API_KEY"),
});

const blockNumber = await client.getBlockNumber();

web3.py

from web3 import Web3

w3 = Web3(Web3.HTTPProvider("https://rpc.swiftnodes.io/rpc/tempo?key=YOUR_API_KEY"))
print("Tempo block:", w3.eth.block_number)

Add Tempo to MetaMask

Features of SwiftNodes for Tempo

• Load-balanced across multiple upstream nodes wherever a chain has more than one, with automatic failover
• Health-checked every 2 minutes with automatic failover
• Free tier available — no credit card or KYC required
• Flat-rate monthly pricing with no per-request fees
• HTTP and WebSocket support
• One API key works across all 75+ supported chains, including Tempo

Rate Limits

Tempo RPC methods

Measured weekly through this endpoint: what each method returns on Tempo, its limits, and an example request.

• eth_blockNumbersupported
• eth_chainIdsupported
• eth_getBalancesupported
• eth_getBlockByNumbersupported
• eth_getTransactionByHashsupported
• eth_getTransactionReceiptsupported
• eth_callsupported
• eth_estimateGassupported
• eth_gasPricesupported
• eth_maxPriorityFeePerGassupported
• eth_sendRawTransactionsupported
• eth_getTransactionCountsupported
• eth_getCodesupported
• eth_subscribesupported
• eth_getLogssupported
• eth_getBlockReceiptssupported
• eth_feeHistorysupported
• eth_getProofsupported
• eth_createAccessListsupported
• debug_traceCallsupported
• trace_blocksupported
• trace_transactionnot measured

Related EVM chains

Explore RPC endpoints for other EVM networks on SwiftNodes: