TasteOS
Checking mode
Checking API mode…
TasteOS / API

Culture, as infrastructure.

Add culturally aware recommendations to an agent without exposing credentials in the browser. Your backend calls the TasteOS API; the browser only sees public JSON.

GET
/api/v1/mode

Inspect runtime mode and Qloo key presence (boolean).

GET
/api/v1/profiles/demo

Curated anonymous demo profiles.

POST
/api/v1/profiles

Create an anonymous taste profile.

PATCH
/api/v1/profiles/{id}

Update preferences / exclusions.

POST
/api/v1/recommendations

Core recommendations for profile ids.

POST
/api/v1/concierge/plan

Reconcile profiles into a proposed outing.

POST
/api/v1/concierge/plan/{id}/reject

Reject one entity and regenerate.

GET
/api/v1/concierge/plan/{id}

Fetch a persisted plan payload.

Responses report their own mode and source. Treat those fields as authoritative; demo data is never presented as live Qloo output. app_rank_score is TasteOS negotiation; qloo_affinity is retrieved evidence when present.