Stellar Plans Pricing
The Stellar Horizon API (SDF-hosted) is free and open to use with no API key, registration, or subscription required. Network transaction fees on Stellar are paid in XLM (the native asset) at the time of transaction submission and are not charged per API call. The minimum base fee is 100 stroops (0.00001 XLM) per operation; during network congestion users may submit a higher fee to prioritize inclusion. Teams requiring higher API throughput or SLA guarantees must self-host Horizon or use a third-party RPC provider. The Stellar network itself has no native paid API tier.
Stellar Plans Pricing is the machine-readable pricing-plan profile for Stellar on the APIs.io network, conforming to the API Commons Plans specification.
It defines 3 plans, covering free, custom, and usage-based tiers, with named plans including Stellar Horizon — Public Free, Stellar Horizon — Self-Hosted, Stellar Network Transaction Fees.
Tagged areas include Blockchain, Cryptocurrency, DEX, Ledger, and Payments.
Plans
Open access to the SDF-hosted Horizon REST API at horizon.stellar.org. No registration, API key, or payment required. Rate limited to 3,600 requests per hour per IP address.
- Full Horizon REST API access (read and submit)
- SSE streaming for real-time ledger events
- Public mainnet and testnet instances
- No API key required
Organizations run their own Horizon instance against a Stellar Core full node or captive core. This eliminates the SDF rate limit and provides full control over data retention, query performance, and uptime SLA. Infrastructure cost varies by cloud provider and node size.
- Unlimited API request rate (self-imposed limits only)
- Full control over ingestion window and data retention
- No dependency on SDF infrastructure
- Open-source Apache 2.0 licensed software
Transaction fees on the Stellar network are paid in XLM at submission time. The minimum base fee is 100 stroops (0.00001 XLM) per operation in a transaction. During surge pricing, users may set higher fees (fee bumps) to compete for inclusion in the next ledger.
- Fee paid in XLM (native asset)
- Fee bump transactions for third-party fee sponsorship
- Surge pricing during high network load