An RPC provider on the network.
Six ways in, one key.
Tenzro JSON-RPC
The full network surface — models, providers, identity, payments, settlement, storage, and agents. The same methods a node exposes, reachable without running one.
Chain RPC
Endpoints for the chains the network settles across — EVM, SVM, and Canton/DAML. Standard eth_* and SVM calls against the multi-VM ledger, so existing wallets and tooling work unchanged.
Inference API
OpenAI-compatible chat, embeddings, and transcription. Point an existing SDK at it and change the base URL — no Tenzro-specific client required.
MCP
Model Context Protocol endpoint so agents and assistants can discover and call network capabilities as tools.
A2A
Agent-to-agent surface for autonomous software that needs to find, hire, and pay other services on the network.
Faucet
Testnet TNZO for development, so you can exercise paid paths before spending anything real.
Our own nodes
We run the infrastructure behind these endpoints — validators, model-serving nodes, and chain RPC — rather than reselling someone else's. We are an operator on the network like any other.
No node to run
Running your own means syncing state, keeping it patched, and staying online. Use ours instead and skip all of it.
Routed beyond us
For inference, requests are matched across operators by price, latency, and track record — not pinned to our hardware. If someone serves it better, they get the work.
One key, one bill
A single key across every surface, metered together and billed by card, bank, stablecoin, or credits.
The network is permissionless and open source — you can always run your own node and talk to it directly, and nothing about the protocol privileges ours. These endpoints exist because most people would rather not, and because someone has to run nodes for the network to work. We do both.