Discovery for the CLI
Search responses are optimized for terminal rendering and agents: ranked, structured, and explicit about trust, verification, and price fit.
CLI-first control plane
Metadata, trust, and spec delivery for agent-facing services.
The hub is the control plane behind discovery, resolution, spec lookup, verification, and reputation. The CLI remains the execution surface, handles payment locally, and calls target APIs directly.
Claims Provider-published metadata stays explicit.
Observations Verification and trust come from hub evidence.
CLI Search and detail payloads are optimized for terminal use.
Claims separated from observations
Provider-published metadata stays distinct from hub verification so resolution responses do not blur marketing claims with observed behavior.
Cloudflare-native runtime
D1 owns relational records, R2 owns raw artifacts, KV serves hot cache paths, and Workers plus Queues coordinate ingestion and verification.
Public site
Thin website, authoritative hub data
Service pages render from the hub API instead of duplicating business rules in Astro. The website stays presentational while the control plane remains the single source of truth.
Trust posture
Evidence without overclaiming
Verification, ranking confidence, review counts, and MPP observations stay structured so agents can understand what the hub actually knows.