# taste

taste connects a person's listening from Last.fm, Discogs, screenshots, and other sources, resolves every artist and release to a single `cluster_id` on the hosaka map, and turns that resolved library into a listener dashboard, recommendations grounded in the hosaka map graph, and a connect API other apps can build on. It is the hosaka fleet's only PII-bearing service — isolated by design.

## Pages

- / — Home: what taste is, how it works, who it is for.
- /how-it-works — Method: the resolver pipeline, coverage honesty, what the hosaka map is.
- /listeners — For listeners: the four dashboard panels, recommendations, how to connect, your data rights.
- /developers — For developers: the connect + consent flow, the /me API, the frozen contract, NINSEI case study.
- /privacy — Privacy commitments: isolated architecture, consent receipts, structural deletion, pairwise IDs, screenshot handling.

## API

The full API surface is a frozen, catalogue-numbered contract served verbatim at:

  /contracts/v1

That YAML file (with comments) is the source of truth. The contract version is 1, last updated 2026-07-07.

All /api/v1/me/* endpoints require the subject's own bearer token (`taste_v1_`). There is no public unauthenticated data API. Token acquisition requires a connect flow — see /contracts/v1 for the full exchange sequence.

## What taste does NOT have

- No Spotify or Apple Music connectors (roadmap, not live).
- No server-side Bandcamp access. Bandcamp data enters only via the user's own screenshots or exports — never server-side scraping or OAuth.
- No user-location features. Scene chips describe where an ARTIST plays; taste holds no user location and has no "near me" feature.
- No public rate card. Pricing is being finalised; taste is free while in dub-plate.
- No self-serve API keys. Integration access requires a contract change (your origin + return URL added to the allowlist). Contact: hello@hosaka.fm.
- No usage or adoption numbers.

## Live example

NINSEI (ninsei.hosaka.fm) — a static SPA with no backend — is the first consumer of the taste connect flow and /me API. It is live and demonstrates the full browser-side integration.

## Fleet

- hosaka.fm — the hosaka fleet home; the hosaka map (≈1.97M artist clusters, 14 source kinds, 448 scene areas as of July 2026).
- crate.hosaka.fm — crate, the fleet's music-data outward service; taste resolves into crate's cluster_id spine via crate's public API.