Katana RPC — Free Endpoint & Developer Guide

Katana is a DeFi-focused EVM network. This guide shows how to connect to a free Katana RPC endpoint on MoltNode — no API key and no signup required.

What is Katana

Katana is a DeFi-focused, EVM-compatible network. Because it follows the EVM standard, it works with the same Solidity contracts, Ethereum-style addresses, and developer tooling used across the rest of the ecosystem — so for builders coming from Ethereum or any layer-2, the workflow is immediately familiar.

For developers, the interface is the standard one: Katana exposes the eth_* JSON-RPC method set and accepts ordinary Ethereum-style accounts and signatures. Its native gas token uses the symbol ETH, and the network is identified by chain ID 747474. The quickest way to get a feel for Katana is to point a JSON-RPC client at a live endpoint and read from the chain directly.

Katana RPC endpoint on MoltNode

MoltNode gives Katana one clean URL that is also a working RPC endpoint:

https://moltnode.ag/katana

No API key is required and there is no signup. The endpoint speaks JSON-RPC 2.0 over HTTP POST, and CORS is open so browser apps can call it directly without a proxy. The URL has dual behavior: a GET opened in a browser renders a human-readable page about the chain, while a POST carrying a JSON-RPC body returns a machine response. One address serves both people and programs.

To use the free Katana RPC in a wallet, add a custom network with the RPC URL https://moltnode.ag/katana, chain ID 747474, and currency symbol ETH.

Probe it with curl

To verify the Katana JSON-RPC endpoint is live, ask for the latest block number:

curl -s https://moltnode.ag/katana \
  -X POST \
  -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"eth_blockNumber","params":[]}'

The response is a JSON object with the current block height, hex-encoded, in result. Swap the method for any standard eth_* call — eth_chainId, eth_getBalance, eth_getTransactionReceipt — to read whatever your application needs from the Katana node.

Use it from your app

Any JSON-RPC client connects to the Katana RPC endpoint. Here is a minimal viem example pointed at the URL:

import { createPublicClient, http } from "viem";

const client = createPublicClient({
  transport: http("https://moltnode.ag/katana"),
});

const blockNumber = await client.getBlockNumber();
console.log("Katana block:", blockNumber);

The same URL drops into ethers, web3.py, wagmi, or any library that accepts an HTTP RPC URL — no special configuration beyond the endpoint itself.

Reliability & failover

Behind the single moltnode.ag/katana URL is MoltNode's upstream routing layer, designed for automatic failover. If an upstream provider is unavailable or returns an error, requests are routed to the next available source so your application keeps reading and writing. The upstream API keys stay server-side and are never exposed to your client, so you get reliable Katana node access without managing any credentials yourself.

There is no hard rate limit, but this is a shared, free resource. Please use it responsibly: cache results where practical, avoid tight polling loops, and for heavy production traffic, treat MoltNode as a fast default and a failover layer rather than your only dependency.

For humans and agents

The dual GET/POST behavior makes the endpoint useful to developers and automated tools alike. You can open https://moltnode.ag/katana in a browser to read about the chain, while a script or wallet POSTs JSON-RPC to the same URL.

For automated discovery, MoltNode publishes a machine-readable catalog of every supported chain at https://moltnode.ag/api/chains and an agent-oriented summary at https://moltnode.ag/llms.txt. An AI agent can fetch the catalog, locate the Katana entry and its endpoint, and start issuing eth_* calls with no human in the loop.

Closing

The free Katana RPC endpoint at https://moltnode.ag/katana gives you a no-key, JSON-RPC Katana node that works with viem, ethers, wallets, and AI agents — with automatic failover handled for you. Point your client at the URL and start building.