Usage & Analytics
Live, public numbers for this data layer: who is consuming it and what it maintains. Served fresh from the same database the API reads — machine-readable at /api/status and /api/analyze.
API calls · all time
226,541
Last 7 days
70,657
Last 24 hours
13,434
Endpoints serving traffic
26
Open REST + MCP, no keys
API calls — all time
Cumulative total of every request to the public API. Hover a day for its new calls (UTC).
Last 30 days
Total calls
By endpoint
Last 7 days
/api/projects/search5,037
/api/research2,641
/api/repos/search620
/api/builders387
/api/partners240
/api/projects/resolve206
/api/leaderboard111
/api/skills96
/api/analyze95
/api/hackathons/builds95
By consumer type
Last 7 days
Monitoring probes8,58186%
Other1,28013%
curl / scripts1291%
Browsers (people)70%
Crawlers/bots30%
User agents are bucketed coarsely at log time (no IPs, no full UA strings), which limits attribution: server-side agent systems — including SDF's Raven, which grounds its ecosystem answers on this data — send generic clients and appear under "Other", while the named agent buckets only catch interactive AI tools. "Monitoring probes" is largely our own automated quality checks auditing the service daily.
The maintained dataset
What the verification engine keeps true — live collection counts.
Project records
1,084
Indexed repositories
13,129
Research documents
10,172
SEPs, CAPs, dev docs, audits + more
Partners & anchors
50
SCF-funded projects
494
SCF funding tracked
$51.9M
In-house reconstruction — see /api/analyze
Methodology: usage counts come from the API's own request log (append-only; queries truncated, user agents bucketed, no IPs stored). Daily series is UTC-bucketed. Dataset figures are live collection counts. SCF totals are an in-house reconstruction — some award amounts are unpublished — and can differ from SDF's submission-based counters; full basis at /api/analyze. Every data change ships dated in the public changelog.