Every service hosaka runs. What it is, where it lives, honest shipping state. One operator, no team, built by agents.
What each door is
crate is the data backbone. Query any artist cluster and get back a dossier: emergence tier, booking arc, press trail, genre coordinates, tastemaker affinities — all from the same substrate the method page documents. The public explorer at crate.hosaka.fm/explore needs no key; keyed API access is metered.
taste is the listener-facing inverse of crate: bring your own listening history and taste resolves it to cluster_ids, then recommends from the co-appearance graph — artists who have shared events and venues with the ones you play. Last.fm and Discogs connect are live, as are the capture bookmarklets and the recommendations themselves. Private beta: there is no public onboarding.
SDK and CLI are the developer-facing doors. The SDK (crate-sdk.hosaka.fm) ships generated TypeScript types for every endpoint. The CLI (github.com/hosaka-fm/crate-cli) is built for agents: stdout is always JSON, stderr is always human, seven exit codes, crate robot-docs for a paste-ready agent handbook. Neither is on a package registry — both are public source (SDK, CLI), built locally. More on the agent surface at /agents.
The full methodology behind what the fleet serves is on the method page. If you are a developer looking to query emergence data, start at /developers or read the SDK docs.