Federal Contract Recompete Watch

Keep your next contract move in sight.

Bring the contracts you care about. Review recorded dates and supported links to SAM notices, with the source and coverage behind each finding. A related notice is a lead to investigate, not proof that bids are open.

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 recorded dates, supported notice relationships and missing information together. Each snapshot review identifies its source edition and coverage.

The optional pipeline brief separates repeated supplied contributions from consistently identified contributions. Forecasts, obligation assertions and contract-ceiling assertions stay separate. It describes your records, not verified revenue or your chance of winning an award.

Demo

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

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

Start here

1. Select Review, then award_and_snapshot for dated SAM notice evidence.
2. Paste 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. Download REVIEW.csv for the working list.

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

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

Follow the original notice for current deadlines and amendments. A completion date does not establish a recompete, cancellation or exercised option.

Pricing

$10.00 per 1,000 eligible completed contract reviews ($0.01 each at the base rate), including this Actor's platform usage, plus $0.00005 per start. There is no Dataset-row surcharge.

Apify plan	Price per completed contract 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. Missing required source coverage remains nonbillable as a completed review; startup charges may still apply.

Results are saved before the custom charge. Check current pricing and your run's maximum cost before starting. Account subscriptions, taxes and unrelated services are separate. An unknown charge outcome may already have settled and is not automatically retried.

Know what was reviewed

Reviews use dated official data, not a real-time or complete historical feed. Check the report's source date, posting window and coverage before acting. Missing descriptions or unassigned notices in the selected window prevent completed-review billing. Absence from a later active-notice file is not automatically a cancellation.

Award-only review is narrower than a notice-snapshot review. Authenticated SAM description retrieval in API mode is a separate unqualified capability, not a requirement for the supported snapshot route. There is no attachment or contact harvesting.

See what your pipeline is made of

Add the optional pipeline brief to Review when you have a prepared pipeline export. It compares declared contribution identities and amounts with the watched procurement references, keeping missing relationships visible.

For example, two amendment records may repeat one USD 100.25 forecast, alongside a separate USD 200 opportunity. Their raw forecast total is USD 400.50, but consistently identified contributions total USD 300.25. A USD 1,000,000 ceiling belongs in a different bucket; a missing currency remains unresolved. These are calculations on your supplied assertions, not a corrected forecast or verified revenue.

Pipeline rows add no separate charge or Dataset billing units. All existing contract-coverage requirements still apply. The pipeline settings below explain its identity requirements. The ordinary contract review does not need this option.

Help

Use the Issues tab for questions about preparing a watchlist or understanding results. Include a run ID for a run problem. Use fictional examples rather than private watchlists, credentials or access links.

A stopped run may already have saved results or a charge. Inspect its Output and billing state before starting another. The Actor does not contact prospects, submit bids or update your private systems.

Advanced reference

Input parameters and bounds

Provide up to 100 contract references through contractsCsv or 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. Request limits can leave coverage incomplete.

In API mode, simple date controls use two pages of ten notices and up to twenty descriptions per organization; noticeSearch replaces those simple controls. Requests are bounded without retries or redirects. Source failures remain visible rather than becoming an all-clear result.

Dated snapshot coverage

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

The report retains the exact revision. An advanced request can select a retained 64-character revision; a retired revision fails rather than silently advancing or charging a completed review. Current and rollback revisions are retained, not every edition indefinitely. Operator-provided source access does not create a customer schedule.

Pipeline settings

In Review mode, supply pipeline alongside the watched contracts. Include an opportunityScope, timezone-bearing capturedAt, and at most 100 rows / 128 KiB. Each row needs a literal rowId and procurement object. A resolved contribution requires opportunityId, contributionId, contributionRevision, watchedCustomerId, and procurement agencyCode plus full awardId.

{
  "opportunityScope":"fictional-export",
  "capturedAt":"2026-10-04T12:00:00Z",
  "rows":[{
    "rowId":"0001", "opportunityId":"OPP-001",
    "contributionId":"VALUE-001", "contributionRevision":"1",
    "watchedCustomerId":"watch-001",
    "procurement":{
      "agencyCode":"0000",
      "awardId":"CONT_AWD_FICTIONAL0001_0000_VEHICLE0001_0000",
      "orderId":"ORDER-001", "parentVehicleId":"VEHICLE-001"
    },
    "amount":{
      "kind":"customer_forecast", "value":"100.25", "currency":"USD",
      "periodStart":"2027-01-01", "periodEnd":"2027-12-31"
    }
  }]
}

This is the optional pipeline object, not a complete watched-contract request. Its fictional award cannot establish source coverage. Supply permitted exact references in the existing contracts or contractsCsv; pipeline rows never trigger additional acquisition.

Treat identifiers as text, including leading zeros. A contribution ID binds opportunity, watched reference, procurement scope, amount meaning/value/currency/period and revision. Exact repeats count once in distinct totals. Conflicting bindings exclude every row for that contribution from those totals. An amendment or related notice is evidence, not automatically another opportunity. Distinct opportunities sharing an award stay separate. Order, lot, solicitation and parent-vehicle relationships remain unverified where unsupported; missing IDs do not trigger fuzzy grouping.

Amount kinds are customer_forecast, award_obligation_assertion and contract_ceiling_assertion. Values are signed decimal strings with at most 12 integer and 6 fractional digits, a three-letter uppercase currency and explicit period dates. The official-source model supplies no obligation or ceiling amounts. Raw totals include repeats and conflicts; distinct totals count consistently bound supplied contributions. Missing value, currency or period excludes the amount. No exchange conversion, win probability, ceiling allocation or inferred bid status is supplied.

Open REPORT.html for the bounded brief and exceptions. OUTPUT.summary.pipeline preserves supplied rows, amounts, scope, exceptions and available source links. REVIEW.csv and Dataset rows remain contract reviews. Pipeline comparison is Review-only: Monitor does not compare pipeline history.

Output and repeated reviews

REPORT.html is the readable review; REVIEW.csv is the working list. OUTPUT links canonical JSON and files. A failed Dataset append does not erase saved reports.

Monitor uses a named history store and state.scopeId; state.storeId and optional baselineSnapshotId select retained comparisons. CHANGES.json/CSV distinguishes 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 a storage permission, not a recurring schedule.

Privacy and interrupted work

Use permitted business data and appropriate Apify access/retention settings. Limited permissions apply; selected history storage needs the stated read/write access. Keep private prose, credentials, contacts and payment details out of inputs. Only selected evidence is retained, not raw upstream error bodies or unrelated fields. The Actor does not automatically delete storage.

Publication and history operations are marked pending before submission. An unknown total charge stays unknown, not zero. Re-entering the same interrupted run does not resubmit its results or charges. Inspect the existing run before a separate review; no cross-storage transaction or automatic cancellation is promised. The custom charge event is contract-review-completed.

Existing saved workflows

New users can start with Demo without choosing a release family. Numbered build 0.4.2, verified October 8, 2026, supplies this guide's optional pipeline brief and current recovery handling. Use that exact build in an established task when a fixed selection is needed; movable tags can change. Preserve original input and read the public release notes before changing a task.

Earlier snapshot/Monitor contracts were recorded under numbered build 0.2.8 on October 2. That is a historical compatibility selector, not a recommendation to downgrade or a promise of indefinite availability; it lacks the pipeline brief and later recovery changes. Inspect the actual available build selector before changing an older workflow. A source-family label such as 0.4 is not itself a numbered build.