Excel & SQL
Download the CSV and keep its manifest with your workbook. Preserve dates, units and unavailable states.
Excel and DuckDB guideUSD funding · Public research
A funding review you can check.
Nine inputs for a macro or rates desk. Keep the values, source dates and exceptions together—from the first look to the saved research note.
Checking the latest saved review…
What the evidence says
Review date—
Source captured—
Packet archived—
This review aligns SOFR and IORB to a common date. Each input retains its own observation date; inspect newer-observation flags before discussing current conditions.
| Input | Value | Observed | Evidence state | Source |
|---|---|---|---|---|
| Loading the verified packet… | ||||
Percentages are rates; $B means billions of US dollars. Blank or restricted data stays unavailable. Dataset contract · Source attribution and rights · Packet manifest
Return to what you saved.
Loading forward archive coverage…
Archive time is when this service first verified the packet. Earlier observation dates do not create earlier knowledge. This is captured research history, not complete publisher-vintage backtesting data.
Reliability, with the gaps visible.
Loading observed service coverage…
Server observations and independent GitHub observations run separately. Missing samples remain missing. A successful request is not proof of uninterrupted service or fresh data.
One packet. Your existing tools.
Automate a daily update — Python, OpenBB or agents
Python & scheduling
Save the verified manifest, JSON and CSV to a new folder. The small client uses Python's standard library.
Download the packet clientOpenBB & agents
Connect the existing funding-review backend to your research workspace. Every review keeps its evidence identity.
API documentationpython3 download_packet.py --output ./funding-review-001The packet client contacts only this service and does not report usage. Exit 1 means a retained review needs attention; exit 2 means acquisition or verification failed.
Make this part of your desk's review.
Start with the public automation guide; no meeting or account is required. For an integration question, include your tool, the packet identity and the error you observed.
Public research access is free and needs no account. Dedicated access, licensed delivery and support commitments require agreed terms. Please keep positions, client data and credentials out of public bug reports.