#ripple

Live on-chain data from the XRP Ledger (XRPL), the decentralized blockchain behind XRP, served straight from public XRPL nodes by JSON-RPC — no key, nothing cached. The account endpoint returns any address's core state: its XRP balance, transaction sequence, the number of objects it owns, and its account flags and domain — the genesis-era account rHb9CJAWyB4rj91VRWn96DkukG4bwdtyTh holds tens of thousands of XRP. The balances endpoint returns the full wallet: the XRP balance plus every issued-currency trustline (token or stablecoin) the account holds, with the issuer, currency and amount, decoding hex currency codes to readable tickers. The transactions endpoint returns the account's most recent ledger activity — payments, DEX offers, trustline changes — each with its hash, type, amount, fee, result and time. The server endpoint returns the state of the ledger itself: the latest validated ledger index and age, the base and per-object XRP reserves, the current fee and the node software version — the network health a wallet or explorer needs. Everything is read live from the XRPL, nothing stored. This is the XRP Ledger on-chain layer for any wallet, explorer, exchange, payments or analytics app. Distinct from EVM and Solana on-chain APIs and from price feeds — this is XRPL account state, token balances, transactions and ledger health. 4 endpoints, no key on our side.

api.oanor.com/xrpl-api

Rectifier ripple and smoothing-capacitor maths as an API, computed locally and deterministically. The ripple endpoint computes the peak-to-peak ripple voltage left on a reservoir (smoothing) capacitor after a rectifier, Vr = I_load/(f_ripple·C), where the ripple frequency is the line frequency for a half-wave rectifier and twice it for a full-wave or bridge rectifier — and it solves for whichever of the load current, the capacitance or the ripple you leave out, also giving the RMS ripple. The capacitor endpoint sizes the smoothing capacitor for a target ripple, C = I_load/(f_ripple·Vr), and the energy it stores. The output endpoint gives the DC output of the rectifier from the transformer RMS voltage: the peak Vrms·√2, minus the diode drops in the conduction path (one for half-wave and centre-tapped, two for a bridge), the average DC voltage and, given the ripple, the ripple factor. Everything is computed locally and deterministically, so it is instant and private. Ideal for power-supply and electronics-design tools, linear PSU, charger and audio-amplifier design, and electronics education. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is rectifier ripple and filtering; for Ohm's law, reactance and RC time constants use an Ohm's-law API.

api.oanor.com/rectifier-api