Migrating a Crawl Pipeline from Firecrawl: Keep the Document Contract Stable
Описание и применение
Перенос пайплайна обхода с Firecrawl на Nstdata с сохранением стабильного внутреннего контракта документа, нормализацией ответов, сохранением состояния задачи и применением политики принятия.
Задача
Changing crawl providers requires a workflow migration that preserves the internal document contract and avoids breaking downstream RAG pipelines.
Результат
The migration stabilizes the document contract, enables resumable crawls, and provides a clear acceptance policy, improving reliability and comparability across providers.
Рабочий процесс
- Define an internal Document contract
- Normalize provider responses at the adapter boundary
- Persist durable crawl job state
- Implement application‑level acceptance checks
- Run the same corpus through both providers and compare metrics
- Roll out with a feature flag and rollback plan
Доказательства
Changing crawl providers is a workflow migration, not a base-URL edit.
The code is illustrative and has not been run against either paid API. Verify current API contracts before production use.
Define an internal document contract
Persist job state so the migration can resume
Treat acceptance as a separate status
- Дата записи: 2026-10-16T09:56:04.582Z