Bankrate Mortgage Rate Offers Scraper

What does Bankrate Mortgage Rate Offers Scraper do?

This Actor parses mortgage-rate offer metadata from Bankrate responses when structured data is available. It handles mortgage products, not residential property listings, and is not personalized financial advice. Run-local offer counts and bounded failure reasons are written to OUTPUT; diagnostics are never added as dataset rows.

Input

Provide public HTTPS Bankrate rate pages, an optional loan-type filter, and a bounded maximum. Only exact bankrate.com and www.bankrate.com hosts are accepted. Redirect responses are not followed.

Output

Accessible pages produce lender, loan type, rate, APR, points, fees, term, offer URL, and source provenance. A successful page with no matching offers completes with an empty dataset. Access restrictions, human-verification pages, and redirects stop further requests. A failed run with no saved offers reports nativeRunStatus: FAILED, collectionStatus: FAILED, and exit code 1; if an error occurs after one or more offers were saved, it reports nativeRunStatus: SUCCEEDED, collectionStatus: PARTIAL, and exit code 0. The Actor never invents financial offers or emits diagnostic/dummy dataset rows.

Source layout

• src/input.js validates scope and limits.
• src/http.js performs bounded public requests and classifies access state.
• src/parser.js parses and sanitizes public mortgage/loan JSON-LD.
• src/run.js processes pages, streams offer rows, and derives final run status.
• src/main.js connects the runner to Apify dataset and key-value storage.

Disclaimer

Mortgage rates, APRs, points, fees, eligibility, and availability change frequently. Verify current terms with Bankrate and lenders; this Actor is not financial advice.

Current source review

Chrome showed a human-verification challenge on the configured rates page on 2026-09-27. No challenge was completed and no Actor/source request was made. The historical challenge diagnostic was archived outside the active Actor dataset; no live offer records are currently saved. This Actor returns mortgage-rate offers, not residential property listings. See ./BROWSER_REVIEW.md.

Storage and dependency remediation

This stateless HTTP Actor uses Apify’s documented default Dataset/KVS REST endpoints on Cloud and the standard local filesystem layout for isolated apify run checks. The runtime token stays in an authorization header sent only to api.apify.com; it is never logged or sent to the target source. A small readable src/platform.js adapter replaces the SDK storage-only usage, removing the Crawlee/cache/ZIP/proxy dependency graph with unpatched advisories. Storage operations are awaited and fail explicitly; uncertain dataset writes are not retried. No migration, queue, proxy or general SDK features are advertised. Source authorization gates, access boundaries and data contracts are unchanged. Node 24 is required. Run npm ci, the existing regression tests (including platform storage tests), schema checks and a production-graph audit before deployment.