Autheo
BuildTechnologyFaucetBlog
About UsOur TeamOur PartnersGlossaryMerch Store
Node SaleEmission StructureTiered PricingValidator AdvantageNode Sale FAQsBuy a Node
Early AccessExplorer

What RPC endpoints and rate limits does Autheo provide?

Autheo's RPC architecture mirrors the proven Ethereum + managed-provider model and is operated in partnership with InfStones and Zeeve, both of which run validator and RPC infrastructure for dozens of major networks.

Direct Answer

Autheo provides public RPC endpoints for mainnet and testnet at no cost, with rate limits suitable for development and small production workloads. Higher-volume teams can subscribe to managed RPC tiers via InfStones and Zeeve or run self-hosted nodes for unmetered access.

Understand the broader Autheo platform

This answer covers one part of the Autheo ecosystem. To understand how this capability fits into the full platform, start with the core Autheo overview and architecture pages.

Autheo overview →Technology and architecture →Developer documentation →

Public RPC Endpoints

The default mainnet RPC is published at docs.autheo.com along with the testnet endpoint. Public endpoints support eth_call, eth_sendRawTransaction, eth_getLogs, and the full standard Ethereum JSON-RPC method set, plus Autheo-specific extensions for AutheoID and AEE compute calls.

Rate Limits and Tiering

Public endpoints enforce per-IP request limits to prevent abuse, sized to support typical development and lightweight production traffic. For higher throughput, managed RPC partners InfStones and Zeeve offer paid tiers with dedicated capacity, geographic distribution, and SLAs. The same JSON-RPC URL pattern works across tiers, so upgrading is a config change.

Self-Hosted Nodes

Teams that need full control can run their own Autheo full node on commodity hardware. A self-hosted node delivers unmetered RPC access, lower latency for co-located applications, and the ability to enable archival mode for historical queries. Autheo's documentation includes Docker Compose templates and Kubernetes Helm charts for production node operations.

Key Statistics

~ 100K req/day
Industry standard public RPC daily limit
Major Layer-1 networks including Ethereum and Polygon enforce free-tier public RPC limits in the range of 100,000 requests per day per IP, the same band Autheo's public endpoints target.
Source ↗
99.9%
InfStones managed nodes uptime SLA
InfStones, an Autheo infrastructure partner, publishes a 99.9% uptime SLA on its managed validator and RPC services across 20+ public chains.
Source ↗
60+
Standard Ethereum JSON-RPC methods supported
Autheo's EVM adapter implements the standard Ethereum JSON-RPC specification, which defines more than 60 methods including the eth_*, net_*, and web3_* namespaces, plus Autheo extensions.
Source ↗

Expert Perspective

“

Public RPC nodes are table stakes. The real differentiator is managed RPC at scale, and the way Autheo partners with InfStones and Zeeve means developers get both options without switching providers.

Infrastructure Engineer, Layer-1 RPC specialist (composite)

Citations & Sources

  1. [1]
  2. [2]
  3. [3]

Related Questions

Developer

How does Autheo handle event logging and monitoring?

Read answer →
Developer

What SDKs and client libraries does Autheo offer?

Read answer →
Developer

Does Autheo support EVM-compatible smart contracts?

Read answer →

Explore More

Developer Docs →Autheo DevHub →

Ready to Start Building?

Explore Autheo's unified Layer-0 OS: blockchain, compute, storage, AI, and identity in one integrated platform.

Start BuildingExplore the TechnologyBrowse All FAQsContact Us