Skip to main content
RTILA Marketplace

The best financial data tools in one place

Finance data tools: published rate tables, filing indexes and market snapshots from public pages, structured to CSV with source and timestamp - never trading. 0 bots in this category.

Finance listings collect published financial data into structured files: rate tables, index and market snapshots from public pages, filing inventories, and repeated observations that become a history when you keep the dated outputs. The category boundary is strict - nothing here trades, executes, advises, or touches a brokerage account.

Expect source URL and collection timestamp on every row, numeric normalisation with the published unit kept verbatim, and a parse-failure flag instead of an invented number when a source changes format. Snapshot cadence is yours to schedule.

Every listing ships the same four launchers - a Windows .exe and .sh scripts for macOS Apple Silicon, macOS Intel, and Linux - delivered as a single raw file with no archive or extraction step. Restore the executable bit on the shell-script platforms, and clear the macOS Gatekeeper quarantine attribute before the first run. Market data ages fast: schedule runs at the cadence your question needs - hourly is neither possible nor polite for a desktop tool, and no listing pretends otherwise.

Bots in this category

No bots in this category yet

Check back soon, or browse another category.

Finance bots: frequently asked questions

Do any of these tools trade or place orders?
Never. This category collects published data into files; execution, custody and advice are entirely outside what a listing may do, and the acceptable-use policy backs that boundary.
What financial data can I collect?
Anything publicly published: rate tables, quotes on public pages, filing lists, fund fact sheets. Rows carry the source and the timestamp, so the file is auditable.
Is the data real-time?
No - each run is a snapshot at a time you scheduled. For questions that need tick data, a desktop collection tool is the wrong instrument and no listing claims to be one.
How reliable is the parsing?
Extraction either matches the published value or flags the row; a source redesign surfaces as parse failures you can see, never as plausible-looking numbers.