GovTech vendors, capture teams, and procurement software
Private beta · Curate route
US federal procurement
Keep proposal applications connected to the current observed opportunity package and its official sources. Access is manually approved and configured for a bounded source, jurisdiction, and workflow scope.
Intended retrieval contract
One request. Bounded evidence.
Private-beta interface preview. Access is manually configured for the approved source and workflow scope. Review the current developer contract.
What changed in the latest verified amendment, including the response deadline?
notice_idpackage_versiondocument_roleNo live result is shown. An approved collection must return bounded passages with citations, source metadata, and one immutable version.
The bounded job
Built for a retrieval problem, not a document dump.
Amendment review, deadline reconciliation, and cited proposal requirements
Retrieval API scoped to one notice and one verified package version
Intended source scope
Public SAM.gov notices and descriptions
Public notice amendments and related records
Public attachments returned by the official API
Explicitly outside scope
Opportunity discovery feeds
Bid recommendations
Private or secure attachments
Automated eligibility decisions
United States federal
English
NoticesAmendmentsAttachments
Coverage and operations
Know what the private beta includes.
Evidence, coverage boundaries, and update targets define this private beta. They are not completeness or service-level promises.
Official API and public-extract paths have been tested against one amendment package. SAM.gov remains a P1 experimental corpus.
Access is configured around a named notice and attachment scope, with attachment rights, archive reconciliation, and workflow requirements confirmed during qualification.
Active opportunities, amendments, attachments, and controlling acquisition material
Research target: daily active-notice checks and weekly archive reconciliation, matching the public SAM.gov update cadence.
Named authorities
Rights status
Official API access is documented. Attachment terms, redistribution boundaries, and derived-artifact rights remain under review.
Provenance gate
Notice identifier, solicitation number, agency, amendment chain, attachment checksum, publication time, deadline, and official URL are required.
Shape the roadmap
Would this source boundary remove real work for your team?
Tell us the workflow, required sources, freshness, filters, and rights that would make it useful.