This first appeared on 15 November 2026 at AgentReady Tools.
The official API for U.S. federal contract notices stores the response deadline under reponseDeadLine. That's how the field appears in GSA's Get Opportunities Public API. If an agent looks for responseDeadline, the date isn't there.
A person can still get work done on SAM.gov, the official U.S. source for those notices. You click through search results, create a free account, open Account Details, and generate a public API key. You may have to re-enter a password or an emailed one-time code. An agent can't complete that part on its own. And even after an operator supplies a key, a new personal key can be tightly rate-limited.
You don't always get a clean error. The agent spends its budget parsing a page, or a slightly different JSON blob every time, instead of doing the work. A shared key pasted into a chat is a bad workaround. The API's description field is a URL, not the notice text, and date formats differ depending on how you fetch. This is what the official source looks like when an agent tries to use it.
That was the bind we were in when we tried to get active solicitations into a shape an agent could actually use. We didn't want a shared key, and we didn't want to scrape SAM.gov pages. We also didn't want to hide how messy the official API can be.
So we built SAM.gov Contract Opportunities, listed under the slug sam-gov-opportunities. It also lives on the Apify Store. The default path streams the official public daily extract of active contract opportunities, ContractOpportunitiesFullCSV, published by SAM.gov Data Services. No SAM.gov key is required. That file is up to about a day old. Each item carries dataSource (sam.gov-daily-extract or sam.gov-api) and, in extract mode, extractDate from the file's Last-Modified header. Those fields are documented on the listing and in the machine-readable record.
If you need live data, you pass your own free public API key from a SAM.gov account, and the Actor uses the official API. The key is a secret input, used only during the run, and is never written into the dataset. We also strip any api_key query parameter from stored links.
The tradeoff is written down. The extract needs no key and covers active notices. The API can include inactive notices in a one-year window, but a new personal key can be tightly rate-limited, and in API mode description is a URL, not the notice text.
For agents: The listing slug is sam-gov-opportunities. Machine-readable copies are at https://agentready-tools.com/tools/sam-gov-opportunities.json, https://agentready-tools.com/tools.json, and https://agentready-tools.com/llms.txt. The public catalog MCP is https://agentready-tools.com/mcp (com.agentready-tools/catalog).
What we learned while building it is now five checks we use when we call a tool agent-ready. These are working notes from one build, not a standard, and not a claim that every listing in our directory already passes all five.
1. Can an agent call it and get a record back?
Most of the useful web is still a page. Agents need a record: one object per thing, with field names that stay put. The misspelled deadline field is the obvious example, but the quieter problem is a key that appears in some rows and vanishes in others.
Our Actor returns one normalized item per SAM.gov notice, in JSON, CSV, or Excel. Stable fields include noticeId, title, solicitationNumber, type, postedDate, responseDeadline, naicsCode, setAside, agency path, place of performance, points of contact, and the official SAM.gov link (uiLink). We accept reponseDeadLine and responseDeadLine from the API and expose a single responseDeadline. Missing values are null, not an empty string.
2. Is the data from an official source, and do you say how fresh it is?
We don't scrape SAM.gov pages. That was a build decision: the default path uses the official public extract, and live mode uses the official API. Because the extract can be up to about a day old, every item carries dataSource, and extract-mode items also carry extractDate from the file's Last-Modified header, so a caller can see which path produced the row and how fresh it is. Those fields are on the listing and in the JSON record. An agent will treat stale data as current if you don't say so.
3. Can the agent actually authenticate?
A public API that still needs a human to click through Account Details, and maybe type a one-time code, is not ready for an agent on its own.
The default extract path needs no SAM.gov key at all. We made that the default so an agent can get a record back without anyone completing the Account Details flow. The live path uses a key the operator already has, or can create on the SAM.gov Account Details page. We don't use a shared key, and we don't ask the agent to sign in to sam.gov in a browser.
You still need an Apify token to run the Actor, or to reach it through Apify's MCP server. That's a platform credential, not a SAM.gov login.
4. Is the price visible before the call, and billed per useful result?
A rule we now use when we review tools (this is policy, not a failed experiment from this build) is that a monthly plan with a soft cap is a poor fit for agents that retry and over-fetch. Pay-per-use only helps if the unit is something the caller can cap.
On this Actor, as of 16 November 2026, the Apify Store listing prices it at $2 per 1,000 opportunities stored, or $0.002 each, on pay-per-event (event name opportunity). Platform usage for the run is included. You are charged only for opportunities that are successfully stored. Notices that get filtered out, duplicates within a run, rejected records, and download or API errors don't generate a charge. The store README also documents maxItems: it defaults to 10 and tops out at 10,000, and the budget is checked before every charged item. The same Actor is listed at SAM.gov Contract Opportunities and in the JSON record.
A few limits we should say out loud: runs are independent, so the same query can charge for the same notice again, and if a run fails after some items are stored, those items may already have been billed. There is no cross-run deduplication.
5. Are the filters structured, and are the gaps written down?
An agent needs inputs it can fill in, not a search box with hidden rules.
You can filter by title keywords, NAICS (a prefix match on the extract, the official ncode on the API), set-aside code, notice type (the official ptype values, such as solicitation or sources sought), place-of-performance state, and a posted-date range of at most one calendar year. Empty input returns up to 10 recent active notices. Filters can also return nothing. That's a valid result, not an error.
We also document the gaps, because an agent will hit them. The extract has no attachment list, so resourceLinks is null in that mode. The Actor does not download attachments, which can have their own access rules. Keyword search is a title search, not full-text. Date formats differ between the extract and the API. And yes, we still have to accept reponseDeadLine.
That last one is small. It's also the kind of thing that quietly breaks a workflow if you pretend the upstream API is tidy.
What we're doing with this
These five checks are how we now look at tools, including our own. AgentReady Tools is a curated directory of tools we think are closer to this bar: clean callable data, pay-per-use pricing, and some control over what an agent can do and spend. As of 16 November 2026 the catalog at /tools.json lists more than 250 agent-ready tools, including this SAM.gov Actor and a few others we built (URL screenshot, ATS jobs). The site also publishes /llms.txt and the public MCP server described above.
Spend Controls is a demand test, not a live product.
If you're building for agents, I'd start with check 1 and check 5. Structured output and honest gaps are what we needed when the official deadline field was misspelled and a key still needed someone to click through Account Details. Write that kind of gap down first. Then look at the listing.
- The tool: agentready-tools.com/tools/sam-gov-opportunities
- Machine-readable record: agentready-tools.com/tools/sam-gov-opportunities.json
- Official Get Opportunities API: open.gsa.gov/api/get-opportunities-public-api
Top comments (0)