Federal Contract Recompete Watch

Keep your next contract move in sight.

Bring the contracts you care about. Get a focused review of recorded dates and related SAM notice evidence, with source links that make the next step clearer. Spend your attention on what needs a closer look, not another pile of records.

Reviews use dated official data. A related notice is a research lead, not a guarantee that a contract is open for competition.

Try the demo · Review your contracts · Pricing · Help

What you get

A readable contract review, a CSV working list, and the evidence behind it. See relevant recorded dates, supported notice relationships and missing information together. Each snapshot review shows the source edition and coverage, so you know what was checked.

Demo

Leave Demo / award_only selected to explore three fictional contracts. Start the run, then open REPORT.html from Output. The sample shows near, later and missing completion dates without making source requests.

The demo has no custom review charge. Apify's automatic $0.00005 per start still applies; check the displayed maximum cost before starting.

Start here

1. Select Review, then award_and_snapshot for the dated SAM notice review.
2. Paste your watched contracts into Contract CSV, using the template below.
3. In Dated snapshot scope, choose the start/end posting dates. Leave the revision as current, then run and open REPORT.html.

customerId,awardUrl
example-official-award,https://www.usaspending.gov/award/CONT_AWD_H907_9700_SPE2DX16D1500_9700

This historical award illustrates the format; it is not a current opportunity recommendation. Replace it with your contracts. Use the complete USAspending award link, including its parent-award identity. Leave API-only notice controls empty when using snapshot coverage.

Download REVIEW.csv for your working list. Output also links the structured results. The Dataset is a convenience view, not the only result location.

Pricing

Base price: $0.01 per completed contract review. Platform usage is included, with Apify's automatic $0.00005 per start in addition. No Dataset-row surcharge.

Apify plan	Price per completed review
Free	$0.0100
Bronze	$0.0090
Silver	$0.0085
Gold / Platinum / Diamond	$0.0080

A contract is charged once when its selected required coverage is complete, not once per notice or passage. Duplicate inputs do not multiply the charge. Results are saved before the custom charge; your run spending limit is respected. Check current pricing before starting. An unknown charge outcome is not automatically retried.

Know what was reviewed

SAM publishes active-notice extracts daily. We publish dated updates for this Actor; they are not real-time. Check the report's source date and follow the original notice for current deadlines or amendments.

The review covers the selected posting window and available source edition, not a complete historical archive. Missing descriptions or unassigned notices in that window prevent completed-review billing. A notice absent from a later active file is not automatically a cancellation.

Help

Ask about your watchlist or a result in the Issues tab. For a run problem, include its run ID and what you expected. Use fictional examples in public support rather than private watchlists, credentials or access links.

A stopped run may already have saved results or a charge. Inspect that run's Output and charge information before starting another.

Advanced reference

Input parameters

Provide up to 100 references through contractsCsv or advanced contracts, not both. lookAheadDays defaults to 180. Current and potential completion dates remain separate. maxRequests defaults to 60 and is capped at 100 across sources. The API-mode simple date controls use two pages of ten notices and up to twenty descriptions per organization; limits can leave incomplete coverage. Advanced noticeSearch replaces the simple API date controls.

Dated snapshot coverage

Use coverage: "award_and_snapshot" and snapshot.postedFrom/postedTo as inclusive YYYY-MM-DD dates within the supported window (at most 365 days). Omit revision or use current to resolve the published edition once at run start. A publication during your run does not change that selection.

The report records the exact revision. Advanced jobs may request a retained 64-character revision; retired revisions fail without silently advancing or charging a completed review. Current/rollback revisions are retained, not every old revision indefinitely. Operator-provided source access is used; no schedule is created. Source publication, acquisition and coverage gaps remain explicit.

Authenticated SAM description retrieval remains a separate unqualified API-mode capability. It is not needed for the accepted snapshot path. Award-only output is a more limited research aid; demo uses fictional award-only evidence.

Output format and repeated reviews

REPORT.html is the review and REVIEW.csv the working queue. OUTPUT links canonical JSON and files. Partial coverage is explicit. A failed Dataset append does not remove the saved report.

Monitor uses a named history store and state.scopeId; state.storeId and an optional baselineSnapshotId select retained comparisons. CHANGES.json/CSV separates source, decision, clock and input changes. History is accepted for 90 days; missing or ambiguous history is disclosed. For hosted Monitor select historyStoreId; any supplied state.storeId must match. This is not a schedule.

Evidence and privacy

An explicit reference names a contract within the same agency scope. It does not establish an open solicitation. Preliminary, cancelled, inactive and past-deadline notices keep their context. Dates alone do not prove a recompete, termination or exercised option. There is no attachment or contact harvesting. Requests are bounded without retries/redirects; source failures stay visible.

Permissions

Use permitted business data and suitable storage/sharing settings. Limited permissions apply; selected history stores need the stated read/write access. Keep credentials, unrelated personal identifiers and payment data out of input. Only selected evidence is retained, not raw upstream error bodies or unselected fields. The charge event remains contract-review-completed.

See the bundled changelog for implementation history.