US Financial Data API avatar

US Financial Data API

Pricing

from $0.005 / actor start

Go to Apify Store
US Financial Data API

US Financial Data API

Search US banking, filings, rates, futures, broker, complaint, and insurance datasets in one run. Get structured financial records fast.

Pricing

from $0.005 / actor start

Rating

0.0

(0)

Developer

kane liu

kane liu

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

10 days ago

Last modified

Share

US Financial Data Search

Search 24 US financial data sources in one query — banking, markets, Treasury, consumer and disaster records, plus New York state financial-program data.

  • ✅ Search 24 US financial data sources across FDIC, FINRA, SEC, CFTC, Treasury, CFPB, FEMA, CoinGecko, and New York state datasets
  • ✅ Get bank and branch records, broker and filing data, futures and market data, Treasury records, complaint and disaster records, and NY state program data in one workflow
  • ✅ Covers 5 banking sources, 6 markets sources, 4 Treasury sources, 4 consumer-protection and disaster sources, and 5 New York state sources
  • ✅ Export results as Excel, CSV, or JSON, or connect it to Apify MCP, API, Make, n8n, and Zapier
  • ✅ Current Apify listing is pay per usage, so you can start with small runs and scale only when the workflow proves useful

US financial data is fragmented across many systems. Bank records live with FDIC, broker records with FINRA, public-company filings with SEC, futures positions with CFTC, rates and debt data with Treasury, complaints with CFPB, disaster and insurance context with FEMA, and some program data at the state level. This Actor combines those active public datasets into one search layer so you can search the parts of the finance-data stack that matter for your workflow, then export or automate the results.


What you can do with it

1. Search banks, branches, failures, financials, and broker records

The banking side of this Actor includes FDIC institutions, locations, financials, failures, and FINRA BrokerCheck. That means you can search bank or firm names and get a broader public-record view than you would from one registry alone.

This is useful when your workflow starts with a bank, broker, or financial institution and you want one place to search for related public records.

What you enter:

WhatExample
Search termJPMorgan, Goldman Sachs, Wells Fargo, or Morgan Stanley
CategoriesBanking only
How many results50 per source

What you get back:

SourceExample fields
FDIC institutions, locations, financials, failuresInstitution or branch name, location, asset or failure metadata
FINRA BrokerCheckFirm or broker name, registration or status metadata

This is useful for institution due diligence, onboarding checks, financial-sector research, compliance support, and AI assistants that need one search layer across bank and broker public datasets.


2. Search SEC filings, futures data, and crypto market records

The markets side of this Actor includes SEC filings, four CFTC source groups, and CoinGecko market data. That creates a useful public-data mix for company-disclosure, derivatives, and market-observation workflows.

These are not one unified schema, but that is part of the value. A workflow may need company filings, positioning-style futures data, and crypto market context together.

What you enter:

WhatExample
Search termTesla, crude oil, Bitcoin, or S&P 500
CategoriesMarkets only
How many results50 per source

What you get back:

SourceExample fields
SEC filingsCompany name, form type, filing date, reporting metadata
CFTC datasetsContract or market name, position or report metadata
CoinGecko marketsCoin name, symbol, pricing or market-cap context

This is useful for market research, disclosure monitoring, futures tracking, crypto context gathering, and finance workflows that need one public search layer across multiple market datasets.


3. Search Treasury debt, rates, exchange-rate, and fiscal-report datasets

The Treasury side of this Actor includes debt, exchange rates, fiscal reports, and interest rates. That gives you one public-data entry point for government-rate and Treasury-reference workflows.

This is useful when you need official Treasury series or fiscal context without treating each dataset as a separate integration.

What you enter:

WhatExample
Search term10-year, dollar, fiscal, or yield
CategoriesTreasury only
How many results50 per source

What you get back:

SourceExample fields
Treasury datasetsInstrument, debt, rate, exchange-rate, or fiscal-report metadata and dates

This is useful for macro monitoring, fixed-income support, rate tracking, Treasury-data research, and workflows that need official US Treasury public records in one place.


4. Search complaints, disasters, housing assistance, and flood-insurance claims

The consumer-protection side of this Actor is broader than just complaints. It includes CFPB complaints plus FEMA disaster declarations, housing assistance, and NFIP claims. That makes it useful for public-risk and consumer-signal workflows where institution-level complaint data and geographic disaster context both matter.

This is especially useful when your search term is a company, place, or risk topic rather than a security or bank name.

What you enter:

WhatExample
Search termWells Fargo, Houston, or mortgage
CategoriesConsumer protection only
How many results50 per source

What you get back:

SourceExample fields
CFPB complaintsCompany, product, issue, complaint metadata
FEMA datasetsDisaster, housing-assistance, or insurance-claims metadata

This is useful for complaint monitoring, geographic-risk research, portfolio context, underwriting support, and mixed public-risk workflows that need complaint and disaster data together.


5. Use one Actor for mixed financial discovery in AI and automation workflows

The main advantage of this Actor is that you can search across several important US finance-data families without integrating each agency dataset separately.

Instead of wiring FDIC, FINRA, SEC, CFTC, Treasury, CFPB, FEMA, CoinGecko, and New York state data into your stack one by one, you can use one Actor as the discovery layer.

What you enter:

WhatExample
Search termGoldman Sachs
CategoriesBanking + markets + Treasury
How many results25 per source

What your assistant or automation gets back:

Source familyReturned data
BankingBank, branch, financial, failure, and broker-related records
MarketsFiling, futures, and crypto market records
TreasuryDebt, rates, exchange-rate, and fiscal-report records
Consumer / NY stateComplaint, disaster, insurance, and state-program records if enabled

This is useful for internal finance assistants, monitoring workflows, public-data research, due-diligence support, and spreadsheet-based analysis that needs one US financial-data entry point.


How to use (no code required)

  1. Click "Try for Free" at the top of this page
  2. Type one or more search terms — institution names, tickers, commodities, crypto terms, rate keywords, locations, or program names
  3. Choose which categories to search:
    • banking
    • markets
    • Treasury
    • consumer protection
    • New York state
  4. Set how many results you want per source
  5. Click Start — the Actor queries the enabled financial data sources and returns the results in the Dataset tab

You can then export the results as Excel, CSV, or JSON.

Because the Actor is listed as pay per usage, it is easy to begin with a small run, confirm which source families matter for your workflow, and then expand from there.


What you get back

Each result comes back as one dataset row. The exact columns vary by source family, because a bank record, a public filing, a futures position row, a complaint, and a state-program record do not share the same schema.

Across the dataset, you will typically see:

  • _product_id
  • _source
  • _search_term
  • _collected_at

Then source-specific fields such as:

  • Banking: institution, branch, asset, failure, or broker-related metadata
  • Markets: filing, market, contract, coin, or positioning fields
  • Treasury: rate, debt, exchange-rate, or fiscal-report fields
  • Consumer protection: complaint, disaster, housing-assistance, or flood-insurance fields
  • New York state: ATM, incentive, IDA, insurance, or SONYMA program fields

Every row tells you which source it came from and which search term matched, so it is easy to split outputs by source family and move them into downstream analysis or automation workflows.


Coverage

This Actor currently searches 24 active US financial data sources:

CategoryCountCoverage
Banking5FDIC institutions, locations, financials, failures, and FINRA BrokerCheck
Markets6SEC filings, 4 CFTC datasets, and CoinGecko markets
Treasury4Debt, exchange rates, fiscal reports, and interest rates
Consumer protection and disaster4CFPB complaints plus FEMA disaster, housing, and NFIP claims
New York state5ATM locations, incentives, IDA projects, insurance premiums, and SONYMA loans

The current active maps in the Actor are:

  • 5 banking sources
  • 6 markets sources
  • 4 Treasury sources
  • 4 consumer-protection and disaster sources
  • 5 New York state sources

That matters because this Actor is not one unified finance terminal. It is a combined public-data discovery layer across several different US financial source families.


Pricing

This Actor is currently listed on Apify as pay per usage.

The safest place to confirm the live commercial terms is the pricing tab:

If you want to keep runs small, the easiest approach is to:

  • search only the categories you actually need
  • start with one or two search terms
  • lower maxResultsPerSource for exploratory runs

Connect to your tools

You can use this Actor directly in the Apify UI, or connect it to automation and AI workflows:

PlatformHow to connect
Apify UIRun it directly and export results
Apify APITrigger runs and fetch datasets programmatically
Make.comUse the Actor ID lentic_clockss/us-finance-search
n8n / Zapier / ChatGPT / ClaudeUse the same Actor ID via Apify MCP or API

→ Browse all Actors: apify.com/lentic_clockss


Also Available