bidflow-ingest

Automate tender ingestion by setting up connectors to TED and SAM.gov APIs, which parse responses, normalize the data into a structured format, deduplicate entries via content hashing, and persist results to a database. Use /sync ted or /sync sam_gov commands to trigger ingestion workflows.

Data normalization transforms raw tender notices from multiple sources into a consistent schema with standardized fields. This enables cross-source querying, deduplication by content hash, and reliable downstream analytics on bid data.

Yes. The Skill supports dual-source ingestion from TED and SAM.gov APIs into one normalized, queryable database. Deduplication via hashing prevents duplicate entries across sources, and CLI commands like /sync ted and /sync sam_gov --from DATE allow scheduled or on-demand syncs.

You need Node.js runtime, access to TED and SAM.gov API endpoints, authentication credentials for each source, and a database to persist normalized bid records. The Skill handles connector setup, query building, and error handling internally.

Configure API credentials for TED and SAM.gov sources within the connector development layer. The Skill implements built-in authentication setup as part of its connector requirements, enabling secure API queries and response parsing.

Implement content-based deduplication using hashing, as this Skill does via a contentHash field in the NormalizedBid model. Hash-based dedup identifies duplicate records across TED and SAM.gov regardless of source format differences.