FDIC Bank Intelligence

Turn the official FDIC institution feed into a small, documented dataset for bank due diligence, counterparty enrichment, market mapping, and agent workflows. Run it from the Apify Console, the Apify API, or a scheduled automation. It returns a clear summary first, followed by normalized bank records that retain the official source URL.

What does FDIC Bank Intelligence return?

The actor queries the public FDIC institutions API and produces one dataset row per matched institution. It is useful when a spreadsheet, CRM, risk workflow, or AI agent needs stable identifiers and numeric financial fields instead of an unstructured search result.

Each run writes these two record types:

• A summary row first, with the query, state, active-status filter, count, totalAvailable, aggregates for returned assets and deposits, activeCount, pagination values, warnings, and an agentMarkdown briefing.
• A bank row for every returned institution, with the certificate, name, operating status, city, state, address, county, coordinates, assets, deposits, domestic branch count, regulator, FDIC supervisor, charter agent, dates, website, completeness score, source URL, retrieval time, and agent-ready markdown.

The live E2E run used the official source with a Maine state filter and a limit of three. It confirmed that rows include schemaVersion, recordType, id, sourceUrl, retrievedAt, fieldCompletenessScore, name, certificate, activeStatus, assetsUsd, depositsUsd, regulator, and agentMarkdown. The FDIC response is parsed from its meta object plus data entries that contain a nested data object.

If this actor saved research time, please leave a short review after the run: FDIC Bank Intelligence reviews.

Why use this instead of a manual FDIC search?

Manual lookups work for one bank. They become repetitive when you need a bounded result set, a repeatable source URL, numeric fields suitable for filtering, and a record a downstream process can identify later. This actor applies an optional name fragment, a two-letter state, an active-only flag, limit, and offset to the official source. It preserves missing source values as null rather than inventing a value.

The output is deliberately narrow. It is an institution-intelligence feed, not a credit opinion, a branch-hours directory, or a substitute for reviewing current official filings. The sourceUrl on every row makes verification practical.

Input reference

Field	Type	Default	What it controls
query	string, up to 120 characters	""	Optional bank-name fragment sent to the FDIC name filter.
state	two letters	omitted	Optional institution state, for example "ME" or "TX". Case is normalized.
activeOnly	boolean	true	Requests institutions marked active by the FDIC source.
limit	integer, 1 to 100	25	Maximum number of institution records returned in this run.
offset	integer, 0 or higher	0	Offset for deterministic page-style traversal of a larger result set.

Concrete input for a first pass over active Maine institutions:

{
  "query": "",
  "state": "ME",
  "activeOnly": true,
  "limit": 25,
  "offset": 0
}

Use a small limit while designing an automation. Once the fields and filters are correct, move offset forward by the same page size. The actor enforces the maximum of 100 records per request to keep each result set manageable.

Output reference

Every row has a schema version, a record type, a stable actor ID, source URL, retrieval timestamp, completeness score, and agentMarkdown. Dataset ordering matters: row one is always the summary, then come the bank rows.

{
  "schemaVersion": "1.0",
  "recordType": "bank",
  "id": "fdic-bank-10",
  "sourceUrl": "https://api.fdic.gov/banks/institutions?format=json&limit=25&offset=0&filters=STALP%3AME+AND+ACTIVE%3A1",
  "retrievedAt": "2026-07-18T15:00:00.000Z",
  "fieldCompletenessScore": 89,
  "name": "Example Institution",
  "certificate": 10,
  "activeStatus": "active",
  "city": "Example City",
  "state": "me",
  "assetsUsd": 125000000,
  "depositsUsd": 99000000,
  "domesticBranches": 3,
  "regulator": "OCC",
  "website": null
}

The values above demonstrate the verified output shape, not a claim about a current institution. Monetary values remain numbers when the FDIC returns them. A field such as assetsUsd, website, coordinates, or a date can be null when it is absent or unusable in the source response.

The accompanying summary is designed for a workflow to inspect before it processes individual records:

{
  "recordType": "summary",
  "id": "fdic-summary-0-25-all-ME",
  "query": "",
  "state": "me",
  "activeOnly": true,
  "count": 25,
  "totalAvailable": 0,
  "offset": 0,
  "limit": 25,
  "sourceStatus": "ok",
  "assetsUsdTotal": 0,
  "depositsUsdTotal": 0,
  "activeCount": 25,
  "warnings": []
}

totalAvailable, assetsUsdTotal, and depositsUsdTotal are examples of fields, not promised values. Read the actual row, especially when a run has a narrow query or an expected no-match.

Tutorial: build a repeatable bank research list

1. Start with a state-only search, activeOnly: true, limit: 25, and offset: 0.
2. Open the first dataset row. Confirm sourceStatus is ok, note count and totalAvailable, and keep the sourceUrl for your audit trail.
3. Filter the following bank records by certificate, regulator, assetsUsd, depositsUsd, or domesticBranches in your data tool.
4. For a name-specific review, add a short query. Treat it as a name search aid, then validate the certificate and source record before making a decision.
5. If more records exist, run the next page with offset increased by the prior limit. Deduplicate downstream on id or certificate.
6. Store retrievedAt with your own decision record. Institution data can change, and a future run should be understood as a new observation.

The actor also creates AGENT_BRIEFING.md in the key-value store. It gives an automation a compact handoff with the query, number returned, active filter, aggregate assets, and source status.

Worked examples from the verified output contract

1. Find active banks in a state

Input:

{"state":"ME","activeOnly":true,"limit":3,"offset":0}

The live E2E shape for this source path returned three bank records and a summary. Use summary.count to confirm the page size, then use name, certificate, city, state, and activeStatus for a compact market list. Every returned record points to the FDIC API URL that produced it.

2. Build a regulator-enrichment table

Input:

{"state":"TX","activeOnly":true,"limit":50,"offset":0}

Send certificate, name, regulator, fdicSupervisor, charterAgent, assetsUsd, and depositsUsd to your table. Keep fieldCompletenessScore beside optional fields so a null is not mistaken for a failed enrichment. This is useful for prioritizing a later review, not for assigning regulatory status beyond what the source reports.

3. Research a name fragment without losing provenance

Input:

{"query":"community","state":"ME","activeOnly":false,"limit":25,"offset":0}

The actor combines the state, active-status, and safely encoded name filters in the official request URL. It returns activeStatus as either active or inactive, allowing an analyst to keep historical institution results distinct from active ones. Use the certificate rather than the displayed name as your preferred institution identifier.

4. Page through a bounded list

First run:

{"state":"CA","activeOnly":true,"limit":100,"offset":0}

Next run:

{"state":"CA","activeOnly":true,"limit":100,"offset":100}

Compare each summary's offset, count, and totalAvailable. Append only bank rows to your destination, keyed by id. This prevents the summary rows from being treated as institutions and lets a workflow stop when count is lower than the requested page size.

5. Send a compact record to an AI research agent

Use the agentMarkdown field from a bank record. It includes the institution name, certificate, status, location, assets, deposits, and source URL. The agent can draft a follow-up checklist, but it should preserve the source link and label any conclusion as a review task.

6. Detect an expected no-match safely

Input:

{"query":"unlikely exact bank phrase","state":"ME","activeOnly":true,"limit":25,"offset":0}

An ordinary no-match is successful and returns a zero-count summary. That is different from a source failure: non-OK HTTP responses, malformed responses, and a non-empty source payload that cannot be normalized fail the run instead of being presented as a clean zero.

Agent workflows and monitoring

For counterparty monitoring, schedule a state or name-fragment query on a cadence that matches your risk process. On each run, first inspect the summary row. Alert on sourceStatus not equal to ok, unexpected zero results for a normally populated query, or a sharp change in count. Use id and certificate to compare runs, and retain sourceUrl and retrievedAt for a reproducible record.

A sensible workflow is:

1. Run the actor nightly or weekly with a fixed input.
2. Store only bank rows in a history table, preserving retrievedAt.
3. Compare current and prior records by certificate or id.
4. Route changes in activeStatus, reported assets, deposits, regulator, or website to a human review queue.
5. Use agentMarkdown and the official link in the queue item, not a generated narrative alone.

Do not use a delta as proof of a corporate event. Recheck the linked FDIC source and, where necessary, the institution's own disclosures.

Limitations and data handling

• The actor reflects fields available from the public FDIC institutions API at retrieval time. It does not calculate credit quality, ownership, branch operating hours, or insurance coverage for a specific account.
• Name matching is not entity resolution. Similar names can represent different institutions, and legal-name changes can occur. Validate with the certificate and official source.
• activeOnly uses the FDIC institution status field. It does not guarantee that every physical branch is open, that a product is offered, or that an account is insured in a particular situation.
• A null field means the source did not provide a usable value to this actor. It is not a zero, an estimate, or a negative answer.
• offset is suitable for page-style collection, but source data can change between runs. Keep run timestamps and deduplicate by stable IDs.
• This output supports research and workflow triage. It is not legal, financial, regulatory, or investment advice.

Buyer FAQ

Is this affiliated with the FDIC?

No. This independent actor reads a public FDIC API. It is not affiliated with, endorsed by, sponsored by, or operated by the Federal Deposit Insurance Corporation.

Can I get every matching bank?

Yes, use bounded pages. Set a limit from 1 through 100 and increase offset for later pages. Use the summary's totalAvailable and count to control the loop.

Why are assets or deposits sometimes null?

The actor preserves the official source's availability. It does not infer missing financial values. Keep the completeness score and source URL in downstream reporting so missingness stays visible.

Does active status tell me a branch is open today?

No. It reflects the institution status returned by the FDIC source. Confirm physical locations, services, account coverage, and any transaction-specific fact through the relevant official channel.

What does a zero-result run mean?

For a legitimate no-match, it means the filter returned no records and the summary reports count: 0. A source HTTP error, malformed payload, or parser-drift condition fails the run rather than pretending to be a zero-result success.

Can my CRM use the output directly?

Yes. Use id or certificate as the deduplication key, map numeric assets and deposits without string parsing, and keep sourceUrl and retrievedAt as provenance fields.

Can an AI agent consume this without another aggregation step?

Yes. The first row is an explicit summary and each institution includes agentMarkdown. An agent should still open the supplied official source before taking an external action or making a material recommendation.

Is there a rate or result-size limit?

Each run accepts at most 100 records through limit. For broader coverage, paginate responsibly and avoid issuing redundant requests from parallel automations.

Pricing

Live Store pricing is $0.01 per Actor start plus $0.003 per dataset result, displayed as $3.00 per 1,000 results. Apify platform usage is included rather than billed separately. Use limit, pagination, and your Apify run-charge controls to keep institution research within budget.

Legal and non-affiliation

FDIC Bank Intelligence is an independent data-processing tool. FDIC names, data, and links belong to their respective owners. Use the public source according to its applicable terms and policies. You are responsible for validating information for your use case and for meeting any legal, regulatory, privacy, retention, and internal-control requirements that apply to your organization.

Related actors

• CPSC Product Recall Intelligence: monitor public product recalls, hazards, remedies, manufacturers, and official recall links for supplier or marketplace workflows.
• NHTSA Vehicle Safety Intelligence: research vehicle recalls and complaint signals when a counterparty or product workflow touches automotive risk.

Support and feedback

For a reproducible data or source-shape issue, open the actor's Issues tab with the input, sourceUrl, timestamp, actor run ID, and error text. Do not include confidential customer, account, or credential data. For a workflow request or a successful outcome, use the feedback section or leave a review. Clear examples of the expected fields and the linked public source help prioritize improvements.