Books that reconcile, and evidence when they are questioned.
Point-in-time correct valuation, provenance on every field, and snapshots an auditor can verify.
The parts you keep working around.
Client reporting has to reconcile, and a historical balance that ignores the multiplier does not.
A vendor that cannot show where a number came from cannot be used in a regulated reporting chain.
Nothing proves a historical record was not altered after the fact.
How the platform answers, point by point.
Reports that don't reconcile
Every historical query applies the multiplier as of that block, and returns it alongside the answer
Unattributable numbers
Provenance on every field: source, block, observation time, and the code version that produced it
No tamper evidence
Daily merkle-rooted snapshots of the tape and multiplier series, published publicly
Every number carries its provenance.
Source, block, observation time, and the code version that produced it — on every field, so a disagreement with another vendor is diagnosable rather than mysterious.
Archive row · trades dataset
manual Parquet / CSV / JSONL export
Live message · StreamSwaps
stream.robinhoodrpc.io:443 · gRPC
Hover a field. It is the same field, byte for byte, on both sides. Raw export fields stay aligned with the stream field model.
Point-in-time by construction.
Historical queries require an as_of parameter and return the multiplier they applied. There is no code path that quietly uses today's scaling factor on a past balance.
Read the docs# Historical queries require as_of — there is no silent# "current multiplier applied to a past balance" path. curl -s https://api.robinhoodrpc.io/v1/accounts/0xabc.../positions \ -H "Authorization: Bearer $RHRPC_KEY" \ -G --data-urlencode "as_of_block=4200000" \ --data-urlencode "cost_basis_method=FIFO" \ | jq '.positions[] | { symbol: .token_symbol, balance_raw, balance_ui, multiplier_applied, multiplier_effective_block, total_return_pct, price_return_pct }'The plan that fits.
Scale
$200/moRecommendedgRPC streaming, full history, and every sink.
Signed snapshots and deterministic replay are Scale features. Audit export and a SOC 2 report are handled under Enterprise.
Compare both plansTalk to us about your reporting chain.
Signed snapshots, deterministic replay, and audit exports. We can walk your team through the controls before you commit.