Quickstart
# 1. Mint a key: CLEATUS → Settings → Integrations → API Keys
# 2. Search opportunities
curl -G https://api.cleat.ai/v1/opportunities/search \
-H "X-Api-Key: ck_live_…" \
--data-urlencode "q=healthcare IT" \
--data-urlencode "naics_codes=541512,541511" \
--data-urlencode "states=VA,MD"
# 3. Everything else is in the OpenAPI spec
curl -s https://api.cleat.ai/api/openapi.json | jq '.paths | keys'OpenAPI + Swagger
Full OpenAPI 3 spec and interactive docs for all 34 endpoints.
MCP for agents
The same surface over the Model Context Protocol, with per-platform setup guides.
Simple auth
X-Api-Key headers for servers, OAuth 2.1 + PKCE for user-scoped apps. One quota, full audit log.
llms-full.txt
The whole platform in one plain-text file, written for AI agents to read.
Guides to the public data sources
Honest, practical guides to the government's own APIs, because you should know exactly what the raw feeds give you before you decide how much of the pipeline to build yourself.
SAM.gov API: the complete guide
Get an API key, query the Get Opportunities endpoint, survive the rate limits, and know when the raw feed is (and is not) enough.
Read the guideUSASpending API: awards data without keys
Pull federal award history, competitor spend, and agency totals from the free USASpending API, with the request shapes that actually work.
Read the guideFPDS explained (and how to pull from it)
What the Federal Procurement Data System is, how it relates to SAM.gov and USASpending, and how to read the ATOM feed.
Read the guide