CASE STUDY · PRIVATE
sourcehound
Web search and browser navigation for agents, with TOON-compressed payloads.
Status ruling private, gate under NDA private repo, walkthrough on request
Evidence for Essay 5, Ideal tooling infrastructure: choosing and building tools. The spec names what that argument has to hit and the figures it will cite.
Problem
Agent web access pays twice: in latency and in context budget. Raw payloads and browser schemas burn the very budget the agent needs for reasoning.
Build
- 454 sources across 22 pools (421 active), read from the running catalog.
- TOON (Token-Oriented Object Notation) compression on every payload.
- MCP surface kept lean: 23 tool registrations, counted from the binary registry.
Outcome
- 40 to 60% payload reduction against raw fetches, from the project README, which is authoritative for this surface after the reconciliation in R2.
- Private by policy: the use policy forbids linking the repo; a walkthrough is available on request.
Provenance
| Catalog | 454 sources / 22 pools | running catalog read, 2026-10-26 |
|---|---|---|
| Tool surface | 23 registrations | binary registry read, 2026-10-25 |
| TOON compression | 40 to 60% | project README, 2026-09-22, reconciled in R2 |
Reproduce
Walkthrough on request. Two different published totals for this tool surface were reconciled in R2, and the registry count replaced both.
Private repository: a walkthrough is available on request instead of a link.
From the documentation
A news and web intelligence engine whose catalog is read from the running binary rather than asserted: 454 sources across 22 pools (421 active), re-derived on 2026-10-26.
re-derived 2026-10-26: 454 sources, 22 pools
The repository stays unlinked under the operator use policy, which is why this study is described-not-linked rather than linked.
standing policy