When the API isn't shaped right for your problem.
Most products at this tier sell you more of the same: more requests, more support, more SLA. We do that too. We also do something they don't.
We have the data, we know how to work with it, and we can shape it to your specific need. The fastest way to find out is to email and describe what you're trying to do.
The kinds of things people come to us with.
Sometimes it's the shape of the data. A team comes asking for a Snowflake share, a Parquet drop, a webhook firehose, a mirror Postgres slice, a CSV that lands in their S3 bucket every morning. The data underneath is the same; the pipe is whatever fits your stack.
Sometimes it's joining things. SAM and USAspending and Grants.gov and SBIR aren't keyed the same way; we've spent enough time in the schemas to merge them cleanly when a project needs it. Sub-award lineage, prime-to-sub teaming, agency rollups by NAICS by quarter, the kinds of joins that take a small team a month and us a few days.
Sometimes it's a signal. Vendor Risk has seven baseline signals. If you need an eighth specific to your compliance program (FASCSA exposure, OFAC address-cluster cross-reference, parent-company linkage, first-time-vendor-on-large-award), that's the kind of thing we're built to prototype on a short loop.
Sometimes it's just the operations. The federal data layer breaks. SAM.gov changed schemas twice in 2024. Rate limits shift, multi-key juggling gets old, and most teams would rather not have a data engineer babysitting it. The pitch on this side is straightforward: pay us, don't think about it.
Sometimes it's the historical depth. The 25-year archive (FY1998 through current FY) is sitting on our infrastructure. If you need a one-shot dump, year-over-year extracts, or NAICS-by-quarter rollups for trend work, ask.
None of this is a fixed catalog. The point of the email is that we hear your specific problem and tell you whether we've already done it, can do it quickly, or shouldn't be the ones to do it. All three are useful answers.
The depth is already in our infrastructure.
Most of what enterprise buyers need is data we already keep. We don't expose all of it on the public API, by design. Ask about the slices that aren't.
- Contract notices241K+
- Currently open11K
- Awards with winners55K
- Full notice descriptions205K (85%)
- Debarment exclusions163K
- SAM-registered firms873K
All exposed via the public API. SAM's own API truncates descriptions; we don't.
- Continuous coverageFY1998 to FY2026
- Fiscal years held29
- Bulk archive size18 GB
- Time-series readyyes
Not exposed publicly. Available for custom delivery: bulk dumps, year-on-year extracts, NAICS-by-quarter rollups, agency trend analysis.
Plus full SAM entity profiles, point-of-contact graphs, and modification chains. If you need a slice that isn't in the public docs, the answer is probably "yes, here's how we'd ship it."
Engagements typically start around $1,500 / month.
Scoped to the actual work. Custom builds, slices, and enrichments are quoted on top, depending on the project. The Developer ($19) and Pro ($39) tiers stay as the API ships.
Tell us what you're trying to do.
The mailto pre-fills a few prompts (problem, data shape, volume, deadline). Ignore them or fill them in. We reply within one business day.
Email [email protected]