Private beta · Curate route · manual review
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.
What this page claims, and where the proof is
- The source boundary and exclusions are defined.
- Named authorities are identified.
- A public retrieval benchmark for this scope.
Stated evidence is quoted as written. Nothing on this page is a service level.
- Delivery route
- Curate
- Jurisdictions
- United States federal
- Languages
- English
- Activation
- Manual review
Exhibit A · Illustrative · not live
One request. Bounded evidence.
Private-beta interface preview. Access is manually configured for the approved source and workflow scope.
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.
Exhibit B · Coverage perimeter
Built for a retrieval problem, not a document dump.1
Evidence, coverage boundaries, and update targets define this private beta. They are not completeness or service-level promises.
In scope · Intended source scope
- Public SAM.gov notices and descriptions
- Public notice amendments and related records
- Public attachments returned by the official API
Out of scope · Explicitly outside scope
- Opportunity discovery feeds
- Bid recommendations
- Private or secure attachments
- Automated eligibility decisions
- Jurisdictions
- United States federal
- Languages
- English
- Source types
- Notices, Amendments, Attachments
Active opportunities, amendments, attachments, and controlling acquisition material
Exhibit C · Versions and updates
No version history is published for this scope yet.
Research target: daily active-notice checks and weekly archive reconciliation, matching the public SAM.gov update cadence.
- 01Detect
Compare the approved official source against its sealed snapshot.
- 02Review
Verify the source change, rights boundary, structure, metadata, and lineage.
- 03Evaluate
Rebuild the candidate and run the corpus-specific retrieval fixtures.
- 04Activate
Switch versions only with a tested rollback path and customer notice.
Exhibit D · Evaluation
No public benchmark for this knowledge base yet.1
The published evidence pages currently cover the EU AI Act. The current evidence for this scope is stated below as written, without derived scores.
Official API and public-extract paths have been tested against one amendment package. SAM.gov remains a P1 experimental corpus.
Intended retrieval contract
Filter the request. Keep the citation boundary in the response.
Private-beta interface preview. The intended contract returns retrieval context for your application. It does not make the decision your workflow owns.
POST /v1/retrieve · illustrative, not live
query: What changed in the latest verified amendment, including the response deadline?
filters: notice_id, package_version, document_role, published_at, attachment_idFilters narrow an approved scope. They cannot add sources, jurisdictions, or unverified material.
notice_id
package_version
document_role
published_at
attachment_idAn approved collection must return bounded passages with citations, source metadata, and one immutable version.
passages
citations
source metadata
versionThe bounded job
Who this coverage is for.
How the private beta is intended to be used and delivered.
Audience
GovTech vendors, capture teams, and procurement software
Primary use
Amendment review, deadline reconciliation, and cited proposal requirements
Intended delivery
Retrieval API scoped to one notice and one verified package version
Private-beta coverage
SAM.gov notices, amendments, attachments, and deadlines for bounded procurement workflows.
Shape the roadmap · Private beta · manual approval
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.
- What the status means
- Access is manually approved and configured for a bounded source, jurisdiction, and workflow scope.
- Access boundary
- Access is configured around a named notice and attachment scope, with attachment rights, archive reconciliation, and workflow requirements confirmed during qualification.
Provenance notes
- Catalogue recordKnowledge base catalogue
- Status
- Private beta
- Current evidence
- Official API and public-extract paths have been tested against one amendment package. SAM.gov remains a P1 experimental corpus.
- Publication
- Stated evidence only. No reviewed benchmark or trace is published for this scope.