# NotOnQ

> A drop-in layer in front of the Qloo taste API (hackathon host). Qloo answers first with the caller's own key; when
> Qloo has no data for a music artist, NotOnQ returns the same shape built from open sources, with a source on every
> value, and uses similar artists Qloo does know ("stand-ins") so taste answers still come from Qloo. Artists only.
> Works with the Qloo API; not affiliated with or endorsed by Qloo.

Use it two ways: point the official Qloo MCP server at it (its base URL, nothing else changes), or call the REST API
under `/q` with the same paths as Qloo. Qloo's results always come first, unchanged; NotOnQ's artists are added after
them, labelled "Not in Qloo" in properties.short_description.

NotOnQ shows the behaviour, not the data pipeline: its open sources stand in for whatever Qloo would use. Built into
Qloo, the same flow would run on Qloo's own licensed sources and taste graph.

## Docs

- [Full reference for agents](https://notonq.vercel.app/llms-full.txt): everything below in one markdown file
- [Overview and quickstart](https://notonq.vercel.app/docs): the three ways in, gap kinds, the 1:1 shape, provenance, limits
- [REST API](https://notonq.vercel.app/docs/rest): endpoints, headers, notonq.* parameters, the notonq block, status codes
- [MCP](https://notonq.vercel.app/docs/mcp): the official Qloo harness pointed at NotOnQ, and what changes in each of its tools
- [OpenAPI 3.1](https://notonq.vercel.app/openapi.json): machine-readable REST description

## Optional

- [Ledger](https://notonq.vercel.app/ledger): every artist looked up through NotOnQ, which app asked, and whether Qloo or NotOnQ answered
- [Proof](https://notonq.vercel.app/proof): live numbers from every lookup, and a dated benchmark run
- [Playground](https://notonq.vercel.app/): look up an artist and see Qloo's answer beside NotOnQ's