SAM.gov Contract Opportunities Monitor

SAM.gov Contract Opportunities Monitor collects public US federal opportunity notices into a structured dataset. Search by keyword and narrow the results by agency, notice type, dates, NAICS, PSC or set-aside. Export titles, solicitation numbers, deadlines, offices and public notice links for bid research and procurement dashboards.

Each run is a fresh search, not a change-alert service. SAM.gov may omit values or descriptions. No login or SAM.gov API key is required.

Quick start

1. Open Input and enter a product or service keyword.
2. Start with a small result limit, for example:

{
  "keywords": ["cybersecurity"],
  "activeOnly": true,
  "maxItems": 5,
  "includeDescription": false
}

3. Select Start, then open the dataset when the run finishes. Confirm the agency and deadline on the linked SAM.gov notice before acting.

Prefer a video guide? This short Apify walkthrough shows you how to set up and run an Actor. It uses a different Actor, but the setup steps are the same.

Ready-to-run examples

Choose an example to start with a small, preconfigured input.

• Monitor active SAM.gov cybersecurity opportunities — Find active cybersecurity notices with deadlines and agency context.
• Watch sources-sought notices for janitorial services — Filter janitorial searches to sources-sought notices for early capture research.

What you get

• Opportunity records: titles, identifiers, notice types, agencies, offices and response deadlines.
• Targeted searches: keyword, date, industry-code and public set-aside filters.
• Public detail fields: NAICS, PSC, place and period of performance, and estimated value when available.
• Text for review: short summaries, matched keywords and a normalized relevance score. Full cleaned search-description text is optional.
• Run context: RUN_SUMMARY records completion, partial results and warnings. A controlled cutoff can leave a checkpoint for continuation.

Who is it for?

• Government contractors finding opportunities that match their services.
• Capture and proposal teams checking notice types, deadlines and contracting offices.
• Procurement analysts building public opportunity datasets for downstream analysis.

Input settings

Setting	JSON key	Behavior
Keywords	keywords	One to 25 non-empty search terms. The form starts with construction. Omitted API input uses cybersecurity.
Posted dates	postedFrom, postedTo	Optional inclusive posted-date range, using YYYY-MM-DD.
Notice types	noticeTypes	Codes or labels, such as ["r"] for sources sought.
Agency or office	agency	Case-insensitive text match across department, sub-agency and office. Use the name as shown in the source, not necessarily an acronym.
Industry codes	naics, psc	Optional code lists checked against public notice details.
Set-aside	setAside	Case-insensitive substring match on the public set-aside label or code.
Active only	activeOnly	Defaults to true. Set to false to include inactive notices returned by the search.
Maximum opportunities	maxItems	Total rows to save, from 1 to 10,000. The form default is 20. Omitted runtime input uses 50.
Sort order	sort	modifiedDate (default), postedDate, responseDeadline or relevance. Requests descending order for the selected field.
Minimum value	minEstimatedValue	Optional USD value floor. Notices without a known value are excluded when this is set.
Full description	includeDescription	Defaults to false. Include cleaned search-description text when available, not attachment contents.
Portable checkpoint	resumeCheckpoint	Complete SAM_GOV_CHECKPOINT object from a compatible interrupted run. Copy the entire object unchanged.
Same-store resume	resumeFromCheckpoint	Defaults to false. Reads a compatible checkpoint only if it exists in the current run's key-value store. Portable checkpoints take precedence.

Input recipes

For construction work, use {"keywords":["construction"],"naics":["236220"],"maxItems":5}. For a set-aside search, add "setAside":["small business"] to a keyword search rather than relying on the phrase appearing in the notice text.

Copy a checkpoint only when continuing the same search settings. A shortened sample object is not a valid checkpoint. It resumes progress, not a recurring comparison against earlier datasets.

Output data

Each row is one saved notice. Fields unavailable from the public source are null or empty lists. This synthetic shape-only excerpt illustrates the format, not a verified live opportunity:

{
  "noticeId": "EXAMPLE_NOTICE_ID",
  "title": "Example public opportunity",
  "agency": null,
  "responseDeadline": null,
  "naics": [],
  "estimatedValue": null,
  "matchedKeywords": ["cybersecurity"],
  "enrichmentStatus": "enriched"
}

Field	Description
noticeId	SAM.gov notice identifier
solicitationNumber	Solicitation or reference number
title	Opportunity title
typeCode	SAM.gov notice type code
typeLabel	Human-readable notice type
agency	Department name
subAgency	Agency name
office	Contracting office when available
postedDate	Original posted date
modifiedDate	Most recent modification date
responseDeadline	Response deadline when available
isActive	Whether the notice is currently active
isCanceled	Whether the notice is canceled
naics	NAICS codes when available
psc	Product Service Codes when available
setAside	Set-aside information when available
placeOfPerformance	Place of performance when available
periodOfPerformance	Public performance period when available from notice detail data
summary	Cleaned short description
descriptionText	Optional full cleaned search-description text
uiUrl	Direct public SAM.gov notice URL
sourceUrl	Source search URL used for the record
relevanceScore	Normalized relevance indicator, not a bid recommendation
matchedKeywords	Input keywords matched in the record text
estimatedValue	Estimated value when exposed
enrichmentStatus	Whether official notice-detail data was merged for the record
enrichmentWarning	Non-fatal detail lookup warning when the base record was still saved

Download your results

Open your run's dataset, choose Export and select JSON, CSV or Excel. JSON keeps nested fields together. CSV and Excel are useful when you want to review the records in a spreadsheet.

See Apify's download and export guide for the available formats and field options.

Pricing

This Actor uses pay-per-event pricing. The start event is charged once when a valid run starts, including searches that return no matching records.

The apify-default-dataset-item event charges for each opportunity saved to the default dataset. A saved notice with incomplete detail enrichment is still a result. Warnings and run-summary records are not additional opportunity rows.

Use maxItems to limit saved results. See the live Pricing tab for current rates and discounts. Your Apify account may also incur platform usage charges.

Tips for best results

• Start with five results. Check relevance before increasing the limit.
• Use source names. Agency matching uses the text SAM.gov returns, which may differ from a familiar acronym.
• Add filters gradually. Codes, set-asides and minimum values exclude notices whose details cannot confirm a match.
• Check the original notice. Deadlines and status can change after collection.
• Compare datasets yourself. Repeated runs do not automatically identify new or changed opportunities.

Limits and caveats

• Public opportunity data only. No private procurement records, login, bid submission or attachment downloads.
• SAM.gov can throttle requests, change records or omit fields. Searches may return no matches.
• Search ordering is requested from SAM.gov. There is no separate final global sort across multiple keywords.
• Detail lookup failures can leave partial enrichment. When a detail-backed filter is requested, an unverified notice is skipped instead of assuming it matches.
• Search limits and the available run time can stop a large lookup before every possible result is collected. Review RUN_SUMMARY and any checkpoint.
• Relevance scores describe text matches, not procurement suitability or likelihood of award.

Automation and integrations

Save your settings for next time

Once you have an input that works for you, save it as an Apify task. This keeps your settings together so you can use them again without filling in the form from scratch.

Run on a schedule

Need fresh results regularly? You can schedule the Actor or a saved task to run at a time that suits you.

Each scheduled run collects the data again. If you want to compare results or highlight changes, add that step in your own workflow.

Send results to your other tools

Use n8n, Make or Zapier to connect this scraper to the rest of your workflow. For example, you could pass its results to an AI assistant or add records to a spreadsheet. Follow the Apify integration guides for your chosen tool.

For a custom connection, an Apify webhook can notify your app when a run finishes or fails. Your app can then fetch the results or handle the failure.

API usage

Want to collect this data from your own app or automation? The examples below send input to the scraper and show how to collect its results.

The Node.js and Python examples wait for the run to finish before reading its results. The cURL example starts the run and returns its details. Wait for that run to finish, then use its defaultDatasetId to fetch the results.

For setup instructions, see Apify's JavaScript client guide, Python client guide and Actor runs API reference.

cURL

curl -X POST 'https://api.apify.com/v2/acts/fetch_cat~sam-gov-contract-opportunities-monitor/runs' \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H 'Content-Type: application/json' \
  -d '{"keywords":["cybersecurity"],"activeOnly":true,"maxItems":5}'
# After the returned run succeeds, use its defaultDatasetId:
curl "https://api.apify.com/v2/datasets/DATASET_ID/items?format=json" \
  -H "Authorization: Bearer $APIFY_TOKEN"

Node.js

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('fetch_cat/sam-gov-contract-opportunities-monitor').call({
  keywords: ['cybersecurity'], activeOnly: true, maxItems: 5,
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

Python

import os
from apify_client import ApifyClient

client = ApifyClient(os.environ['APIFY_TOKEN'])
run = client.actor('fetch_cat/sam-gov-contract-opportunities-monitor').call(run_input={
    'keywords': ['cybersecurity'], 'activeOnly': True, 'maxItems': 5,
})
items = client.dataset(run['defaultDatasetId']).list_items().items
print(items)

MCP and AI agents

You can ask your AI assistant to collect data with SAM.gov Contract Opportunities Monitor and help you work with the results. The scraper returns the data, and your assistant can then summarize it, compare records or prepare notes.

Connect your assistant through the Apify MCP server. MCP gives your assistant a way to find this scraper, run it and read the results. Follow the official setup and sign-in guide for your app.

Easier setup with an Apify plugin

If you use a supported coding assistant, the official Apify plugin can set up the connection for you. It connects your assistant to Apify and includes instructions for common tasks. Follow the guide for your particular app.

Use Apify AI in Console

Prefer to keep everything in Apify? Open Apify AI in Console and ask it to find Fetch Cat's SAM.gov Contract Opportunities Monitor. You can describe the data you want and ask questions about the results.

Apify AI is currently in beta. It asks for confirmation before starting an Actor, and normal run charges apply.

Choose your assistant

• Claude and Claude Code (Anthropic): Apify setup guide.
• ChatGPT and Codex (OpenAI): Apify setup guides.
• Grok Bot (xAI): Apify plugin guide.
• Gemini CLI (Google): MCP server setup guide. Use the server URL below with the HTTP configuration supported by Gemini CLI.

Connect just this scraper

To keep your setup focused on this scraper, add this server configuration to a compatible MCP client:

{
  "mcpServers": {
    "apify": {
      "url": "https://mcp.apify.com?tools=fetch_cat/sam-gov-contract-opportunities-monitor"
    }
  }
}

Sign in to Apify when your client asks. If your client uses a Bearer token instead, follow its setup guide and keep the token in its secure configuration. Configuration formats vary by app, so use the linked guide if your client needs a different format.

Use Apify's general server

Already connected to the general Apify MCP server at https://mcp.apify.com? You can use it to find this scraper without adding another server. Ask your assistant to use SAM.gov Contract Opportunities Monitor by Fetch Cat, or give it the identifier fetch_cat/sam-gov-contract-opportunities-monitor.

Your assistant can check the available settings and retrieve the results from the returned run. If the run is still working, it should follow that run rather than start it again. Both connection options use Apify's hosted service.

Example requests

• "Find five active cybersecurity opportunities and list their agencies and response deadlines."
• "Get sources-sought notices for janitorial services and summarize the available descriptions for our capture team."
• "Find construction opportunities with NAICS 236220 and organize their public notice links for review."

Normal Apify charges apply. Check the live Pricing tab before asking your assistant to run a larger batch.

Pay with x402

If your AI agent has a funded wallet, it can pay for Apify usage through x402. This experimental option lets an agent use Apify without a conventional account.

Apify AGI provides a prepaid API token with a spending cap after payment. Your agent can use that token to run this scraper through the Apify API or an authenticated MCP connection.

Some MCP setups also support paying for each request directly. That is a different payment option, so check the official guide for its availability.

Follow the official guide for wallet setup, supported payment options and current terms. Apify handles the payments. Keep wallet keys and payment tokens in your agent's secure configuration.

Other ways for agents to pay

Apify also supports MPP for prepaid access through AGI and Skyfire for eligible Actors. If your agent already uses one of these, see the agentic payment guide to choose the right setup.

FAQ

Can I use this as a SAM.gov data API?

Yes. The Apify API starts a search and returns run details. Read the saved dataset after completion. This is not an official SAM.gov service.

Does it need a SAM.gov login or API key?

No. It reads public opportunity data without either. Private records and bid submission are outside its scope.

Can I include full descriptions or export to Excel?

Enable includeDescription for the cleaned description available in search data. It does not download attachments. Export the dataset to Excel, CSV or JSON when the run completes.

Why are some fields empty or results missing?

Not every notice exposes codes, value or performance details. Restrictive filters can remove notices with missing details. Review RUN_SUMMARY for warnings before relaxing a filter.

Does monitoring compare runs or send alerts?

No. You can schedule fresh searches through Apify and add comparison, deduplication across runs or notifications in your own workflow.

What affects the cost?

There is a start event and a charge for each saved opportunity. Set a small maxItems and check the live Pricing tab before expanding a search.

Related Actors

• Grants.gov Opportunities Scraper — Research public grant opportunities alongside contracts.
• Bing Rank Tracker & SERP Scraper — Research agencies and suppliers on the public web.
• Google News Scraper — Collect news relevant to procurement research.
• Website Contact Finder — Find public contact information for downstream outreach.
• SEC EDGAR Company Filings Scraper — Research public-company filings alongside supplier due diligence.

Support and feedback

For custom additions or integrations, email hello@fetchcat.dev.

Found an error or have a feature request? Open an issue with the run URL, a non-sensitive input example and what you expected.

Need help sharing it? See Apify’s guide to sharing a run when reporting an issue. Sharing a run can give the developer access to its input, logs and results, so use a run that contains no sensitive data. Please leave out API tokens, passwords, cookies, private documents and personal data. Use a public sample URL or a redacted example instead.

Tried this scraper? We'd love to hear how it worked for you. Leave a review to help others choose the right tool and help us improve it. Your feedback means a lot to us.

Made with care for curious people, AI agents and the possibilities in data. ♥