Public funding data · Developer workflow

Keep funding data in your own workflow.

Save nine verified USD funding inputs with their dates, units and sources. On your next run, fetch the changes and keep the last successful packet if a request fails.

Download the Python job Open a research notebook Read the API contract

Public access needs no account, payment or meeting. Inspect dates and source terms before using or redistributing the data.

Run once. Reuse it tomorrow.

Save the Python job, then run it with Python 3.10 or newer on macOS or Linux. It uses the standard library.

python3 daily_job.py --state ./funding-state

The output says updated or unchanged. Verified JSON, CSV and their manifest stay in funding-state/packets/. Captured changes stay in funding-state/changes/. A failure exits with code 2 and preserves the previous cursor.

Run it once for each research update you need. A daily task is enough for a daily report. Keep the state directory between runs.

# Example cron entry: daily at 08:00 in the machine's timezone.
0 8 * * * /usr/bin/python3 /absolute/path/daily_job.py --state /absolute/path/funding-state

Notebook template · Request and error examples · Attribution and source terms

Connect the tools you already use.

OpenBB Workspace

Add this custom backend, then open the Funding Evidence Automation app:

https://api.seiche.info/funding-evidence

The table uses the same versioned packet endpoint and preserves dates and newer-data flags. Stale or failed inputs return an error.

Agents through MCP

Download the small local tool beside the daily job. Install the MCP SDK and explicitly connect the tool in your agent host.

Local MCP tool · Setup and example research task

The tool shares the same packet checks and local cursor. A template does not automatically install itself in another application.

The hosted packet API and downloadable templates are independently deployed. The published Financial Evidence v0.1.5 package retains its existing transport API; installing that wheel alone does not install this new job.

Know what changed—and what is still unknown.

SOFR and IORB use a common review date. Weekly inputs keep their own observation dates. Archive time means the first time this service verified a packet. The archive contains observed packets and visible gaps; it does not reconstruct complete historical publisher vintages.

The change feed describes differences between captured packets. A same-date change is not independently confirmed as a publisher revision. HTTP 503 means the latest evidence failed availability or freshness checks; a cached response cannot override those checks.

Observed reliability and gaps · Forward archive coverage

Optional identity for your application.

Anonymous reads work immediately. If you choose an application key, you consent to the service recording a random installation identity, UTC day and packet for successful data responses. This helps measure returning integrations. It does not identify your employer or prove independent ownership.

The key is returned once. Keep it in a private file and pass --token-file /private/path/key to the job. Keyed access has the same public limits; it does not promise a higher quota or an SLA. Never put a key in a URL, notebook output, public repository or agent prompt.

Enrollment and deletion instructions · Retention and privacy

Application completions expire after 90 UTC dates. Keys expire after 180 days without accepted use. Deleting a key removes its identity and linked events. Our own applications and synthetic checks are excluded from external-use counts; self-issued keys remain unverified until independent ownership is established.