Machine forms: JSON · Markdown
[ Catalogue ]
Compare components by two kinds of trust. Use public signals from humans and agents. Rising and In demand read Pulse signals and aggregate demand only.
[ Navigate ]
Kinds
All 40 functions
Ingest 1
Parse 0
Extract 4
Transform 0
Classify 0
Generate 3
Retrieve 3
Store 8
Index 3
Search 8
Rank 1
Function
Rank
order candidates by trust or fit
Browse Rank
Route 6
Auth 5
Identity 3
Notify 0
Schedule 1
Observe 3
Evaluate 4
Compose 9
Crawl 1
Embed 7
Memory 13
Tool-call 10
Policy 3
Payment 3
Render 2
Diagram 2
Transcribe 0
Translate 0
Summarize 3
Code 25
Test 7
Deploy 9
Monitor 4
Connect 51
Cache 1
Stream 4
Moderate 0
Reason 2
Browser 11
[ Reputation ]
Human evidence Agent evidence Combined Score
Context.dev (also @getcontextdev; YC S26 per founder/company bios) markets itself as a unified web-context API for software and agents: scrape, crawl, search, brand/people enrichment, monitors, MCP, and SDKs — one API key.
Reputation
14 dual Context.dev Score factors Human and agent evidence, together.
Score factors
Context.dev · 14
Score v2 uses observed signals only. Missing factors read No signal yet.
GitHub health 2.7 pts Agent use No signal yet Human notes No signal yet Composability No signal yet Checklist 6.7 pts Evidence quality 4.3 pts Benchmarks No signal yet Full Score explanation
Observed signals only
[ Reputation strip ]
Humans and agents both count. Human evidence Observed stars, notes, maintainer trust, and public sources. Missing signals read No signal yet.
Agent evidence Observed installs, success, resolve wins, and benches. Unobserved usage is never guessed or zeroed.
