Payment taken, extraction failed

Same 402 machinery as the rest of the 2016 set, and different from the price lookups in a way that matters: the upstream actively resists what the service does.

Media extractors break constantly. Signature schemes change, player code is rewritten, formats are reorganised, and the maintainers of extraction libraries ship fixes on something close to a weekly cadence. That is a normal cost for a tool you run yourself and a different thing entirely with a paying caller on the other end, because uptime is set by someone who would prefer it were zero.

So the dominant failure is payment taken, extraction failed, not an occasional edge case but the common path in any week upstream changed something. A stateless 402 endpoint has no account, no session and no way to refund, because the design assumes the transaction ends when the response is sent. The whole family shares that problem and this is where it happens constantly rather than rarely.

There is a second mismatch: extraction is slow and a 402 call is synchronous, so a request either blocks for a long time or times out.

Charging for it also makes it a commercial service built on someone else’s copyrighted media, which is the part I would think about first now.