Help keep this open and current.

1. Sponsor on GitHub

Recurring sponsorships are the most useful kind of support — they fund the ongoing time spent tracking FFIEC API changes, updating docs when institutions restate filings, fixing edge cases reported against ffiec-data-connect, and keeping this site accurate.

No tier is gated. All features of the library are free for everyone under MPL-2.0. Sponsorship is a way for people and teams who rely on the project to fund its upkeep.

Sponsor call-report

2. Use it, and tell someone

If the library or these docs saved you time, a short note helps:

• Star ffiec-data-connect on GitHub. It's a cheap signal that the project is worth maintaining.
• Mention it in your team's internal docs or an external post. Search engines keep surfacing the wrong-API tutorials from older sites; correct references help drown those out.
• Cite it in papers or reports: Call.Report (2026). A resource for bank and holding company regulatory data. Retrieved from https://call.report.

3. Contribute

Bug reports and PRs for the library are welcome:

• ffiec-data-connect issues — bugs, features, API drift.
• Website issues (documentation errors, broken samples, unclear prose) — email michael@civicforge.solutions.

If a code example on this site fails against the real library, that's always a bug — please include the page URL and the traceback.

4. Commercial support

For teams that need priority response times, formal vendor agreements, or custom work (ETL on top of the library, internal deployments, training), Civic Forge Solutions LLC offers commercial support separate from the open-source project. See COMMERCIAL.md for scope and contact. Commercial arrangements do not gate any features of the library.