Quality And Refund
The spec's `quality` block is declared but not read by the server: the refund endpoint judges the output and answers `501 REFUND_NOT_IMPLEMENTED`.
Quality + refund
quality:
min_rating: 4.0
refund_window: 24h
Buyers may request a refund within refund_window if output quality is below min_rating (rated 1-5). Refund logic is the same for v0.1 and v0.2.
What the server does with these two fields today: nothing. They are part of
the spec, a pipeline may declare them, but no code reads min_rating or
refund_window — the refund endpoint does not look at a rating.
What it does look at:
- the purchase: it must be paid, and the 24 hours after it
(
refund_eligible_until, counted from the purchase — not from therefund_windowthe pipeline declares) must still be open; - the output: five patterns disqualify it — empty, shorter than 100 characters, an error string, a stub marker, a single repeated character.
And the endpoint itself pays nothing: it answers 501 REFUND_NOT_IMPLEMENTED
and a human issues the refund. It never reports success and moves no USDC by
itself. A pipeline purchase is refused outright with the same code — the
endpoint does not judge pipeline outputs at all.
Full detail: Refunds.