GovAuctions

Government-surplus data built for code and AI agents - real sold-price comps, resale scores, and live listings

The GovAuctions API lets you explore live and historical surplus auction data at scale. Access past sales, sold-price comps, price trends and Flip Scores computed across four government-surplus markets - US, UK, Canada and Australia. You can also access live GSA federal-surplus listings, and webhooks that push new lots to you. Query it over REST, or add the hosted MCP server to Claude Code in one line. One key, the same valuation engine behind GovAuctions Pro.

Add it, list the tools, and ask a sold-price question before anyone signs up. An agent should not need an account to find out whether we have your data.

$1.90 per 1,000 calls, and $0.98 on the tier above. Judge us on that, not on the monthly figure.

US, UK, Canada and Australia comps from the same endpoints and the same key, including on the free tier. No regional add-on, no separate contract.

- •Active federal-surplus lots from GSA Auctions, in one clean schema
- •Filter by state, category, price, and keyword
- •ZIP-radius search: pass a ZIP and a mile radius, get lots nearest first
- •Clean JSON, facts only - pull images from each source URL

- •What comparable items actually sold for: p25 / median / p75
- •Four markets - US, UK, Canada and Australia - matched by item
- •Ask for the underlying sales too, so you can show your work
- •Price up to 100 items in a single batch call

- •The individual sales behind a number: price, month, state
- •Month-by-month medians - is this category softening?
- •A coverage endpoint that tells you what we can’t price, up front

- •Our resale signal: estimated value, effective bid, discount gap
- •Webhooks push matching new lots to you - stop polling
- •The Pro deal-finder, exposed straight to your code

Compare data APIs oncalls per dollar, not on the headline monthly price. Every card below shows what 1,000 calls actually costs on that plan, so a cheaper-looking plan carrying a tenth of the volume cannot hide behind a smaller number.

Plans carry two budgets: total calls, and a smaller allowance for the valuation endpoints - comps, sold history, trends and Flip Score - which is the data we compute rather than collect. Listing calls keep working if you exhaust the valuation allowance, and/api/v1/usagereports both at any time. Batch calls charge one valuation call per item, exactly as if you had sent them one at a time.

- ✓ 100 valuation calls (comps, history, trends, Flip Score)
- ✓ 10 req/sec burst
- ✓ Comps in US, UK, CA, AU
- ✓ 5 underlying sales per call
- ✓ 10 items per batch call
- ✗ Webhooks
- ✗ CSV export

- ✓ 1,000 valuation calls (comps, history, trends, Flip Score)
- ✓ 20 req/sec burst
- ✓ Comps in US, UK, CA, AU
- ✓ 25 underlying sales per call
- ✓ 50 items per batch call
- ✓ 3 webhooks
- ✓ CSV export up to 5,000 rows

- ✓ 10,000 valuation calls (comps, history, trends, Flip Score)
- ✓ 30 req/sec burst
- ✓ Comps in US, UK, CA, AU
- ✓ 50 underlying sales per call
- ✓ 100 items per batch call
- ✓ 10 webhooks
- ✓ CSV export up to 25,000 rows

Bulk historical archives, high call volumes, custom feeds, a data license, or an SLA. Tell us what you're building and we'll shape a plan around it.

Not building against the API? If you want a bulk historical archive, a custom feed, or a commercial data license - for sourcing, valuation, asset recovery, or research - tell us your use case and we'll scope coverage, a sample export, and pricing around it.

curl https://govauctions.app/api/v1/listings?country=US&category=vehicles&limit=5 \ -H "Authorization: Bearer YOUR_API_KEY"

Raw listings and webhook payloads cover sanctioned federal sources (GSA Auctions) in the US. Comps, sold history and trends are our own derived aggregates and cover the full surplus market in all four countries.

Medians are checkable, so your users don't have to take anything on faith.